From c7804b5b1cd945474ba8299a6e4fe8f17d748894 Mon Sep 17 00:00:00 2001 From: Steve Loeppky Date: Wed, 7 Dec 2022 15:57:03 -0800 Subject: [PATCH] Added changelog entry --- docs/changelogs/v0.18.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/changelogs/v0.18.md b/docs/changelogs/v0.18.md index 4afa6793ea92..e29e71450c71 100644 --- a/docs/changelogs/v0.18.md +++ b/docs/changelogs/v0.18.md @@ -68,6 +68,19 @@ $ curl "http://127.0.0.1:8080/ipfs/$DIR_CID?format=dag-json" | jq } ``` +#### Improving libp2p resource management integration + +To help protect nodes from DoS (resource exhaustion) and eclipse attacks, +Kubo enabled the [go-libp2p Network Resource Manager](https://github.com/libp2p/go-libp2p/tree/master/p2p/host/resource-manager) +by default in [Kubo 0.17](https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.17.md#libp2p-resource-management-enabled-by-default). + Introducing limits like this by default after the fact is tricky, + and various improvements have been made to improve the UX including: + 1. [Dedicated docs concerning the resource manager integration](https://github.com/ipfs/kubo/blob/master/docs/libp2p-resource-management.md). This is a great place to go to learn more or get your FAQs answered. + 2. Increasing the default limits for the resource manager. + 3. Enabling the [`Swarm.ConnMgr`](https://github.com/ipfs/kubo/blob/master/docs/config.md#swarmconnmgr) by default and reducing it thresholds so it can intelligently prune connections in many cases before the indiscriminate resource manager kicks in. + 4. Adjusted log messages and levels to make clear that the resource manager is likely doing your node a favor by bounding resources. + 5. [Other miscellaneous config and command bugs reported by users](https://github.com/ipfs/kubo/issues/9442). + ### Changelog ### Contributors