Skip to content
This repository has been archived by the owner. It is now read-only.

Decoupled serving and signing #117

Closed
omphalos opened this issue May 10, 2016 · 1 comment
Closed

Decoupled serving and signing #117

omphalos opened this issue May 10, 2016 · 1 comment

Comments

@omphalos
Copy link

omphalos commented May 10, 2016

For mutable storage, my understanding is that you run a server, and this server signs pointers to content-addressed IPFS entries.

Is it possible for one party (such as a web browser, mobile device, IoT device) to sign a pointer and publish this signed pointer over IPFS via a willing intermediary? For example: a web application signs a message pointing their key to such-and-such content, then sends this signed pointer to an IPFS node. Then this IPFS node publishes this signed pointer on the application's behalf over IPNS. (This would all be done in a way such that the IPFS/IPNS node does not have knowledge of the private key managed by the web application.)

In case this is not possible, is there any plan to make it possible in the future?

@flyingzumwalt
Copy link
Contributor

flyingzumwalt commented May 23, 2017

This issue was moved to https://discuss.ipfs.io/t/decoupled-serving-and-signing/398

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants