It’s extremely easy to fuck up cryptography code; you require both extraordinary mathematical insight and the programming skills to defend against every known and future side-channel attack. I would suggest instead trusting software where you can read the source yourself, and which has been openly reviewed by a selection of experts in the field.
I don’t mean I wrote the cryptography implementation, I mean I wrote the code that uses it to encrypt my files. Yeah, I don’t trust myself to implement AES, but I also don’t trust others to use it correctly.
For anything I want to actually keep private, I only trust the software that I wrote. But LUKS is good enough for most stuff.
It’s extremely easy to fuck up cryptography code; you require both extraordinary mathematical insight and the programming skills to defend against every known and future side-channel attack. I would suggest instead trusting software where you can read the source yourself, and which has been openly reviewed by a selection of experts in the field.
I don’t mean I wrote the cryptography implementation, I mean I wrote the code that uses it to encrypt my files. Yeah, I don’t trust myself to implement AES, but I also don’t trust others to use it correctly.