-
Notifications
You must be signed in to change notification settings - Fork 300
Hi, I am currently playing around with using the file ids as a persistent identifier for sth else. Thus, in my case, empty files already have a file id.
Anyways, I was very suprised that gocryptfs aggressively removes file headers whenever sth is truncated to 0. In particular, I found
gocryptfs/internal/fusefrontend/file.go
Line 91 in 33fa0b5
What exactly is the risk of file id poisioning? Is it about like setting it to all zeroes in order to invalidate the strength of the AAD or sth? I never formally had a cryptography lecture...
All reactions
This was found in the security audit, it's explained in section 2.2 here: https://defuse.ca/downloads/audits/gocryptfs-cryptography-design-audit.pdf
Replies: 1 comment 1 reply
This was found in the security audit, it's explained in section 2.2 here: https://defuse.ca/downloads/audits/gocryptfs-cryptography-design-audit.pdf
All reactions
Sorry for the annoyance, I don't know how I missed that one, will read the audit back to back later today! Thanks!