This issue addresses a zero configuration setup. The motivation behind this PR is to introduce running nodes on a closed network and allow nodes which join the network to be accessible via the generated public key which is propagated on runtime. Features introduced.
unsafe mode: Allows to add the public keys of nodes in the network to the node which enabled unsafe mode in the config file.
Bug fixing to allow nodes to update nodes in the network faster.
Introduced new field called PublicKey in the IPTable. This field propagates the IP address through the network to ensure all nodes that have the latest IPTable can access this information.
Motivation
Using master the allow N number of of Raspberry PIs to P2PRC without any pre-setup needed.
The ability to build a deployment system on top of the preset SSH connections.
Limitation
The authorisation_keys file needs to be public keys to be manually removed to ensure the file does not grow in size exponentially.
Add authorisation searches on disk to check for duplicates which can be expensive.
(The limitations will be addressed in a separate issue when it is at the required priority).
This issue addresses a zero configuration setup. The motivation behind this PR is to introduce running nodes on a closed network and allow nodes which join the network to be accessible via the generated public key which is propagated on runtime. Features introduced.
unsafe mode: Allows to add the public keys of nodes in the network to the node which enabled unsafe mode in the config file.PublicKeyin the IPTable. This field propagates the IP address through the network to ensure all nodes that have the latest IPTable can access this information.Motivation
Limitation