https://netmaker.org logo
Hi! I've been evaluating nebula for a bit and am j...
# netmaker
a
Hi! I've been evaluating nebula for a bit and am just starting to look at netmaker. (This is more or less a homelab setting, possibly connecting multiple homelabs.) I like the idea of netmaker -- it's something I wished for when setting up my first wireguard network. To me it seems like there is a big difference between the trust model of nebula and the trust model of netmaker. It seems to me that nebula lighthouses can operate as more or less untrusted orchestration nodes on the network, but a netmaker server must be fully trusted. This would mean that a compromised netmaker server could basically mitm all network traffic, but a compromised nebula lighthouse could not. This is a concern for me as I see these as the most vulnerable nodes on the network. It seems to me that this is a tradeoff for more or less "automagical" configuration granted by netmaker. I've only barely started to look at netmaker, so I wanted to ask: is this an accurate assessment?
b
Netmaker server is not involved in peer to peer communications.
a
But it distributes keys, right?
b
No. Keys are generated by client
Server does generate the keys for external clients but not for regular nodes
Server does not know the private key of a normal client. For ext clients, the server generates the private key but does not keep a copy of the key
a
But the server distributes the public keys? In nebula there can be an external, non-lighthouse, CA to sign public keys.
b
Public key only works with its corresponding private key.
a
My concern is that a compromised server can distribute whatever keys it likes, generate its own, and mitm
b
It would have to spoof the public IP of peers as well
a
Does it not manage those as well?
b
It distributes them, yes
a
Gotcha, thanks! I wonder if some sort of similar signing mechanism could be implemented in the future to allow for centralized trust that is shifted off of the server.
Just for context, in case it's of interest: the reason this concerns me (somewhat) is that what appeals to me about this type of setup is running everything on hardware I control. On a budget, this still means I still need some sort of publicly accessible cloud server, meaning it's both exposed to the public internet and running on someone else's hardware. The ideal scenario for me is that this server is not trusted, but netmaker's apparent ease of management and performance is a huge plus of course. Know that's perhaps a bit paranoid, but 🤷
5 Views