-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Same Key Used for Encryption and Authentication #8
Labels
Comments
vgough
pushed a commit
that referenced
this issue
Mar 24, 2016
Forgot to update header declaration for CurrentInterface
vgough
pushed a commit
that referenced
this issue
Mar 24, 2016
Default to Block32 when choosing standard or paranoid mode on case-insensitive systems (Apple and Windows)
Closed
lukateras
added a commit
to prism-break/prism-break
that referenced
this issue
Jan 15, 2019
From the latest audit (https://defuse.ca/audits/encfs.htm): > EncFS is probably safe as long as the adversary only gets one copy of > the ciphertext and nothing more. EncFS is not safe if the adversary has > the opportunity to see two or more snapshots of the ciphertext at > different times. EncFS attempts to protect files from malicious > modification, but there are serious problems with this feature. vgough/encfs#8 vgough/encfs#9 (critical) vgough/encfs#10 vgough/encfs#11 vgough/encfs#13 vgough/encfs#16 vgough/encfs#17
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From: https://defuse.ca/audits/encfs.htm
Exploitability: Low
Security Impact: Low
EncFS uses the same key for encrypting data and computing MACs. This is generally considered to be bad practice.
EncFS should use separate keys for encrypting data and computing MACs.
The text was updated successfully, but these errors were encountered: