4 ms·

I'll be looking forward to see how your access control feature works. I am currently using netmaker (netmaker.org) which is limited to allow/deny per endpoint i

I'll be looking forward to see how your access control feature works. I am currently using netmaker (netmaker.org) which is limited to allow/deny per endpoint instead of service based policy. I really like you auth0 option for the self-hosted version. Having to host identity can be quite the security risk. What I dislike a little right now are all the required open ports. I see of course why they are required, However having to secure all of them would be quite a feat. I am always a "simpler is better" proponent. Fewer ports will reduce the attack-surface to manage in the enterprise. Keep up the good work!

braginini 4y ago
Thank you for the kind words and feedback! Access controls are in progress and will be released in June. We are building a tagging system for peers (endpoints) so that you could create peer groups and assign access rules to them. Check the mockups https://github.com/netbirdio/dashboard/blob/main/media/tagging-policy.png https://github.com/netbirdio/dashboard/blob/main/media/taggi... We will reduce ports for Management (merge gRPC with HTTP) so it will be just port 443. AS for TURN and Signal, these are separate components and require open ports. You could also use any public TURN server - your traffic will be p2p encrypted, just the IP of your peer will be exposed to that services. If it is not a concern, then it is a good option :)