Unable to decode files (WARNING MAC comparison failure in block 0) #559

Activity

1. rfjakob commented on Oct 12, 2019

   

   rfjakob

   on Oct 12, 2019

   Collaborator

   More actions

   Did you have a crash / network drive disconnect / some other problems during moving the folders?
2. bpavacic commented on Oct 14, 2019

   

   bpavacic

   on Oct 14, 2019

   Author

   More actions

   Hi,
   it turned out to be related to "filename to IV header chaining" #141 (externalIVChaining=1). I recently had to recover the (encrypted) contents from Google Drive using Insync on Ubuntu and Insync failed to pick up and re-upload files that I have moved around.

   I have managed to recover some of the files by moving encrypted versions back to their original folders if I could recall where it was. I have pulled some files from a backup hard drive literally on another continent. Lots of scripting and manual work was involved.

   Can you please confirm that the following configuration will have atomic moves (underlying FS move only with no re-encryption or modifications to encrypted files)?

   <?xml version="1.0" encoding="UTF-8"?>
   <!DOCTYPE boost_serialization>
   <boost_serialization signature="serialization::archive" version="7">
       <cfg class_id="0" tracking_level="0" version="20">
           <version>20100713</version>
           <creator>EncFS 1.9.5</creator>
           <cipherAlg class_id="1" tracking_level="0" version="0">
               <name>ssl/aes</name>
               <major>3</major>
               <minor>0</minor>
           </cipherAlg>
           <nameAlg>
               <name>nameio/block</name>
               <major>4</major>
               <minor>0</minor>
           </nameAlg>
           <keySize>192</keySize>
           <blockSize>1024</blockSize>
           <plainData>0</plainData>
           <uniqueIV>1</uniqueIV>
           <chainedNameIV>1</chainedNameIV>
           <externalIVChaining>0</externalIVChaining>
           <blockMACBytes>0</blockMACBytes>
           <blockMACRandBytes>0</blockMACRandBytes>
           <allowHoles>1</allowHoles>
           <encodedKeySize>44</encodedKeySize>
           <encodedKeyData>
   zFbACkpuua9MZskQ3GDSeu1FABmsRyUQivpV6fDvgNAf8W6FwCk8Rfkbdus=
   </encodedKeyData>
           <saltLen>20</saltLen>
           <saltData>
   BsqlwEXlr9qwTfq7ZT8+XmgG2Fg=
   </saltData>
           <kdfIterations>398411</kdfIterations>
           <desiredKDFDuration>500</desiredKDFDuration>
       </cfg>
   </boost_serialization>
   
   
3. benrubson commented on Oct 26, 2019

   

   benrubson

   on Oct 26, 2019

   Contributor

   More actions

   No modification to files' content, but filenames may change, see man note on Filename Initialization Vector Chaining which is activated in your configuration.

   👍React with 👍1Reacted by Boris Pavacic
4. bpavacic commented on Oct 30, 2019

   

   bpavacic

   on Oct 30, 2019

   Author

   More actions

   Closing the issue as encfs is working as intended. It is just something worth keeping in mind when using tools synchronizing encrypted files to the cloud.
5. bpavacic

   closed this as completedon Oct 30, 2019
6. hrunting

   added 2 commits that reference this issue on Nov 11, 2022

   Squashed 'vendor/github.com/google/benchmark/' changes from 5b7683f4.…

   ...

   8e7e676

   Squashed 'vendor/github.com/muflihun/easyloggingpp/' changes from 468…

   ...

   b353ce4