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
Hello,
Thanks for this amazing work.
It would be nice to have an option to encrypt files in place providing a key as argument.
That should be probably achievable with something like described here : https://kerkour.com/rust-file-encryption, apart from the tricky part of working out the real file size from the encrypted file size... and to store a generated per file nonce as an encrypted file header, so that the nonce is not the same for each file, but recoverable from the file itself...
Best regards.
The text was updated successfully, but these errors were encountered:
In case you could be interested anyway, I made a quick proof of concept here : https://github.com/nicolaspernoud/dufs/tree/encryption .
The key is all zeros (but easy to pass as arguments), there is lots of ugly unwraps, the non encrypted case is not catered for, the range header as well ... but the nonce is properly randomized and stored at the beginning of the file, and the decrypted file size is properly calculated...
Hello,
Thanks for this amazing work.
It would be nice to have an option to encrypt files in place providing a key as argument.
That should be probably achievable with something like described here : https://kerkour.com/rust-file-encryption, apart from the tricky part of working out the real file size from the encrypted file size... and to store a generated per file nonce as an encrypted file header, so that the nonce is not the same for each file, but recoverable from the file itself...
Best regards.
The text was updated successfully, but these errors were encountered: