UtahFS: Encrypted File Storage
blog.cloudflare.com
UtahFS: Encrypted File Storage
1–10 of 45 posts
Re: UtahFS: Encrypted File Storage
#2Will keep an eye on this!
Re: UtahFS: Encrypted File Storage
#3Love 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.
Re: UtahFS: Encrypted File Storage
#4IPFS already has a storage and data layer as well as integrity and other properties. I wonder if it would be a good backend for this filesystem.
Re: UtahFS: Encrypted File Storage
#5Dropbox 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.
Re: UtahFS: Encrypted File Storage
#6Love 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.
Boxcryptor is a paid solution, similar to Cryptomator. I think I gave each one a try out on my phone, but ultimately just went back to using plain Google Drive and Google Photos. It fell into the category of "what is the real tangible benefit of this to me actually?" The real cost was added complexity, decreased reliability, a worse photos experience, and possibly another subscription cost.
Re: UtahFS: Encrypted File Storage
#7mtgx - you are dead.
I haven't looked at native OpenZFS encryption... The method I used for a while was having a Veracrypt volume locally of all my files, and zfs-sending it to a remote location. It is a large file, several gigabytes. However, any updates made locally would get synced remotely at a block level vs. a file level, so the whole encrypted file didn't need synced. Much better than rsync, for example.
I did not read the entire F'in article yet, I just stepped in while a CI/CD pipe was running at work :) BUT! this looks like a pretty accessible article about filesystems.
I also wonder if it is named UtahFS because of the NSA facility near Salt Lake City.
Re: UtahFS: Encrypted File Storage
#8IPFS already has a storage and data layer as well as integrity and other properties. I wonder if it would be a good backend for this filesystem.
Until your pk is compromised
Re: UtahFS: Encrypted File Storage
#9Love 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.
Thats also rather large. I have a cryptomator “vault” of approx 40 GB, performance on linux, windows and iOS seems fine.
Re: UtahFS: Encrypted File Storage
#10There 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.