This shows you the differences between two versions of the page.
|
sw:encfs_creation [d-m-Y H:i] |
sw:encfs_creation [d-m-Y H:i] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== EncFS Creation ====== | ||
| + | |||
| + | <code> | ||
| + | $ encfs <encrypted-dir> <decrypted-dir> | ||
| + | Creating new encrypted volume. | ||
| + | Please choose from one of the following options: | ||
| + | enter "x" for expert configuration mode, | ||
| + | enter "p" for pre-configured paranoia mode, | ||
| + | anything else, or an empty line will select standard mode. | ||
| + | ?> x | ||
| + | |||
| + | Manual configuration mode selected. | ||
| + | The following cipher algorithms are available: | ||
| + | 1. AES : 16 byte block cipher | ||
| + | -- Supports key lengths of 128 to 256 bits | ||
| + | -- Supports block sizes of 64 to 4096 bytes | ||
| + | 2. Blowfish : 8 byte block cipher | ||
| + | -- Supports key lengths of 128 to 256 bits | ||
| + | -- Supports block sizes of 64 to 4096 bytes | ||
| + | 3. blowfish-compat : algorithm compatible with EncFS 0.2-0.6 | ||
| + | -- key length 160 bits | ||
| + | -- block size 64 bytes | ||
| + | |||
| + | Enter the number corresponding to your choice: 1 | ||
| + | |||
| + | Selected algorithm "AES" | ||
| + | |||
| + | Please select a key size in bits. The cipher you have chosen | ||
| + | supports sizes from 128 to 256 bits in increments of 64 bits. | ||
| + | For example: | ||
| + | 128, 192, 256 | ||
| + | Selected key size: 256 | ||
| + | |||
| + | Using key size of 256 bits | ||
| + | |||
| + | Select a block size in bytes. The cipher you have chosen | ||
| + | supports sizes from 64 to 4096 bytes in increments of 16. | ||
| + | Or just hit enter for the default (512 bytes) | ||
| + | |||
| + | filesystem block size: 512 | ||
| + | |||
| + | Using filesystem block size of 512 bytes | ||
| + | |||
| + | The following filename encoding algorithms are available: | ||
| + | 1. Block : Block encoding, hides file name size somewhat | ||
| + | 2. Null : No encryption of filenames | ||
| + | 3. Stream : Stream encoding, keeps filenames as short as possible | ||
| + | |||
| + | Enter the number corresponding to your choice: 1 | ||
| + | |||
| + | Selected algorithm "Block"" | ||
| + | |||
| + | Enable filename initialization vector chaining? | ||
| + | This makes filename encoding dependent on the complete path, | ||
| + | rather then encoding each path element individually. | ||
| + | This is normally desireable, therefor the default is Yes. | ||
| + | Any response that does not begin with 'n' will mean Yes: no | ||
| + | |||
| + | Enable per-file initialization vectors? | ||
| + | This adds about 8 bytes per file to the storage requirements. | ||
| + | It should not affect performance except possibly with applications | ||
| + | which rely on block-aligned file io for performance. | ||
| + | The default here is Yes. | ||
| + | Any response that does not begin with 'n' will mean Yes: yes | ||
| + | |||
| + | External chained IV disabled, as both 'IV chaining' | ||
| + | and 'unique IV' features are required for this option. | ||
| + | Enable block authentication code headers | ||
| + | on every block in a file? This adds about 12 bytes per block | ||
| + | to the storage requirements for a file, and significantly affects | ||
| + | performance but it also means [almost] any modifications or errors | ||
| + | within a block will be caught and will cause a read error. | ||
| + | The default here is No. | ||
| + | Any response that does not begin with 'y' will mean No: no | ||
| + | |||
| + | |||
| + | Configuration finished. The filesystem to be created has | ||
| + | the following properties: | ||
| + | Filesystem cipher: "ssl/aes", version 2:1:1 | ||
| + | Filename encoding: "nameio/block", version 3:0:1 | ||
| + | Key Size: 256 bits | ||
| + | Block Size: 512 bytes | ||
| + | Each file contains 8 byte header with unique IV data. | ||
| + | |||
| + | Now you will need to enter a password for your filesystem. | ||
| + | You will need to remember this password, as there is absolutely | ||
| + | no recovery mechanism. However, the password can be changed | ||
| + | later using encfsctl. | ||
| + | |||
| + | New Encfs Password: | ||
| + | Verify Encfs Password: | ||
| + | |||
| + | $ | ||
| + | </code> | ||