You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is an easily discoverable way for a js-libp2p node operator to find the monitoring options available to them
We have a document we can point js-libp2p operators to in defense of or response to various resource exhaustion attacks (DoS, eclipse).
Why Important
These are concepts that are best thought about in advance to prevent successful attacks.
If there is an attack, especially in the heat of battle, every minute reducing response/mitigation times can be significant. Having suggestions/steps prethought outside the fog of war will provide better suggestions in a quicker period of time.
Background
js-libp2p has various mechanisms to protect a node against attacks. We want to make sure users are aware of the mechanisms available to them and that they're thinking about this.
Done Criteria
Why Important
Background
To-do
These are partially covered in docs: update limits doc #1456.
The text was updated successfully, but these errors were encountered: