From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from v6.tansi.org (mail.tansi.org [87.118.116.4]) by mail.server123.net (Postfix) with ESMTP for ; Wed, 10 Feb 2016 22:50:14 +0100 (CET) Received: from gatewagner.dyndns.org (77-57-36-72.dclient.hispeed.ch [77.57.36.72]) by v6.tansi.org (Postfix) with ESMTPA id 6A09820DC1FB for ; Wed, 10 Feb 2016 22:50:14 +0100 (CET) Date: Wed, 10 Feb 2016 22:50:14 +0100 From: Arno Wagner Message-ID: <20160210215013.GA32269@tansi.org> References: <20160208160227.6a446085@lustre.ryper.org> <20160209011150.GB10406@tansi.org> <20160209152824.774e5d25@lustre.ryper.org> <20160209232819.GA21086@tansi.org> <20160210131315.1991cca7@lustre.ryper.org> <20160210192121.GA31043@tansi.org> <20160210200256.GQ12867@yeono.kjorling.se> <56BB989F.5090805@whgl.uni-frankfurt.de> <20160210201350.GR12867@yeono.kjorling.se> <56BB9D93.7020804@whgl.uni-frankfurt.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <56BB9D93.7020804@whgl.uni-frankfurt.de> Subject: Re: [dm-crypt] Size of LUKS header and how to overwrite List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de I should probably update the FAQ with the information about the "payload offset" field in a separate item. Maybe "How to overwrite only the LUKS header". Keep in mind that much of the statements in the FAQ are still=20 in their first incarnation and quite a few things may lack=20 a simplified description, as I like to give the full story. Hence I am grateful if anybody points out such shortcommings. Regards and thanks, Arno On Wed, Feb 10, 2016 at 21:29:07 CET, Sven Eschenberg wrote: > Ah, I see. Well the FAQ gives alternatives and more information on > the size of the header for different keylengths and so on. But as > the header+keymaterial can hardly be bigger than the offset of the > encrypted payload on the backing device a dd with > count=3Dpayload-offset and bs=3D512 indeed does the trick. >=20 > Of course you'd have to check the payload offset of that particular > container and not mix any numbers etc. . >=20 > Regards >=20 > -Sven >=20 >=20 > Am 10.02.2016 um 21:13 schrieb Michael Kj=F6rling: > >On 10 Feb 2016 21:07 +0100, from sven@whgl.uni-frankfurt.de (Sven Eschen= berg): > >>Yes, it will overwrite the header and potential free space after the > >>header up to the first sector of encrypted data. > >> > >>Does this seem so weird? > > > >No, but given the somewhat roundabout way this was described in the > >FAQ at least last I looked, this seems like a much easier way to > >describe it... > > > _______________________________________________ > dm-crypt mailing list > dm-crypt@saout.de > http://www.saout.de/mailman/listinfo/dm-crypt --=20 Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718 ---- A good decision is based on knowledge and not on numbers. -- Plato If it's in the news, don't worry about it. The very definition of=20 "news" is "something that hardly ever happens." -- Bruce Schneier