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?
_______________________________________________
dm-crypt mailing list
dm-crypt@xxxxxxxx
http://www.saout.de/mailman/listinfo/dm-crypt
