Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

A way to sign things using IPFS keys #2880

Closed
mitar opened this issue Mar 6, 2017 · 11 comments
Closed

A way to sign things using IPFS keys #2880

mitar opened this issue Mar 6, 2017 · 11 comments
Assignees
Labels
exp/novice Someone with a little familiarity can pick up kind/feature kind/maybe-in-helia kind/resolved-in-helia need/maintainer-input Needs input from the current maintainer(s)

Comments

@mitar
Copy link

mitar commented Mar 6, 2017

So each peer has its own key (and optional additional keys), but it seems there is no API which would allow one to sign messages using those keys (except by storing them inside IPNS).

@daviddias
Copy link
Member

@whyrusleeping thoughts?

@daviddias
Copy link
Member

This would require exposing a new API.

@daviddias
Copy link
Member

@richardschneider has been working a ton on the ipfs key API, he will have thoughts here :)

@richardschneider
Copy link
Contributor

Hopefully the Key API #1133 will be merged soon.

Then the options sign <key> and encrypt <key> can be added to file/block/message creation commands. They would generate a CMS structure, see richardschneider/ipfs-encryption#9

@alanshaw
Copy link
Member

alanshaw commented Dec 4, 2018

A bunch of folks have also requested signed pubsub messages.

@fiatjaf
Copy link

fiatjaf commented Dec 4, 2018

@adamskrodzki
Copy link

@richardschneider Is it merged? If so, where is documentation how to use it?

I would like to be able to sign some arbitrary data by one node private key, so it can be attributed forever to that node by any other node just by verification of signature.

@richardschneider
Copy link
Contributor

richardschneider commented Dec 12, 2018

To be frank, I did a interview with protocol labs and they never got back to me. After a month I reached out and got a "Oh sorry we don't need you response". This after a year+ of contributing to the projects.

I suggest you take a look at https://github.com/libp2p/js-libp2p-keychain

Also, https://github.com/richardschneider/ipfs-encryption contains my original designs and questions

@zicmama
Copy link

zicmama commented Jan 18, 2020

I wish to use keystore and node keys in other software
But I miss relation between
"PeerID": "Qm***" and "PrivKey" that can be found in ./.ipfs/config
And ed25519 keypair as in https://scuttlebot.io/more/protocols/secure-scuttlebutt.html

Any clarification is welcome.

@achingbrain achingbrain transferred this issue from ipfs-inactive/interface-js-ipfs-core Mar 10, 2020
@achingbrain achingbrain added kind/feature exp/novice Someone with a little familiarity can pick up labels Mar 10, 2020
@SgtPooki SgtPooki self-assigned this May 17, 2023
@SgtPooki SgtPooki moved this to 🥞 Todo in js-ipfs deprecation May 17, 2023
@SgtPooki
Copy link
Member

js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide.

Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterward (see #4336).

@achingbrain this sounds like something we should probably support in Helia. I'm not sure if it's already there, so assigning to you for either migrating this issue, creating new Helia specific issue for signing messages using keys in helia, or telling us it's already possible!

@SgtPooki SgtPooki assigned achingbrain and unassigned SgtPooki May 26, 2023
@SgtPooki SgtPooki moved this from 🥞 Todo to 🛑 Blocked in js-ipfs deprecation May 26, 2023
@SgtPooki SgtPooki added need/maintainer-input Needs input from the current maintainer(s) kind/maybe-in-helia labels May 26, 2023
@achingbrain
Copy link
Member

When you export a key from the libp2p keychain you can access the raw public/private keys so this is possible without an API change.

Closing as completed 👍

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/novice Someone with a little familiarity can pick up kind/feature kind/maybe-in-helia kind/resolved-in-helia need/maintainer-input Needs input from the current maintainer(s)
Projects
No open projects
Status: Done
Development

No branches or pull requests

10 participants