Live data from Hacker News

Show HN: End-to-End Encrypted Cloud Storage. All Open Source

disk42.com

1–10 of 43 posts

Re: Show HN: End-to-End Encrypted Cloud Storage. All Open Source

#6
"All of our code is open source and can be reviewed by anyone. This guarantees maximum security."

Can be reviewed doesn't mean has been reviewed. Nor does it imply any quality of review, or the quality of the reviewers itself.

And the knife cuts on two sides, though only one side is mentioned, the one side that should attract users. Not the side, that every evil minded person can look through the source code, abuse it, before we were able to counter/fix etc it.

Re: Show HN: End-to-End Encrypted Cloud Storage. All Open Source

#9
post #5

Can you explain how the data is encrypted? Why so you only support Ubuntu Linux? It doesn't run on other distros?

I'm guessing they had to start somewhere, and that support for other distros will follow probably after they've implemented support for mobiles.

Re: Show HN: End-to-End Encrypted Cloud Storage. All Open Source

#10
This is awesome. End-to-end encryption is the natural solution to the problem of universal surveillance as well as more mundane issues, like companies losing data and servers getting hacked. I think it's very elegant that one can build useful services with untrusted servers.

The algorithms for end-to-end encryption are there, but usability of actual implementations has been pretty terrible so far. For example, compare the usability of Gmail vs Thunderbird+Enigmail. Or compare the usability of Dropbox and Tarsnap. I've actually wondered why there isn't a good end-to-end encrypted Dropbox alternative that's remotely as easy to use. I hope this works out.

Beautiful, usable end-to-end encrypted software is the future. See, for example, Keybase, @moxie's Signal or Whatsapp. The only caveat is that writing secure software is really hard. I just made a disk42 account, but I'll treat it as a untrusted demo until it's had more test mileage and outside code review.

Also, curious:

* How do you detect changes in the synced folder?

* How do you do conflict resolution (if a file is edited simultaneously on two different client machines)?

* What algorithms, key sizes, etc do you use for the actual encryption?

Post reply on HN