Hello, According to the EncFS presentation, page 33 : http://www.arg0.net/encfs-presentation.pdf
>From what I understand, if an application reads a 512 bytes data block, and if >MAC (authentication code) is enabled, alignment with disk blocks will not be >preserved, and 2 blocks will be read from the disk, "instead" of one. Same thing of course if we talk about 4K data blocks on 4K block disks. So for alignment / performance purpose, authentication code should be turned off, as random bytes (0). This is the default configuration. What about per-file initialization vectors ? Per-file IV adds a file header (in which the IV is stored), leading into non-aligned IOs. However, per-file IV seems to be a must-have for security reasons. In addition, default configuration enables this option. So could we think about a solution to keep IOs aligned even with per-file IV option enabled ? Growing the header to the exact size of a block (512b, 4K... depending on the configured block size) ? Moving header at the end of the file, in the last data block (last block would then be data;padding;footer) ? Any other solution ? Is there any other EncFS configuration option (except MAC, random bytes and per-file IV) that would lead into non aligned IOs ? Thank you very much ! Best regards, Ben ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Encfs-users mailing list Encfs-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/encfs-users
