README
¶
coe865-final : gossip protocol
gossip Shutdown : overview
the Shutdown has the following sub-components :
sentry: it stores the Shutdowns private RSA key and it's job is to confirm message signatures, generate new nonce and encrypt/decrypt payloads based on myDARE( data at rest encryption) refrence implementationswarm: holds a snapshot of all the gossip nodes the Shutdown is directly connected to. it has an upper limit which controls the maximum number of nodes the Shutdown has established a direct connection to??: holds information about the state of the network and uses djikstra's algorithm calculate best pathscheduler: a background task scheduler that fires an event, based on given cron specs
gossip Shutdown : init
initially , when every gossip Shutdown daemon comes online, starts a listener and waits for incomming connection. it also takes in a list of initial bootstrap peers to connect to which it tries to establish direct connection to.
swarm's listener spawns a new goroutine per incoming connection. the newly created incomming connection
is passed down to underlying swarm component for handling the new peer that established connection to it.
swarm component , checks to see if it still has room for more direct peers. it replies back with a hello message
in which it indicates whether the connection was accepted or dropped based on the number of direct
connections it was configured to accept. if the connection was dropped ,
it returns back with an error to Shutdown and Shutdown, by default ,drops connections
if there is an error from swarm. in case the connection was accepted, swarm replies back with addresses
of peers it is directly connected to so that the other Shutdown can start infecting them.
when Shutdown recieve a hello message that shows the other Shutdown they are trying to connect to
accepted the connection, they reply back with their own hello message which contains
list of nodes they are directly connected to which the recieving Shutdown would try to
establish direct connection to them.
gossip Shutdown : rumour
the gossip Shutdown, with the help of scheduler component tries to spread a rumor at set time
quantums. the rumor is result of ?? calculating best path using djikstra's algorithm.
once the message is prepared, it is sent to sentry component. sentry would encrypt the payload
with DARE, i.e. generate a new nonce and encrypt the message with the said nonce and original key.
it also would sign the message and attach the signature before returning the result to Shutdown.
then Shutdown would pass in the message to swarm component so that it can encode the message with json
and pushes it on the wire for all nodes it is directly connected to
once swarm recieves a rumor, it decodes it from json and through it's internal channel with Shutdown , sends
the decode message to Shutdown for processing. once Shutdown picks up a message from channel , it would send the message
to sentry. sentry would confirm message authenticity and reply back to Shutdown. at this point based on sentry's reply,
the Shutdown can take two actions : reject the message or infect other nodes connected to it.
in case sentry replies back with an error, the Shutdown would reject the message. it also keeps track of how
many messages it has rejected from a particular node. if it passes a certain threshold, it would ask swarm
component to remove the node from it's address book and broadcast to others that the node is behaving maliciously
so that other nodes remove the bad actor from their own swarm, effectively kicking it out from the network
in case the message was authentic, sentry would generate a new nonce and re-encrypts the message with new nonce
before returning it back to Shutdown . this nonce chaining scheme is why my DARE implementation can prevent
replay attacks.
gossip Shutdown : leave
Directories
¶
| Path | Synopsis |
|---|---|
|
build
|
|
|
cmd
|
|
|
pkg
|
|
|
gossip/codec
Package codec provides an interface for marshalling/unmarshalling data in json .
|
Package codec provides an interface for marshalling/unmarshalling data in json . |
|
gossip/core
Package core maintains common configuration values used in the network it also encodes and decodes internal and external messages and queries
|
Package core maintains common configuration values used in the network it also encodes and decodes internal and external messages and queries |
|
gossip/lamport-clock
Package lamportclock is a thread-safe implementation of a lamport clock.
|
Package lamportclock is a thread-safe implementation of a lamport clock. |
|
gossip/sentry
Package sentry wraps rsa.PublicKey
|
Package sentry wraps rsa.PublicKey |
|
gossip/swarm
Package swarm helps a node in the swarm keep track of all the nodes that is connected to it it .
|
Package swarm helps a node in the swarm keep track of all the nodes that is connected to it it . |
|
hashsink
Package hashsink implements io.reader and io.writer that hashes the payload as operating on data
|
Package hashsink implements io.reader and io.writer that hashes the payload as operating on data |
|
jsonutil
Package jsonutil helps with encoding/decoding data in json format.
|
Package jsonutil helps with encoding/decoding data in json format. |
|
view
Package view implements Gated Writer and log writer
|
Package view implements Gated Writer and log writer |