Skip to content

Releases: libp2p/go-libp2p

v0.28.3

07 Aug 23:38
@github-actions github-actions
v0.28.3
851f49d
Compare
Choose a tag to compare
v0.28.3

What's Changed

  • Updates quic-go to v0.33.1

Full Changelog: v0.28.2...v0.28.3

Assets 2
Loading

v0.27.9

07 Aug 23:38
@github-actions github-actions
v0.27.9
aa04c53
Compare
Choose a tag to compare
v0.27.9

What's Changed

  • Update quic-go to v0.33.1

Full Changelog: v0.27.8...v0.27.9

Assets 2
Loading

v0.27.8

04 Aug 00:00
@github-actions github-actions
v0.27.8
8506ab2
Compare
Choose a tag to compare
v0.27.8

This patch release contains backports of:

  • updating the qtls dependencies (qtls is quic-go's fork of crypto/tls). The new versions now contain a backport of the Go standard library fix included in the Go 1.20.7 / 1.19.12 release for quic-go's crypto/tls fork: golang/go@2350afd
  • core/crypto: restrict RSA keys to <= 8192 bits: #2454. The analogous vulnerability in go-libp2p's crypto package.
  • swarm: don't open new streams over transient connections: #2450. This fixes a regression introduced in v0.26.0.

Note that in order to be protected against the DoS attack making use of large RSA keys, it's necessary to update to this patch release AND to use the updated Go compiler (1.20.7 or 1.19.12, respectively).

Full Changelog: v0.27.7...v0.27.8

Assets 2
Loading

v0.29.1

03 Aug 21:28
@github-actions github-actions
v0.29.1
68dc5cc
Compare
Choose a tag to compare
v0.29.1

This patch release contains backports of:

  • update quic-go to v0.36.3, fixing RSA key size vulnerability: #2455. This in turn is a backport of the Go standard library fix included in the Go 1.20.7 / 1.19.12 release for quic-go's crypto/tls fork: golang/go@2350afd
  • core/crypto: restrict RSA keys to <= 8192 bits: #2454. The analogous vulnerability in go-libp2p's crypto package.
  • swarm: don't open new streams over transient connections: #2450. This fixes a regression introduced in v0.26.0.

Note that in order to be protected against the DoS attack making use of large RSA keys, it's necessary to update to this patch release AND to use the updated Go compiler (1.20.7 or 1.19.12, respectively).

Full Changelog: v0.29.0...v0.29.1

Assets 2
Loading

v0.28.2

03 Aug 21:27
@github-actions github-actions
v0.28.2
256b838
Compare
Choose a tag to compare
v0.28.2

This patch release contains backports of:

  • updating the qtls dependencies (qtls is quic-go's fork of crypto/tls). The new versions now contain a backport of the Go standard library fix included in the Go 1.20.7 / 1.19.12 release for quic-go's crypto/tls fork: golang/go@2350afd
  • core/crypto: restrict RSA keys to <= 8192 bits: #2454. The analogous vulnerability in go-libp2p's crypto package.
  • swarm: don't open new streams over transient connections: #2450. This fixes a regression introduced in v0.26.0.

Note that in order to be protected against the DoS attack making use of large RSA keys, it's necessary to update to this patch release AND to use the updated Go compiler (1.20.7 or 1.19.12, respectively).

Full Changelog: v0.28.1...v0.28.2

Assets 2
Loading

v0.29.0

14 Jul 17:40
@github-actions github-actions
v0.29.0
636a096
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.29.0

⚠️ Warning

Be warned if you run go get -u github.com/libp2p/go-libp2p the Go toolchain will incorrectly update github.com/quic-go/qtls-go1-20 to an incompatible version of v0.3.0 (at v0.* everything may change according to semver). You may have to downgrade github.com/quic-go/qtls-go1-20 to v0.2.2 manually.

It's recommended to do go get github.com/libp2p/go-libp2p instead.

🔦 Highlights

Smart Dialing

In our last release, we shipped Smart Dialing. To reiterate, it’s a clever way to reduce the number of spurious dials. Instead of dialing all addresses in parallel (which is what we did before v0.28), we now carefully rank the addresses and dial them one by one.

However, there were two areas where the logic we introduced could lead to suboptimal results:

  • There are some networks that block UDP. This means that we won’t be able to dial any QUIC or WebTransport connections at all. This is problematic since our smart dialing logic dials a QUIC address first before dialing a TCP address, which would lead to a regression for these users.
  • Similarly, not all ISPs support IPv6 yet. This is problematic as well, since we prefer IPv6 addresses over IPv4.

This is why smart dialing was disabled by default in v0.28.

For this release, we implemented a logic we call Black Hole Detection in this release. We now detect if UDP or IPv6 is completely blocked (blackholed) by observing the outcomes of dial attempts. When a black hole is detected, we skip QUIC / WebTransport and IPv6 addresses, respectively. This significantly reduces the number of unsuccessful dials for users in these environments. To monitor the status of black hole detection, we added two Grafana dashboards to our swarm dashboard, showing the percentage successful / failed dials on UDP and IPv6, and if that leads to our blackhole logic kicking in.

This now allows us to use RFC8305 Happy Eyballs for QUIC: When we dial a peer that has a QUIC IPv6 and IPv4 address, we dial the IPv6 address first, and only start dialing the IPv4 address if we haven’t heard back from the peer within 250ms. Only if we don’t hear back within another 250ms, we start dialing on TCP.

In a future release, we will enable a similar logic for TCP IPv6 and IPv4 addresses, however, this will require us to refactor our code a bit (see #2394 for details).

Preliminary measurements on the IPFS network show that:

  • In ~90% of the cases, we end up with a connection on the first address we dial.
  • Canceled connection attempts are reduced by more than 60% (compared to the v0.27 release).

Smart Dialing is now enabled by default. We don’t expect it to cause any performance regression, but if you find any problems, please open an issue. It can be disabled via a constructor option to libp2p.New:

libp2p.SwarmOpts(swarm.WithDialRanker(swarm.NoDelayDialRanker))

Metrics

  • It's now possible to spin up a local Grafana dashboards - with all libp2p dashboards imported and ready to go - by just running docker-compose up in the dashboards directory: #2383.
  • Resource Manager metrics are now enabled by default: #2370.

Changelog

Read more

Contributors

ajsutton, SahibYar, and sysvm
Assets 2
Loading

v0.28.1

20 Jun 16:13
@github-actions github-actions
v0.28.1
c358b81
Compare
Choose a tag to compare
v0.28.1

What's Changed

  • fix: in the swarm move Connectedness emit after releasing conns #2373
  • identify: set stream deadlines for Identify and Identify Push streams #2382

Full Changelog: v0.28.0...v0.28.1

Assets 2
Loading

v0.27.7

19 Jun 20:53
@github-actions github-actions
v0.27.7
68ad5ea
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.27.7

What's Changed

  • fix: in the swarm move Connectedness emit after releasing conns #2373
  • identify: set stream deadlines for Identify and Identify Push streams #2382

Full Changelog: v0.27.6...v0.27.7

Assets 2
Loading

v0.28.0

12 Jun 18:02
@github-actions github-actions
v0.28.0
703c3a4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.28.0

🔦 Highlights

Smart Dialing

This release introduces smart dialing logic. Currently, libp2p dials all addresses of a remote peer in parallel, and
aborts all outstanding dials as soon as the first one succeeds.
Dialing many addresses in parallel creates a lot of churn on the client side, and unnecessary load on the network and
on the server side, and is heavily discouraged by the networking community (see RFC 8305 for example).

When connecting to a peer we first determine the order to dial its addresses. This ranking logic considers a number of corner cases
described in detail in the documentation of the swarm package (swarm.DefaultDialRanker).
At a high level, this is what happens:

  • If a peer offers a WebTransport and a QUIC address (on the same IP:port), the QUIC address is preferred.
  • If a peer has a QUIC and a TCP address, the QUIC address is dialed first. Only if the connection attempt doesn't succeed within 250ms, a TCP connection is started.

Our measurements on the IPFS network show that for >90% of established libp2p connections, the first connection attempt succeeds,
leading a dramatic decrease in the number of aborted connection attempts.

We also added new metrics to the swarm Grafana dashboard, showing:

  • The number of connection attempts it took to establish a connection
  • The delay introduced by the ranking logic

This feature should be safe to enable for nodes running in data centers and for most nodes in home networks.
However, there are some (mostly home and corporate networks) that block all UDP traffic. If enabled, the current implementation
of the smart dialing logic will lead to a regression, since it preferes QUIC addresses over TCP addresses. Nodes would still be
able to connect, but connection establishment of the TCP connection would be delayed by 250ms.

In a future release (see #1605 for details), we will introduce a feature called blackhole detection. By observing the outcome of
QUIC connection attempts, we can determine if UDP traffic is blocked (namely, if all QUIC connection attempts fail), and stop
dialing QUIC in this case altogether. Once this detection logic is in place, smart dialing will be enabled by default.

More Metrics!

Since the last release, we've added metrics for:

WebTransport

  • #2251: Infer public WebTransport address from quic-v1 addresses if both transports are using the same port for both quic-v1 and WebTransport addresses.
  • #2271: Only add certificate hashes to WebTransport mulitaddress if listening on WebTransport

Housekeeping updates

  • Identify
    • #2303: Don't send default protocol version
    • Prevent polluting PeerStore with local addrs
      • #2325: Don't save signed peer records
      • #2300: Filter received addresses based on the node's remote address
  • WebSocket
    • #2280: Reverted back to the Gorilla library for WebSocket
  • NAT
    • #2248: Move NAT mapping logic out of the host

🐞 Bugfixes

New Contributors

Full Changelog: v0.27.0...v0.28.0

Contributors

chaitanyaprem
Assets 2
Loading

v0.27.6

12 Jun 18:56
@github-actions github-actions
v0.27.6
2df518f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.
Compare
Choose a tag to compare
v0.27.6

What's Changed

  • Clean up stream scope in case of error

Full Changelog: v0.27.5...v0.27.6

Assets 2
Loading