ipfs/kubo v0.19.1

on GitHub

• 💬 Discuss
• 🔦 Highlights
  • Improving the libp2p resource management integration
  • Gateways
    • Signed IPNS Record response format
    • Example fetch and inspect IPNS record
  • Addition of "autoclient" router type
  • Deprecation of the ipfs pubsub commands and matching HTTP endpoints
• 📝 Changelog
• 👨‍👩‍👧‍👦 Contributors

Overview

🔦 Highlights

Improving the libp2p resource management integration

There are further followups up on libp2p resource manager improvements in Kubo 0.18.0
and 0.18.1:

1. ipfs swarm limits and ipfs swarm stats have been replaced by ipfs swarm resources to provide a single/combined view for limits and their current usage in a more intuitive ordering.
2. Removal of Swarm.ResourceMgr.Limits config. Instead the power user can specify limits in a .json file that are fed directly to go-libp2p. This allows the power user to take advantage of the new resource manager types introduced in go-libp2p 0.25 including "use default", "unlimited", "block all".
   • Note: we don't expect most users to need these capablities, but they are there if so.
3. Doc updates.

Gateways

Signed IPNS Record response format

This release implements IPIP-351 and
adds Gateway support for returning signed (verifiable) ipns-record (0x0300)
when /ipns/{libp2p-key} is requested with either
Accept: application/vnd.ipfs.ipns-record HTTP header
or ?format=ipns-record URL query parameter.

The Gateway in Kubo already supported trustless, verifiable retrieval of immutable /ipfs/ namespace.
With ?format=ipns-record, light HTTP clients are now able to get the same level of verifiability for IPNS websites.

Tooling is limited at the moment, but we are working on go-libipfs examples that illustrate the verifiable HTTP client pattern.

Example: fetch IPNS record over HTTP and inspect it with ipfs name inspect --verify

$ FILE_CID=$(echo "Hello IPFS" | ipfs add --cid-version 1 -q)
$ IPNS_KEY=$(ipfs key gen test)
$ ipfs name publish /ipfs/$FILE_CID --key=test --ttl=30m
Published to k51q..dvf1: /ipfs/bafk..z244
$ curl "http://127.0.0.1:8080/ipns/$IPNS_KEY?format=ipns-record" > signed.ipns-record
$ ipfs name inspect --verify $IPNS_KEY < signed.ipns-record
Value:         "/ipfs/bafk..."
Validity Type: "EOL"
Validity:      2023-03-09T23:13:34.032977468Z
Sequence:      0
TTL:           1800000000000
PublicKey:     ""
Signature V1:  "m..."
Signature V2:  "m..."
Data:          {...}

Validation results:
 Valid:     true
 PublicKey: 12D3...

Addition of "autoclient" router type

A new routing type "autoclient" has been added. This mode is similar to "auto", in that it is a hybrid of content routers (including Kademlia and HTTP routers), but it does not run a DHT server. This is similar to the difference between "dhtclient" and "dht" router types.

See the Routing.Type documentation for more information.

Deprecation of the ipfs pubsub commands and matching HTTP endpoints

We are deprecating ipfs pubsub and all /api/v0/pubsub/ RPC endpoints and will remove them in the next release.

For more information and rational see #9717.

📝 Changelog

👨‍👩‍👧‍👦 Contributors