require new nodes to be validated before being able to connect #310

New issue

Open

opened 2022-05-23 20:39:02 +00:00 by trinity-1686a · 0 comments

trinity-1686a commented

2022-05-23 20:39:02 +00:00

Owner

Today the RPC is secured by requiring the knowledge of the RPC secret and the ip and node id of at least one node. To make Garage more secure against leakage of the RPC secret and node id, Garage could require a new node to be accepted by an other node before it can issue any RPC command (or require initial connection to always come from an already known node to a new node). This functionality should probably be optional.
It's currently not possible to implement something like this as client RPC creates a temporary node, so it would prevent any administrative operation, however as we move to a REST admin API, it should become possible

Today the RPC is secured by requiring the knowledge of the RPC secret and the ip and node id of at least one node. To make Garage more secure against leakage of the RPC secret and node id, Garage could require a new node to be accepted by an other node before it can issue any RPC command (or require initial connection to always come from an already known node to a new node). This functionality should probably be optional. It's currently not possible to implement something like this as client RPC creates a temporary node, so it would prevent any administrative operation, however as we move to a REST admin API, it should become possible

👍 1