School project at CentraleSupélec. The goal is to build a network with the authentication rule "friends of my friends are my friends".
Each node of the network is named "Equipment". Each launch of the binary simulates a new equipment.
ssl_network -a 127.0.0.1 -p 3201 -n Equipment1When the simulated equipment is generated, a shell starts. The available commands are :
certified : Display certified equipments
clear : Clear shell
con:client : Start a connection as client (ex: con:client 127.0.0.1:3202)
con:server : Start a connection as server
help : Print this help
history : Print commands history or run a command from it
infos : Display equipment infos
quit : Quit
syn:client : Start a synchronization as client (ex: syn:client 127.0.0.1:3202)
syn:server : Start a synchronization as server
To build this project you need to install Cargo.
git clone git@github.com:quentm74/SSL_network.git
cd ./SSL_network
cargo build
./target/release/ssl_nework -hFollow those simple commands to see in action a "friends of my friends are my friends" network.
Equipment1 and Equipment3 will be able to connect automatically even without connecting before.
ssl_network -a 127.0.0.1 -p 3201 -n Equipment1ssl_network -a 127.0.0.1 -p 3202 -n Equipment2ssl_network -a 127.0.0.1 -p 3203 -n Equipment3The user should approve the insertion of the peer equipment in each terminal.
shell Equipment1
> con:server
shell Equipment2
> con:client 127.0.0.1:3201
The user should approve the insertion of the peer equipment in each terminal.
shell Equipment2
> con:server
shell Equipment3
> con:client 127.0.0.1:3202
The user does not have to approve the insertion of the peer equipment in each terminal because :
- Equipment1 receive a certification chain from Equipment3 that certify Equipment3 from itself
- Equipment3 has a certification chain that certify Equipment1 from itself
At this step you should also see that they automatically exchange new certificates too.
shell Equipment1
> con:server
shell Equipment3
> con:client 127.0.0.1:3201