Re: Problem after detaching the header

> > Another solution that looks very interesting:
> > In a comment on stackexchange, someone suggested creating a dummy header instead of the original one, but using a detached one. Do you see any potential problems and is this a good idea?
> 
> 
> LUKS header after calling luksErase is actually "dummy" header (if it means header without keyslots).
I meant to go one step further and instead of luksErase create a fake header (bluff, decoy): Create a temporary container, make a header luksHeadeBackup and then luksHeaderRestore to the location of my original header on disk. It will "pretend" to be a real header, and in fact I will be using another detached one. If my computer is stolen, I wish good luck to the opponent who tries to brute-force a drive with a fake header (the real header at this time will be on a USB in my pants pocket). Do you see any possible problems in the operating system due to the fake header?