From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from v6.tansi.org (ns.km31936-01.keymachine.de [87.118.116.4]) by mail.server123.net (Postfix) with ESMTP for ; Mon, 23 Nov 2015 04:35:05 +0100 (CET) Received: from gatewagner.dyndns.org (77-57-54-224.dclient.hispeed.ch [77.57.54.224]) by v6.tansi.org (Postfix) with ESMTPA id D596120DC13E for ; Mon, 23 Nov 2015 04:35:04 +0100 (CET) Date: Mon, 23 Nov 2015 04:35:04 +0100 From: Arno Wagner Message-ID: <20151123033504.GA12468@tansi.org> References: <20151121184914.GA28647@tansi.org> <5651B1CF.7090306@sapo.pt> <20151122125233.GA4802@tansi.org> <5651D9B3.6000500@sapo.pt> <565241FF.90005@whgl.uni-frankfurt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <565241FF.90005@whgl.uni-frankfurt.de> Subject: Re: [dm-crypt] Open raid1 with luks encryption after a raid re-create List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On Sun, Nov 22, 2015 at 23:30:23 CET, Sven Eschenberg wrote: [...] > Now to your question, once you know the offset of the header: > 1.)Setup a loop device from your image (You can use an offset into > the image where your loop device starts with sector 0) see --offset > in losetup man page. Ah, yes. That would save copying it. > Inspect loopdevice if the LUKS Header now is on sector 0 > 2.)Try a cryptsetup luksopen in readonly mode Good idea. With that it may be reasonaly safe to work with the original disk. I still would make a full backup before. Regards, Arno -- 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 "news" is "something that hardly ever happens." -- Bruce Schneier