Bump libp2p-noise from 0.43.1 to 0.43.2

[dependabot]

Bumps libp2p-noise from 0.43.1 to 0.43.2.

Release notes

Sourced from libp2p-noise's releases.

libp2p-v0.52.3

See individual changelogs for details.

libp2p-v0.52.2

See individual changelogs for details.

libp2p-v0.52.1

See individual changelogs for details.

libp2p-v0.52.0

Automatic kademlia client/server mode

Let's get the biggest one out the way first, I promise the other points are easier explained but equally exciting. The tl;dr is: Healthier Kademlia routing tables and an improved developer experience.

If you don't know about Kademlia's client/server mode, checkout the specs.

With the v0.52 release, rust-libp2p automatically configures Kademlia in client or server mode depending on our external addresses. If we have a confirmed, external address, we will operate in server-mode, otherwise client-mode. This is entirely configuration-free (yay!) although follow-up work is under-way to allow setting this manually in certain situations: #4074.

We can now do the following:

1. As soon as we learn about an external address (e.g. via AutoNAT), we activate server mode of Kademlia.
2. Activating server-mode means we allow inbound requests, this is a change in our set of supported protocols.
3. The change is detected automatically and reported to all protocols as ConnectionEvent::LocalProtocolsChange.
4. libp2p-identify picks up this change and pushes it to all connected remote nodes.
5. Remote nodes can instantly put us into their routing table.

To implement this, several other features/issues had to be fixed. If you are interested in the details, read on:

• Simplify the scoring mechanism of external addresses: #3954

  As a consequence, the observed address reported by identify is no longer considered an external address but just an address candidate. Checkout the changelog-entry for a way of restoring the old behaviour.

• Changes to the supported protocols are now detected at runtime and communicated to all protocols: #3651.

  Previously, a protocol could retrieve the supported protocols via PollParameters::supported_protocols. This list however was computed at start-up and was static. Now, ConnectionEvent has two new variants:

  pub enum ConnectionEvent<'a> {
    // existing variants omitted ...
  /// The local [ConnectionHandler] added or removed support for one or more protocols.
  LocalProtocolsChange(ProtocolsChange<'a>),
  /// The remote [ConnectionHandler] now supports a different set of protocols.
  RemoteProtocolsChange(ProtocolsChange<'a>),
  }
  pub enum ProtocolsChange<'a> {
  Added(ProtocolsAdded<'a>),
  Removed(ProtocolsRemoved<'a>),
  }

... (truncated)

Commits

• c980b4e deps(noise): update x25519-dalek to 2.0.0
• e1c1f03 chore(perf): remove unused module
• c91ecbc ci: don't run changelog check on chores and refactor PRs
• 29c44e8 ci: run clippy on all targets
• 44ce656 chore: activate clippy::unnecessary_wraps lint
• 15ad4ea feat(gossipsub): deprecate Config::idle_timeout
• 4686ce8 feat(rendezous): refresh registration on change to external addresses
• d72c67d fix(kad): actually report unsupported protocol
• 0446068 ci: ensure Cargo.toml and CHANGELOG of published crates are updated
• 74c087d fix(libp2p): add shortcut with_tcp(...).with_bandwidth_logging()
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)