Re: Design flaw in LUKS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05.08.2006 12:32:41, Absolon wrote:
> The solution is so easy to implement; making a proper utility to save the
> header to
> a file and having more copies of the header, security meassures to ensure
> that the header
> isn't damaged and more recovery options. Since the header is crypted it
> doesn't matter if it's
> written to a file since you can already read it on the disk.

That tool is called dd.

	dd if=/dev/hda2 of=luksheader count=1032

Greetings,
	Benjamin
-- 
  ____  _        _    ____  _   _ _ _____ __  __ 
 / ___|| |      / \  / ___|| | | ( ) ____|  \/  |
 \___ \| |     / _ \ \___ \| |_| |/|  _| | |\/| |
  ___) | |___ / ___ \ ___) |  _  | | |___| |  | |
 |____/|_____/_/   \_\____/|_| |_| |_____|_|  |_|
 play online: telnet://slashem.crash-override.net
 view scores: http://slashem.crash-override.net
 watch deaths: irc://irc.freenode.net#slashem

Attachment: pgpPnVm7zyo8I.pgp
Description: PGP signature


[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux