[dm-crypt] LUKS and backdoors

.. ink .. mhogomchungu at gmail.com
Sun Oct 20 02:38:17 CEST 2013


There is a lot of commotion surrounding truecrypt's presence or lack of
backdoors and there are calls for its source code to be audited[1]

How the header is created and maintained seem to be the most obvious place
to put a backdoor as discussed in the linked article.

can the same be done with LUKS? can a propriety,closed source application
be able to create a LUKS header in a way that will allow it to secretly put
the master key "between gaps" in a header in a way that will still make the
header fully functional and cryptsetup will be able to open it without any
complains?

[1]
http://blog.cryptographyengineering.com/2013/10/lets-audit-truecrypt.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.saout.de/pipermail/dm-crypt/attachments/20131019/d8e856e0/attachment.html>


More information about the dm-crypt mailing list