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.

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

How to prevent Ddos attack? #16

Closed
LeonLi000 opened this issue Dec 5, 2017 · 3 comments
Closed

How to prevent Ddos attack? #16

LeonLi000 opened this issue Dec 5, 2017 · 3 comments
Assignees

Comments

@LeonLi000
Copy link
Contributor

How to prevent Ddos attack in Nebulas?
If someone maliciously falsifies a lot of invalid transactions to attack our network in Nebulas, our block broadcast and relay will not work. Because the network will be occupied by those invalid transactions.
So, how to prevent Ddos attack?

@LeonLi000
Copy link
Contributor Author

LeonLi000 commented Dec 5, 2017

Now I have three ideas.

  1. Defines the priority of receiving processing network packet messages. Take precedence over the block message.
  2. Avoid message infinite relay and add hop limit.
  3. Limit the frequency of messages from the same node.

So, does anyone have any other idea?

@LeonLi000 LeonLi000 self-assigned this Dec 5, 2017
@fbzhong fbzhong added TODO and removed help wanted labels Dec 6, 2017
@fbzhong
Copy link
Contributor

fbzhong commented Jan 24, 2018

Latest develop branch includes more functionality to prevent some kind of DDOS attack:

  1. priority message queue for sending network message in net model;
  2. Guaranteed block producing time, make sure nodes would mint and broadcast block on time.
  3. Seperating the handling process of tx, block and LIB.

@fbzhong
Copy link
Contributor

fbzhong commented Feb 3, 2018

Updated:

  1. Add [Design] Add optimize strategy for message dispatching in network #50 optimize strategy for message dispatching in network

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants