Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update IPFS Kubo to 0.26.0 #34896

Closed
Jorropo opened this issue Dec 14, 2023 · 1 comment · Fixed by brave/brave-core-crx-packager#839
Closed

Update IPFS Kubo to 0.26.0 #34896

Jorropo opened this issue Dec 14, 2023 · 1 comment · Fixed by brave/brave-core-crx-packager#839
Assignees
Labels
feature/web3/ipfs OS/Desktop priority/P3 The next thing for us to work on. It'll ride the trains. QA/Yes release-notes/include

Comments

@Jorropo
Copy link

Jorropo commented Dec 14, 2023

cc @cypt4 @bbondy @autonome

Signed Binaries: https://dist.ipfs.tech/kubo/v0.26.0/
Release Notes: https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.26.md (ipfs/kubo#10259)

Important feature

Commands ipfs key sign and ipfs key verify

This allows the Kubo node to sign arbitrary bytes to prove ownership of a PeerID or an IPNS Name. To avoid signature reuse, the signed payload is always prefixed with libp2p-key signed message:.

These commands are also both available through the RPC client and implemented in client/rpc.

For more information see ipfs/kubo#10230.

This is required for #14774

@rebron rebron added QA/Yes release-notes/include priority/P3 The next thing for us to work on. It'll ride the trains. labels Dec 21, 2023
@hacdias
Copy link

hacdias commented Jan 22, 2024

@Jorropo can you bump this issue to Kubo 0.26.0? I don't think we need to open a new one since this hasn't been done yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/web3/ipfs OS/Desktop priority/P3 The next thing for us to work on. It'll ride the trains. QA/Yes release-notes/include
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

5 participants