[Ndn-interest] repo-ng and least-authority storage

[Corbin]

Oh, I forgot redundancy! Let's say that I want to run three repos in different availability zones; can I have them all synchronize with each other somehow?
Peace,~ C.
------ Original message------From: CorbinDate: Tue, Jun 27, 2017 19:37To: ndn-interest at lists.cs.ucla.edu;Cc: Subject:[Ndn-interest] repo-ng and least-authority storage

    Hi,
I want to know if the following security design is provider-independent; that is, whether it still holds even if I don't trust the NDN nodes running repo-ng.

To make a cap for a file, generate a secret key and nonce, use libsodium to put the file in a box with the key and nonce, and finally, insert the box in a repo with a random name. The name, key, and nonce form a capability for the file; the capability is necessary and sufficient for file retrieval.
This is a lot less work than Tahoe-LAFS has to put in! Would it really work?
Peace,~ C.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20170627/bdbbef41/attachment.html>