<html><head>
</head>
<body style="margin-bottom:45px">
<div style="font-size: 10pt;"><div dir="auto">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?</div><div dir="auto"><br></div><div id="LGEmailSignatureBox" dir="auto"><div dir="auto" font-size:9pt;"=""><i>Peace,</i></div><div dir="auto" font-size:9pt;"=""><i>~ C.</i></div></div></div><div style="font-size: 10pt;"><div id="LGEmailHeader" dir="auto"><div dir="auto"><br></div><div dir="auto">------ Original message------</div><div dir="auto"><b>From: </b>Corbin<cds@corbinsimpson.com></cds@corbinsimpson.com></div><div dir="auto"><b>Date: </b>Tue, Jun 27, 2017 19:37</div><div dir="auto"><b>To: </b><a href="mailto:ndn-interest@lists.cs.ucla.edu">ndn-interest@lists.cs.ucla.edu</a>;</div><div dir="auto"><b>Cc: </b></div><div dir="auto"><b>Subject:</b>[Ndn-interest] repo-ng and least-authority storage</div><div dir="auto"><br></div></div>
<div style="font-size: 10pt;"><div dir="auto">Hi,</div><div dir="auto"><span style="font-size: 10pt;"><br></span></div><div dir="auto"><span style="font-size: 10pt;">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.</span><br></div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">This is a lot less work than Tahoe-LAFS has to put in! Would it really work?</div><div dir="auto"><br></div><div id="LGEmailSignatureBox" dir="auto"><div dir="auto" font-size:9pt;"=""><i>Peace,</i></div><div dir="auto" font-size:9pt;"=""><i>~ C.</i></div></div></div>
</div>
</body></html>