From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mail.saout.de (Postfix) with ESMTP for ; Fri, 5 Feb 2010 12:11:07 +0100 (CET) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1NdM4d-0001Ja-Om for dm-crypt@saout.de; Fri, 05 Feb 2010 12:10:07 +0100 Received: from 80-27.79-83.cust.bluewin.ch ([83.79.27.80]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Feb 2010 12:10:07 +0100 Received: from studhalter.daniel by 80-27.79-83.cust.bluewin.ch with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Feb 2010 12:10:07 +0100 From: wucherpfennig Date: Fri, 05 Feb 2010 09:24:06 +0100 Message-ID: References: <20100204134943.GA15211@tansi.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit In-Reply-To: <20100204134943.GA15211@tansi.org> Sender: news Subject: Re: [dm-crypt] cryptsetup won't accept password after normal reboot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de Am 04.02.2010 14:49, schrieb Arno Wagner: > On Thu, Feb 04, 2010 at 10:21:26AM +0000, wucherpfennig wrote: >> First: I'm sorry for this strange topic behaviour, but I don't know how to >> write real answers (I tried in the test list, but didn't work either). >> >>> I gahther this is a new installation and you would only lose >>> a few hours of configuration work, correct? >> >> No. It was a fully working installtion. I wouldn't car that much about >> this problem, but I wanted to backup my stuff last weeekend (old backup >> was messed up). So basicly I'm standing here without any backup from the >> last few years... > > So you unlocked it sucessfully a number of times and suddenly > this does not work anymore? Any changes, like a different > keyboard? Yes and No, I didn't change anything... Thats why I think it has to be something with the keyboard... >>> For example if >>> you have, say, 12 characters and 9 of them are the same on most >>> keymaps, then you could try a direct brute force. >> >> I had the same idea last night. although my password is about 20 >> characters long a brute force attack shouldn't take too long, because >> there are 4 special Chars [eg ()_-] and 8 numbers. Letters shouldn't be >> the problem, numbers too... > > Letters, except 'y' and 'z'. Numbers should be the same. > Specials you will have to try some alternatives. > > Sounds doable. > > Arno I avoided y z, so there should be no problem... Any suggestions how to go on further?