Hello, Here is a topic about Filename Initialization Vector Chaining.
I do not use it because I have directories with a huge amout of subdirectories and files, so I do not want to be impacted by the significant performance impact which directory renames involve. Could we think about a solution to give each object's name its own initialization vector but not based on its path ? This would help with the performance impact. About attacks, let's assume that the attacker knows that at a specific location of the encoded files' tree, there is an object called "myfile.txt". For example, he now knows that "myfile.txt" gives "p5aHkU3UCjr21t6pqz0wK8zIdbHAoTqO6jdTcLcocpMNg9" once encoded. Can he find out the key with associations like this ? - without Filename Initialization Vector Chaining enabled ? - even with Filename Initialization Vector Chaining enabled ? Thank you very much ! Best regards, Ben ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Encfs-users mailing list Encfs-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/encfs-users
