On Sun, Jul 15, 2012 at 5:50 PM, Tony Arcieri <[email protected]> wrote: > On Sun, Jul 15, 2012 at 5:34 PM, David Barrett <[email protected]> > wrote: >> >> 1) What is the UI? Is this a command-line tool or is there a GUI? (I >> actually hope it's just a command-line tool; I like the idea of >> separating file transport from searching and viewing/playback.) > > I'm shooting for both a CLI and a realtime web UI using Websockets.
Awesome. For the CLI, what's the general idea? Is it something like: $ apt-get install cryptosphere $ cryptosphere put <filename> Success, stored as: <encryptedSHA> <publicSHA> $ cryptosphere get <encryptedSHA> <publicSHA> Success, saved to: <filename> >> 2) This seems a great storage and transport system. But why does it >> also do encryption? Don't get me wrong -- encryption is great. But >> why insist that it be used for all content -- why not allow me to just >> publish an unencrypted file (or a file encrypted with a different >> algorithm)? > > I'd like to go to extreme lengths to maximize obscurity for outside > observers of the system. I guess it's just a philosophical thing. I agree with that goal, but I'd argue that usability trumps that: I'd rather have a less-secure system that people use, than a more-secure system that people don't use. Again, I don't know the usability tradeoff that the encryption causes: ideally it'd be so under the hood (like Skype) that you wouldn't even know it's happening. But if my above guess about the CLI syntax is right, then it means everybody who stores a file into the system must hold on to not one, but *two* extremely long hex numbers in order to fetch the file. This feels unwieldly. Or is this all off? -david _______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
