From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Missing keyslot or broken header or still some hope?
Date: Mon, 7 Nov 2016 22:30:50 +0100 [thread overview]
Message-ID: <20161107213050.GA15750@tansi.org> (raw)
In-Reply-To: <trinity-07e77522-de90-4e6e-8acc-dd6f22d61bf6-1478417210545@3capp-webde-bs39>
It happens. Don't worry about it.
Regards,
Arno
On Sun, Nov 06, 2016 at 08:26:50 CET, zero.tonin@web.de wrote:
> Good morning all, good morning Sven,
>
> thank you very much for your message and insight and also for confirming parts of my understanding of the situation.
>
> Now, getting back to my drive, I have to make the most embarrassing confession - for the last three days I actually tried to unlock the drive with my user account password and, in contrast to my initial words (which I eat now), _not_ with the drive password. I have not the lsightest idea why, apart from the two (password and passphrase) being in use both for the same amount of time, which is roughly 5 years or so.
>
> The luks header and keyslot are not only intact, they are fully working and I can decrypt the drive no problem. Turns out it was, indeed, a "layer 8 problem".
>
> I am, while relieved I can recover the data, add a second keyslot and rsync the drive immediately, sincerely sorry for having used (some may say wasted) this list's and some individual's time,, but thanks again for all your help.
>
> On the positive side, this forced me to learn a bit more about luks and what it actually does (instead of just using it) and also was an opportunity to lear to never again claim I am "100% certain about the password"…
>
>
> Thanks again, all, and a great Sunday to everyone,
> Mark
>
> (I will take the liberty to remain on this list for future interesting topics)
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
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
prev parent reply other threads:[~2016-11-07 21:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 18:30 [dm-crypt] Missing keyslot or broken header or still some hope? Zero Tonin
2016-11-03 19:04 ` Michael Kjörling
2016-11-03 20:58 ` Zero Tonin
2016-11-04 11:32 ` Arno Wagner
2016-11-04 19:35 ` zero.tonin
2016-11-04 20:08 ` Michael Kjörling
2016-11-05 10:16 ` Heinz Diehl
2016-11-05 10:47 ` Michael Kjörling
2016-11-04 23:28 ` Arno Wagner
2016-11-05 7:56 ` zero.tonin
2016-11-05 10:54 ` Michael Kjörling
2016-11-05 21:58 ` zero.tonin
2016-11-05 22:41 ` Sven Eschenberg
2016-11-06 7:26 ` zero.tonin
2016-11-06 11:13 ` [dm-crypt] Missing keyslot or broken header or still some hope? SOLVED Michael Kjörling
2016-11-07 21:30 ` Arno Wagner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161107213050.GA15750@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.