From: Jan Engelhardt <jengelh@medozas.de>
To: "Stefan G. Weichinger" <lists@xunil.at>
Cc: gentoo-user@lists.gentoo.org,
Daniel Troeder <daniel@admin-box.com>, walt <w41ter@gmail.com>,
Florian Philipp <lists@f_philipp.fastmail.net>,
Jason Dusek <jason.dusek@gmail.com>,
Till Maas <opensource@till.name>,
hanno@gentoo.org
Subject: [gentoo-user] Re: Kernel upgrade and now LUKS failure
Date: Tue, 18 May 2010 15:05:24 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.01.1005181504030.28404@obet.zrqbmnf.qr> (raw)
In-Reply-To: <4BF108F3.1080304@xunil.at>
On Monday 2010-05-17 11:14, Stefan G. Weichinger wrote:
>Am 16.05.2010 14:36, schrieb Jan Engelhardt:
>> [Replying to
>> http://thread.gmane.org/gmane.linux.gentoo.user/229533/focus=229542
>> ]
>>
>> Second, it's using echo without the -n parameter, thus implicitly
>> inserting a newline into the key -- which is the cause for yoru
>> observed mounting problems.
>>
>> Third, because you are passing the key via stdin into cryptsetup, it
>> only uses the first line of whatever you pipe into it; whereas
>> pam_mount uses the entire keyfile as it is supposed to be.
>>[...]
>Jan, thanks for your suggestions.
>
>I created a new LUKS-volume and tried to avoid all the mentioned
>pitfalls (I used "echo -n", avoided stdin etc.), but this didn't help here.
To be sure, use
openssl -d ... | hexdump -C
to detect newlines in the key. The shell has far too many occasions
where \n gets stripped or added.
next prev parent reply other threads:[~2010-05-18 13:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 12:36 [gentoo-user] Re: Kernel upgrade and now LUKS failure Jan Engelhardt
2010-05-17 9:14 ` Stefan G. Weichinger
2010-05-17 21:01 ` Daniel Troeder
2010-05-18 13:05 ` Jan Engelhardt [this message]
2010-05-18 13:44 ` Stefan G. Weichinger
2010-05-18 16:04 ` Jan Engelhardt
2010-05-18 16:56 ` Stefan G. Weichinger
2010-05-18 17:57 ` Jan Engelhardt
2010-05-18 18:57 ` Stefan G. Weichinger
2010-05-18 19:33 ` Stefan G. Weichinger
2010-05-18 20:06 ` Jan Engelhardt
2010-05-18 20:17 ` Stefan G. Weichinger
2010-05-18 21:16 ` Jan Engelhardt
2010-05-18 21:49 ` Stefan G. Weichinger
2010-05-18 22:23 ` Jan Engelhardt
2010-05-20 10:25 ` Stefan G. Weichinger
2010-05-20 13:40 ` Stefan G. Weichinger
2010-05-23 20:37 ` [gentoo-user] SOLVED: " Stefan G. Weichinger
2010-05-23 21:57 ` Mick
2010-05-25 18:44 ` Stefan G. Weichinger
2010-05-18 19:38 ` [gentoo-user] " Eray Aslan
2010-05-21 20:24 ` Daniel Troeder
-- strict thread matches above, loose matches on Subject: below --
2010-05-03 16:56 [gentoo-user] " Jason Dusek
2010-05-04 10:06 ` Stefan G. Weichinger
2010-05-04 16:54 ` [gentoo-user] " walt
2010-05-04 17:38 ` Stefan G. Weichinger
2010-05-04 19:28 ` Stefan G. Weichinger
2010-05-04 21:24 ` Daniel Troeder
2010-05-05 4:42 ` Stefan G. Weichinger
2010-05-05 8:00 ` Daniel Troeder
2010-05-05 8:42 ` Stefan G. Weichinger
2010-05-05 19:39 ` Daniel Troeder
2010-05-05 20:17 ` Stefan G. Weichinger
2010-05-05 20:23 ` Stefan G. Weichinger
2010-05-06 16:24 ` Daniel Troeder
2010-05-06 18:38 ` Stefan G. Weichinger
2010-05-07 8:53 ` Stefan G. Weichinger
2010-05-07 14:24 ` Stefan G. Weichinger
2010-05-07 21:14 ` Stefan G. Weichinger
2010-05-10 16:48 ` Daniel Troeder
2010-05-04 23:51 ` walt
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=alpine.LSU.2.01.1005181504030.28404@obet.zrqbmnf.qr \
--to=jengelh@medozas.de \
--cc=daniel@admin-box.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=hanno@gentoo.org \
--cc=jason.dusek@gmail.com \
--cc=lists@f_philipp.fastmail.net \
--cc=lists@xunil.at \
--cc=opensource@till.name \
--cc=w41ter@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox