Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Limit allowed connections #620

Closed
ineiti opened this issue Feb 13, 2020 · 0 comments · Fixed by #640
Closed

Limit allowed connections #620

ineiti opened this issue Feb 13, 2020 · 0 comments · Fixed by #640
Assignees
@cgrigis

Comments

@ineiti
Copy link
Member

ineiti commented Feb 13, 2020 •
edited
Loading

To further lock down the nodes, it should be possible to define which nodes are allowed to connect. This can be a simple extension of the Server structure with something like:

AllowNodes([]network.ServerIdentityID)

Whenever a new block is accepted by the byzcoin service, it would call this method with the latest roster.

The AllowRoster should limit both incoming and outgoing connections to be restricted to the set given in AllowNodes.

An environmental variable can be used to switch between the behaviour before AllowNodes is called:

  • locked - nothing allowed
  • open - everybody can connect
  • xxxx:xxxx:.... - a list of ServerIdentityIDs allowed to connect
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@cgrigis cgrigis

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add filtering for input and output connections
2 participants
@ineiti @cgrigis