Re:Introducing the Keybase filesystem
by fapjacks on Saturday February 06, 2016 @05:23PM
(#11050238)
Are we THAT forgetful? http://kiledjian.com/main/2013/6/7/nsa-is-using-google-faceb...
Dropbox was listed on PRISM documents. Are you kidding me?
They could do client side encryption.
Their profitability depends on being able to dedupe and compress data across all customers. They would need to raise prices significantly to make client side encryption a built in feature.
You trust the end users to back up their private keys?
I don't care what other people do. I want client side encryption!
Re:Introducing the Keybase filesystem
by reitanqild on Friday February 05, 2016 @11:18AM
(#11042386)
Then use tarsnap already. Bonus: it is owned by our own cperciva.
tarsnap is nerdish, secure and reasonably priced for what it provides IIRC. Haven't used it though but expect someone would have yelled out here if it was bad. (In fact the only one I've seen bashing it was patio11, -because it was too cheap and too nerdish.)
Re:Introducing the Keybase filesystem
by cperciva on Saturday February 06, 2016 @08:35AM
(#11047701)
tptacek also complains that tarsnap is too nerdish. :-)
At least on Linux/OSX/Android, you can use encfs to have a encrypted directory tree.
Spideroak can do it without private keys to back up.
Re:Introducing the Keybase filesystem
by reitanqild on Friday February 05, 2016 @11:19AM
(#11042394)
Thanks for adding facts. Do they still have that questionable(?) politician on the board?
Edit to add link to EFF ratings: https://www.eff.org/who-has-your-back-government-data-reques...