ipfs/kubo v0.28.0

on GitHub

• 💬 Discuss
• 🔦 Highlights
  • RPC client: removed deprecated DHT API
  • Gateway: /api/v0 is removed
  • Removed deprecated Object API commands
  • No longer publishes loopback and private addresses on DHT
  • Pin roots are now prioritized when announcing
• 📝 Changelog
• 👨‍👩‍👧‍👦 Contributors

Overview

RPC client: removed deprecated DHT API

The deprecated DHT API commands in the RPC client have been removed. Instead, use the Routing API.

Gateway: /api/v0 is removed

The legacy subset of the Kubo RPC that was available via the Gateway port and was deprecated is now completely removed. You can read more in #10312.

If you have a legacy software that relies on this behavior, and want to expose parts of /api/v0 next to /ipfs, use reverse-proxy in front of Kubo to mount both Gateway and RPC on the same port. NOTE: exposing RPC to the internet comes with security risk: make sure to specify access control via API.Authorizations.

Removed deprecated Object API commands

The Object API commands deprecated back in 2021 have been removed, except for object diff, object patch add-link and object patch rm-link, whose alternatives have not yet been built (see issues 4801 and 4782).

Kubo ignores loopback addresses on LAN DHT and private addresses on WAN DHT

Kubo no longer keeps track of loopback and private addresses on the LAN and WAN DHTs, respectively. This means that other nodes will not try to dial likely undialable addresses.

To support testing scenarios where multiple Kubo instances run on the same machine, Routing.LoopbackAddressesOnLanDHT is set to true when the test profile is applied.

Pin roots are now prioritized when announcing

The root CIDs of pinned content are now prioritized when announcing to the Amino DHT with Reprovider.Strategy set to all (default) or pinned, making the important CIDs accessible faster.

📝 Changelog

Security Note: CVE-2024-22189 has been addressed by upgrading to quic-go v0.42.0.

👨‍👩‍👧‍👦 Contributors