Live data from Hacker News

UtahFS: Encrypted File Storage

blog.cloudflare.com

21–30 of 45 posts

Re: UtahFS: Encrypted File Storage

#21

They should use Peergos [1], which satisfies all their requirements. It's built on top of ipfs, encrypts metadata as well as data, and hides file sizes and directory structure too. A directory is indistinguishable from a small file. We can also use S3 compatible object storage, including allowing direct reads and writes from the browser. Disclaimer: I'm the founder. 1. https://github.com/peergos/peergos

Peergos doesn't hide access patterns as far as I can tell.

Re: UtahFS: Encrypted File Storage

#23
post #3

Love the idea of this. I've tried to use something similar (at least in function), called Cryptomator. However, Cryptomator would always choke on larger files or directories with thousands of items (e.g. my Google Photos gallery). Will be interested to see if this or another solution is what I'm looking for.

True, the messy bit with Cryptomator is that it's not really very easily to share files with others. I've found it more of a tool really for an individual to use. I find myself sometimes training people on it a recommending it to people and then switching them to something like Tresorit when they have problems.

Re: UtahFS: Encrypted File Storage

#24

They should use Peergos [1], which satisfies all their requirements. It's built on top of ipfs, encrypts metadata as well as data, and hides file sizes and directory structure too. A directory is indistinguishable from a small file. We can also use S3 compatible object storage, including allowing direct reads and writes from the browser. Disclaimer: I'm the founder. 1. https://github.com/peergos/peergos

Peergos doesn't hide access patterns as far as I can tell.

We use a similar structure to their oram, a merkle champ, with random labels. Some operations do move blocks to new labels, but reads currently don't because of the overhead as well as wanting to support multiple concurrent readers.

Re: UtahFS: Encrypted File Storage

#25
One way to achieve encrypted remote file storage is to combine Linux's EncFS² with some other type of remote storage protocol such as CIFS. The basic idea is to mount a CIFS volume from a server you don't trust with your unencrypted files, then you mount that directory again with EncFS to get to the unencrypted files.

The main drawbacks are that EncFS will not hide your directory structure and file sizes and also that not all of the EncFS vulnerabilities that were discovered in 2014 have been addressed with an EncFS 2.0 release.

--

² or one of its similar alternatives of course

Re: UtahFS: Encrypted File Storage

#26

There a couple of solutions that are fuse based and dealing with folder based encryption and gocryptfs has a page that compares them here[1]. It will be interesting to see how this project does against its competition. SiriKali[2] is a front end to a majority of these projects and it works on Linux, MACOS and windows. [1] https://nuetzlich.net/gocryptfs/comparison/ [2] https://mhogomchungu.github.io/sirikali/

[deleted]

Re: UtahFS: Encrypted File Storage

#27

For anyone thinking about playing with this, please make sure you note this line: > Keep in mind that this system is not used in production at Cloudflare: it’s a proof-of-concept that I built

That's right. The Research Team does all sorts of stuff. Some of it ends up as open source projects, some of it as production software.

Re: UtahFS: Encrypted File Storage

#28
post #5

Dropbox and Google could easily encrypt the files locally with your own key prior to uploading them to their servers. But of course they won't do that, because then how else will they mine your data? Also, you probably shouldn't trust them even if they did offer this anyway.

Sure, if you don't want search or sharing or 90% of the other features of Google Drive then encrypting on the client side makes great sense. For people who demand that their computers are useful, it doesn't make any sense.

Re: UtahFS: Encrypted File Storage

#29
post #5

Dropbox and Google could easily encrypt the files locally with your own key prior to uploading them to their servers. But of course they won't do that, because then how else will they mine your data? Also, you probably shouldn't trust them even if they did offer this anyway.

Also (and more charitably), I'm pretty sure at least Dropbox deduplicates files between customers.

If the key for the file is the hash of the file, which they encrypt with the user’s passphrase, they can prevent anyone who didn’t originally have the file from being able to read it, including themselves.

Re: UtahFS: Encrypted File Storage

#30
post #3

Love the idea of this. I've tried to use something similar (at least in function), called Cryptomator. However, Cryptomator would always choke on larger files or directories with thousands of items (e.g. my Google Photos gallery). Will be interested to see if this or another solution is what I'm looking for.

I just started using Cryptomator for sensitive files on a self-hosted NextCloud (since i access it via internet). The photos thing was an issue so I just sync those unencrypted and use Cryptomator for non-media files - i suppose if I had a photo that I wouldn't want exposed i'd just move it individually over.
Post reply on HN