> DeLUKS
Interesting, hadn't seen this project yet, or would have been more careful, thanks.
A few thoughts:
- The lack of a link to a white paper makes DeLUKS difficult to analyze, but it looks like they're hashing the password using PBKDF2-SHA1, which is quite outdated. (PUREE uses argon2id.)
- The installation/usage seems slightly complex. I'd suggest people compare to the PUREE quick start instructions.
> TrueCrypt/VeraCrypt
As per your link: "When you create an encrypted volume using TrueCrypt or VeraCrypt it is stored as a file (container) on your hard drive.".
And as per VeraCrypt's wikipedia page: "VeraCrypt supports plausible deniability[16] by allowing a single "hidden volume" to be created within another volume"
I didn't read too much deeper, but the phrases "stored in a file" and "hidden volume within another volume" are red flags.
Interesting, hadn't seen this project yet, or would have been more careful, thanks.
A few thoughts:
- The lack of a link to a white paper makes DeLUKS difficult to analyze, but it looks like they're hashing the password using PBKDF2-SHA1, which is quite outdated. (PUREE uses argon2id.)
- The installation/usage seems slightly complex. I'd suggest people compare to the PUREE quick start instructions.
> TrueCrypt/VeraCrypt
As per your link: "When you create an encrypted volume using TrueCrypt or VeraCrypt it is stored as a file (container) on your hard drive.".
And as per VeraCrypt's wikipedia page: "VeraCrypt supports plausible deniability[16] by allowing a single "hidden volume" to be created within another volume"
I didn't read too much deeper, but the phrases "stored in a file" and "hidden volume within another volume" are red flags.