https://github.com/cloudflare/utahfs

UtahFS is an encrypted storage system that provides a user-friendly FUSE drive backed by cloud storage.
https://github.com/cloudflare/utahfs

Last synced: 6 days ago
JSON representation

UtahFS is an encrypted storage system that provides a user-friendly FUSE drive backed by cloud storage.

• Host: GitHub
• URL: https://github.com/cloudflare/utahfs
• Owner: cloudflare
• License: bsd-3-clause
• Created: 2020-06-08T15:41:57.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2024-09-26T15:08:04.000Z (3 months ago)
• Last Synced: 2024-11-21T09:04:56.132Z (21 days ago)
• Language: Go
• Homepage:
• Size: 18.7 MB
• Stars: 815
• Watchers: 27
• Forks: 49
• Open Issues: 15
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-repositories - cloudflare/utahfs - UtahFS is an encrypted storage system that provides a user-friendly FUSE drive backed by cloud storage. (Go)
• awesome-starts - cloudflare/utahfs - UtahFS is an encrypted storage system that provides a user-friendly FUSE drive backed by cloud storage. (Go)

README

        
UtahFS

======

UtahFS is a state-of-the art encrypted storage solution, meant to be similar to

Dropbox. It has a FUSE binding that creates a synthetic drive on the user's

computer that they can interact with like an external hard-drive. Files stored

in the drive are uploaded to a cloud storage provider, which means the drive

will never run out of space and minimizes the likelihood of any files being

lost. However the files are encrypted such that the cloud storage provider knows

almost nothing about what's being stored.

Features

--------

1. **Interchangeable Storage Providers.** For storing data in the cloud, UtahFS

   uses *Object Storage*, which is cheap and commodified. Example providers

   include: AWS S3, Google Cloud Storage, Backblaze B2, and Wasabi.

2. **Very Very Strong Encryption.** The method of encryption hides the number of

   files, file names, file contents, individual file size, and prevents any

   modifications (including rollbacks!). The only information which is clearly

   leaked is the maximum archive size: archives grow to fit new data, but won't

   shrink if that data is deleted. Instead, that space is left allocated and

   will be re-used if needed in the future.

3. **Local Hardware allows Multiple Users and Improved Performance.** If the

   user has server-like hardware on their LAN (Raspberry Pi / Intel NUC), this

   can be used to coordinate multiple users operating in the same archive. It

   can also dramatically improve the performance of uploads, because a user can

   upload large amounts of already-encrypted data to the server over the fast

   local network, and let the server take over the much slower upload to the

   cloud provider.

4. **Archive Mode.** The client can be configured to guard against deleting or

   overwriting existing files, while still allowing new files to be created and

   old files to be moved around. This helps protect against accidental data

   loss.

5. **Oblivious RAM (ORAM).**  ORAM can be used to hide the access pattern of

   data from the cloud storage provider, so the provider only sees the *amount*

   data is accessed. *(Access pattern: Which pieces of data are being accessed,

   and whether the access was a read or write.)*

How to Use

----------

Setup documentation can be found in the `docs/` folder.

Future Work

-----------

1. **Reliability strategies for the WAL.** Changes are buffered in a local

   Write-Ahead Log (WAL) before being sent to the cloud storage provider. If the

   disk that the WAL is stored on fails, it could become very difficult to

   return the archive to a usable, partially-regressed state.