You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With CryptoFS 2.1.0 exists a possibilty to restore orphaned directories. The only downside of this method (and also other health fixes of Diagnostic Results) is, that the for the fix important dirId is not present by looking only at the encrypted vault structure and hence all files inside the orphaned dir need new, arbitrary names.
After implementing #47, this problem can be solved by storing the directory ID within the dir node itself, simplyfing the retrieveal if the dirID and making also more fixes possible.
The text was updated successfully, but these errors were encountered:
Or alternatively (since xattr may not survive sync) we can store it in a dedicated file inside the dir. This may need encryption to prevent attackers to descramble the dir structure.
Regarding encryption: The dirId can be encrypted with the masterkey and the rootDir as AD. That way, we can always decrypt it and it is has the same protection level as everything else.
infeo
changed the title
Store (encrypted) DirectoryID in extended attributes of directory
Store (encrypted) DirectoryID inside of ciphertext directory
Mar 31, 2022
With CryptoFS 2.1.0 exists a possibilty to restore orphaned directories. The only downside of this method (and also other health fixes of Diagnostic Results) is, that the for the fix important dirId is not present by looking only at the encrypted vault structure and hence all files inside the orphaned dir need new, arbitrary names.
After implementing #47, this problem can be solved by storing the directory ID within the dir node itself, simplyfing the retrieveal if the dirID and making also more fixes possible.
The text was updated successfully, but these errors were encountered: