From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.depressiverobots.com (depressiverobots.com [85.14.254.23]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Fri, 24 Nov 2017 17:23:58 +0100 (CET) References: From: protagonist Message-ID: Date: Fri, 24 Nov 2017 17:15:53 +0100 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dm-crypt] LUKS header recovery attempt, bruteforce detection of AF-keyslot bit errors List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jindrich Kolman , dm-crypt@saout.de Hello Jindrich, could you get in direct contact with me and send some further technical information regarding the affected drive / partition info / filesystem / SMART values / .. ? I'd be happy to help. protagonist On 24.11.2017 12:57, Jindrich Kolman wrote: > About a week back, i was suddenly unable to open my luks-encrypted partition. Mysteriously, a day later, it then worked again, but since two days ago, i an again locked out. Would you be willing to share your code, protagonist? > > >>My current memcmp of the first 512 bytes therefore works just as well on >>LVM as on ext4 and has managed to find a bit flip on a deliberately >>corrupted key slot. > >>However, this is bad news for my ultimate target of recovering the >>actual master key of the SSD in question, as it seems my previous >>1-error checks have been unsuccessful, but valid. >>Regards, >>protagonist