Skip to content
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.

Sign up for GitHub

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

Jump to bottom

64-bit MACs #13

Open
lipnitsk opened this issue Aug 26, 2014 · 0 comments
Open

64-bit MACs #13

lipnitsk opened this issue Aug 26, 2014 · 0 comments
Labels
2.x candidate

Comments

@lipnitsk
Copy link

From: https://defuse.ca/audits/encfs.htm

Exploitability: Low
Security Impact: Medium

EncFS uses 64-bit MACs. This is not long enough, as they can be forged in 2^64 time, which is feasible today.

EncFS should use (at least) 128-bit MACs.
@jetwhiz jetwhiz mentioned this issue Mar 20, 2016
Open
@benrubson benrubson mentioned this issue Mar 20, 2017
Closed
@benrubson benrubson mentioned this issue Mar 10, 2018
Open
@taz-007 taz-007 mentioned this issue May 21, 2018
Closed
lukateras added a commit to prism-break/prism-break that referenced this issue Jan 15, 2019
@lukateras
Remove EncFS
c4e8b79 
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
Assignees
No one assigned
Labels
2.x candidate
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lipnitsk @vgough