Closed nondedjeu closed 5 years ago
To answer myself, just had to delete all .lng
files that were ≤ 66 bytes and decryptVault then completed successfully.
(not sure about the "66" value, you should double-check that before proceeding)
A well-formatted 0-byte file has 88 ciphertext bytes, a 1-byte file at least 137 bytes (Source).
So the real magic number here should be < 88
Hi, While using sanitizer's decryptVault command, many files are successfully getting decrypted but sometimes the process crashes with a similar exception stack as below. A workaround consists of manually deleting the source file on which the process crashed, and restart the whole decryptVault process (which takes hours on my large vault) until the process crashes on another file, etc... Is there a way to anticipate on which files the process will crash, in order to delete these files upfront ? Or a way to tell sanitizer to only log these exceptions in a log file but keep processing the next files ?