I don't know if this feature is already implemented...
I looked at the VC documentation but found nothing;
If I understand well, an Evil Maid Attack is the replacement of the VC Boot sector with a tampered one, which first does its magic and then goes normally on with Pre-Boot authentication and what follows...
A way to check/avoid this could be to store a copy of the untampered sector within the encrypted volume, and compare it (once the system has booted) with the current boot sector; this way the user can be sure about his system.
Is this feature already existing (so the question is silly), is it on the wishlist, or is it not possible to implement it?
Thank you ,
AE
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know if this feature is already implemented...
I looked at the VC documentation but found nothing;
If I understand well, an Evil Maid Attack is the replacement of the VC Boot sector with a tampered one, which first does its magic and then goes normally on with Pre-Boot authentication and what follows...
A way to check/avoid this could be to store a copy of the untampered sector within the encrypted volume, and compare it (once the system has booted) with the current boot sector; this way the user can be sure about his system.
Is this feature already existing (so the question is silly), is it on the wishlist, or is it not possible to implement it?
Thank you ,
AE
Hi AE,
Yes the VeraCrypt Boot Loader tampering detection has been implemented starting with 1.12 version on August 5, 2015.
Go to the Release Notes and using your browser search website function, search for Evil.
https://veracrypt.jp/en/Release%20Notes.html
Last edit: Enigma2Illusion 2026-08-18
Wonderful!
(so in the end, it was an almost silly question...)
Thank you very much!