ipfs/kubo v0.27.0

on GitHub

• 💬 Discuss
• 🔦 Highlights
  • Gateway: support for /api/v0 is deprecated
  • IPNS resolver cache's TTL can now be configured
  • RPC client: deprecated DHT API, added Routing API
  • Deprecated DHT commands removed from /api/v0/dht
  • Repository migrations are now trustless
• 📝 Changelog
• 👨‍👩‍👧‍👦 Contributors

Overview

🔦 Highlights

Gateway: support for /api/v0 is deprecated

Support for exposing the legacy subset of Kubo RPC via the Gateway port is deprecated and should not be used. It will be removed in the next version. 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.

IPNS resolver cache's TTL can now be configured

You can now configure the upper-bound of a cached IPNS entry's Time-To-Live via Ipns.MaxCacheTTL.

RPC client: deprecated DHT API, added Routing API

The RPC client for GO (kubo/client/rpc) now includes a Routing API to match the available commands in /api/v0/routing. In addition, the DHT API has been marked as deprecated.

In the next version, all DHT deprecated methods will be removed from the Go RPC client.

Deprecated DHT commands removed from /api/v0/dht

All the DHT commands that were deprecated for over a year were finally removed from /api/v0/dht. Users should switch to modern /api/v0/routing which works with both Amino DHT and Delegated Routers.

Repository migrations are now trustless

Kubo now only uses trustless requests (e.g., CAR files) when downloading repository migrations via HTTP. This further strengthens Kubo by not delegating trust to public gateways. The migration binaries are locally verified before being executed.

📝 Changelog

👨‍👩‍👧‍👦 Contributors