🆕 Software Suggestion | CryFS #1631

New Issue

2020-01-05T00:40:41Z

totikom commented

2020-01-05 00:40:41 +00:00

(Migrated from github.com)

Basic Information

Name: CryFS
Category: File encryption
URL: https://www.cryfs.org/

Description

Unlike EncFS, Cryptomator and ECryptFS, cryfs encrypts not individual files but same sized chunks, which keeps file sizes, metadata and directory structure confidential.
It's theoretical security was shown in this paper and master's thesis of the author.

From the site:

To hide file sizes, CryFS splits the content of a file into same-size blocks and encrypts these blocks individually. A tree structure is used to remember how the blocks belong together to form a file. This tree structure has very little overhead and itself is also stored using encrypted same-size blocks. To hide file metadata and directory structure, they are also represented using encrypted same-size blocks.
Each encrypted block is stored as a file in the base directory, using a random ID as filename. The base directory can then be set up to be synchronized with a cloud provider like Dropbox. An attacker with access to the base directory can only see a set of same-size ciphertext blocks and can't see contents, file sizes, metadata or directory structure of your data.

## Basic Information **Name:** CryFS **Category:** File encryption **URL:** https://www.cryfs.org/ ## Description Unlike EncFS, Cryptomator and ECryptFS, ```cryfs``` encrypts not individual files but same sized chunks, which keeps file sizes, metadata and directory structure confidential. It's theoretical security was shown in this [paper](https://link.springer.com/chapter/10.1007%2F978-3-319-61176-1_23) and master's [thesis](https://www.cryfs.org/cryfs_mathesis.pdf) of the author. From the site: > To hide file sizes, CryFS splits the content of a file into same-size blocks and encrypts these blocks individually. A tree structure is used to remember how the blocks belong together to form a file. This tree structure has very little overhead and itself is also stored using encrypted same-size blocks. To hide file metadata and directory structure, they are also represented using encrypted same-size blocks. > Each encrypted block is stored as a file in the base directory, using a random ID as filename. The base directory can then be set up to be synchronized with a cloud provider like Dropbox. An attacker with access to the base directory can only see a set of same-size ciphertext blocks and can't see contents, file sizes, metadata or directory structure of your data.

lrq3000 commented

2020-02-02 16:04:39 +00:00

(Migrated from github.com)

Very interesting, although in early alpha stages. I particularly like the protection (both in terms of encryption and redundancy) of file and folders metadata against tampering, this is usually a point of failure in all files encryption schemes, and so encrypted files are easily lost. I did not try yet (I'm running Windows and these builds are still experimental - although available which is nice), but it's something to watch out for sure.

This repo is archived. You cannot comment on issues.

1 Participants

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1631