Skip to content

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Mar 28, 2024

Bumps the go_modules group with 3 updates in the / directory: github.com/btcsuite/btcd, github.com/ipld/go-ipld-prime and github.com/libp2p/go-libp2p.

Updates github.com/btcsuite/btcd from 0.22.0-beta to 0.23.2

Release notes

Sourced from github.com/btcsuite/btcd's releases.

btcd v0.23.2

What's Changed

New Contributors

Full Changelog: btcsuite/btcd@v0.23.1...v0.23.2

btcd v0.23.1-beta

What's Changed

... (truncated)

Commits
  • 6b5418d Merge pull request #1898 from Roasbeef/v0-23-2-branch
  • 1a4af39 build: bump version to v0.23.2
  • d0aa747 Merge pull request #1896 from Roasbeef/witness-wire-hot-fix
  • f523d4c wire: remove erroneous witness size check in wire parsing
  • 38ee9a4 build: bump golang base image version to 1.17
  • ef4a8d3 doc: fix Tor hidden service setup link
  • 0f49e10 Merge pull request #1866 from darioush/bump-btcutils-versions
  • da4b534 Merge pull request #1865 from sputn1ck/musig2_0.3.0
  • 06ce960 btcec/schnorr/musig2: add infinity testvectors
  • 44eb8c6 btcec/schnorr/musig2: Allow infinity nonces
  • Additional commits viewable in compare view

Updates github.com/ipld/go-ipld-prime from 0.18.0 to 0.19.0

Release notes

Sourced from github.com/ipld/go-ipld-prime's releases.

v0.19.0

go-ipld-prime's release policy says that:

even numbers should be easy upgrades; odd numbers may change things

The only major, potentially disruptive change in this release is a bump to Go 1.18.

🛠 Breaking Changes

Update go.mod to Go 1.18.

🔦 Highlights

Changelog

Sourced from github.com/ipld/go-ipld-prime's changelog.

v0.19.0

2022 October 13

go-ipld-prime's release policy says that:

even numbers should be easy upgrades; odd numbers may change things

The major change in this release is a bump to Go 1.18.

🛠 Breaking Changes

Update go.mod to Go 1.18.

🔦 Highlights

Commits
  • ac99fc3 Prepare v0.19.0
  • 146d1c8 fix: correct json codec links & bytes handling
  • 7548eb8 build(deps): bump github.com/google/go-cmp from 0.5.8 to 0.5.9 (#468)
  • 4b84deb build(deps): bump github.com/ipfs/go-cid from 0.3.0 to 0.3.2 (#466)
  • a007538 build(deps): bump github.com/ipfs/go-cid in /storage/bsadapter (#465)
  • 6c3aeea build(deps): bump github.com/ipfs/go-cid in /storage/bsrvadapter (#464)
  • 8fd3dea test(basicnode): increase test coverage for int and map types (#454)
  • e57582f build(deps): bump github.com/ipfs/go-cid in /storage/bsrvadapter
  • 8572ef0 build(deps): bump github.com/ipfs/go-cid in /storage/bsadapter
  • e23acb3 build(deps): bump github.com/ipfs/go-cid from 0.2.0 to 0.3.0
  • Additional commits viewable in compare view

Updates github.com/libp2p/go-libp2p from 0.23.4 to 0.27.8

Release notes

Sourced from github.com/libp2p/go-libp2p's releases.

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: libp2p/go-libp2p#2454. The analogous vulnerability in go-libp2p's crypto package.
  • swarm: don't open new streams over transient connections: libp2p/go-libp2p#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: libp2p/go-libp2p@v0.27.7...v0.27.8

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: libp2p/go-libp2p@v0.27.6...v0.27.7

v0.27.6

What's Changed

  • Clean up stream scope in case of error

Full Changelog: libp2p/go-libp2p@v0.27.5...v0.27.6

v0.27.5

What's Changed

Full Changelog: libp2p/go-libp2p@v0.27.3...v0.27.5

v0.27.4

What's Changed

  • identify
    • Fixed an issue where we now avoid spuriously triggering pushes
    • Fixed an issue where signed peer records weren’t rejected if the signature didn’t match
  • swarm
    • Fixed duplicate tracking in dial worker loop

v0.27.3

This patch release contains a fix for a rare panic that occurs on Windows systems (backport of libp2p/go-libp2p#2276).

Full Changelog: libp2p/go-libp2p@v0.27.1...v0.27.3

v0.27.2

What's Changed

quic: fix race condition when generating random holepunch packet (libp2p/go-libp2p#2263) webtransport: initialize the certmanager when creating the transport (libp2p/go-libp2p#2268)

... (truncated)

Changelog

Sourced from github.com/libp2p/go-libp2p's changelog.

Table Of Contents

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

... (truncated)

Commits

Updates golang.org/x/crypto from 0.0.0-20220829220503-c86fa9a7ed90 to 0.7.0

Commits

Updates golang.org/x/net from 0.0.0-20220920183852-bf014ff85ad5 to 0.8.0

Commits

Updates golang.org/x/text from 0.3.8-0.20211105212822-18b340fc7af2 to 0.8.0

Commits

Updates google.golang.org/protobuf from 1.28.1 to 1.30.0

You can trigger a rebase of this PR 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps the go_modules group with 3 updates in the / directory: [github.com/btcsuite/btcd](https://github.com/btcsuite/btcd), [github.com/ipld/go-ipld-prime](https://github.com/ipld/go-ipld-prime) and [github.com/libp2p/go-libp2p](https://github.com/libp2p/go-libp2p).


Updates `github.com/btcsuite/btcd` from 0.22.0-beta to 0.23.2
- [Release notes](https://github.com/btcsuite/btcd/releases)
- [Changelog](https://github.com/btcsuite/btcd/blob/master/CHANGES)
- [Commits](btcsuite/btcd@v0.22.0-beta...v0.23.2)

Updates `github.com/ipld/go-ipld-prime` from 0.18.0 to 0.19.0
- [Release notes](https://github.com/ipld/go-ipld-prime/releases)
- [Changelog](https://github.com/ipld/go-ipld-prime/blob/master/CHANGELOG.md)
- [Commits](ipld/go-ipld-prime@v0.18.0...v0.19.0)

Updates `github.com/libp2p/go-libp2p` from 0.23.4 to 0.27.8
- [Release notes](https://github.com/libp2p/go-libp2p/releases)
- [Changelog](https://github.com/libp2p/go-libp2p/blob/master/CHANGELOG.md)
- [Commits](libp2p/go-libp2p@v0.23.4...v0.27.8)

Updates `golang.org/x/crypto` from 0.0.0-20220829220503-c86fa9a7ed90 to 0.7.0
- [Commits](https://github.com/golang/crypto/commits/v0.7.0)

Updates `golang.org/x/net` from 0.0.0-20220920183852-bf014ff85ad5 to 0.8.0
- [Commits](https://github.com/golang/net/commits/v0.8.0)

Updates `golang.org/x/text` from 0.3.8-0.20211105212822-18b340fc7af2 to 0.8.0
- [Release notes](https://github.com/golang/text/releases)
- [Commits](https://github.com/golang/text/commits/v0.8.0)

Updates `google.golang.org/protobuf` from 1.28.1 to 1.30.0

---
updated-dependencies:
- dependency-name: github.com/btcsuite/btcd
  dependency-type: indirect
  dependency-group: go_modules-security-group
- dependency-name: github.com/ipld/go-ipld-prime
  dependency-type: indirect
  dependency-group: go_modules-security-group
- dependency-name: github.com/libp2p/go-libp2p
  dependency-type: indirect
  dependency-group: go_modules-security-group
- dependency-name: golang.org/x/crypto
  dependency-type: indirect
  dependency-group: go_modules-security-group
- dependency-name: golang.org/x/net
  dependency-type: indirect
  dependency-group: go_modules-security-group
- dependency-name: golang.org/x/text
  dependency-type: indirect
  dependency-group: go_modules-security-group
- dependency-name: google.golang.org/protobuf
  dependency-type: indirect
  dependency-group: go_modules-security-group
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants