>>> Issues 2.2 and 2.3, as well as reference [2] could be solved by using >>> random bytes. >>> How can this feature be enabled ? >> >> Random bytes won't solve reference [2] because the same amount of random >> bytes (proportionally) will be added to each file, so you can still >> figure out the relative sizes of files in a directory, and the number of >> files in a directory. > > You’re right. > I thought that random bytes were used as a padding for the last partial data > block. But no :) > > So, a solution could to use a block instead of a stream for the last > (partial) data block. > The last partial block could be padded with random bytes, zeros… > I don’t know wether number of blocks used in a file is stored in its EncFS > header or not, but if it is, it could be replaced by its size, so that the > end of the file data in the last block is known. > Stream mode would then not be used at all, which would solve issues 2.2 and > 2.3. > > It would also solve reference [2] as encoded files' size would not be the > real files’ size but a multiple of the block size. > By "chance" it could be the real files' size, but not necessarily.
Taylor, do you think it could be a solution ? Many thanks ! Ben ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Encfs-users mailing list Encfs-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/encfs-users
