Skip to content

Latest commit

 

History

History
101 lines (73 loc) · 2.43 KB

Readme.md

File metadata and controls

101 lines (73 loc) · 2.43 KB
Raw

SSL_network

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 Equipment1

When 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

Build

To build this project you need to install Cargo.

git clone [email protected]:quentm74/SSL_network.git
cd ./SSL_network
cargo build
./target/release/ssl_nework -h

Example

Follow 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.

Launch three equipments in different terminals

ssl_network -a 127.0.0.1 -p 3201 -n Equipment1
ssl_network -a 127.0.0.1 -p 3202 -n Equipment2
ssl_network -a 127.0.0.1 -p 3203 -n Equipment3

Connect 1 with 2

The 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

Connect 2 with 3

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

Connect 1 with 3

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