From: "J. Roeleveld" <joost@antarean.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [SOLVED] Running cryptsetup under mdev
Date: Wed, 07 May 2014 20:57:29 +0200 [thread overview]
Message-ID: <adc2d4fb-ef5a-4c35-a3bf-15064e3586ce@email.android.com> (raw)
In-Reply-To: <20140507181110.GA806@waltdnes.org>
On 7 May 2014 20:11:10 CEST, Walter Dnes <waltdnes@waltdnes.org> wrote:
>On Wed, May 07, 2014 at 08:11:02AM +0200, J. Roeleveld wrote
>> On Tuesday, May 06, 2014 05:34:52 PM Walter Dnes wrote:
>> >
>> > Unfortunately, mdev != udev. People running RAID have problems
>too.
>>
>> I know it isn't. I just find it strange that LVM can't work without
>> udev when I see options which configure the LVM-tools to either
>> double-check udevs actions or even completely bypass udev:
>
> Thanks for the pointer. After turning off the udev-related options in
>lvm.conf, I'm getting /dev/mapper device nodes as expected.
That is good. Now if only mdadm can be confirmed to work with mdev. I could try it on one of my machines.
> I still
>can't get cryptsetup to work with LUKS, but it works fine *WITHOUT*
>LUKS
>as per instructions at
>http://sleepyhead.de/howto/?href=cryptpart#woluks
>In my case, the initial setup was...
>
>cryptsetup -y create usbkey1 /dev/sdb1
>mkfs.ext2 /dev/mapper/usbkey1
>mount -t ext2 /dev/mapper/usbkey1 /mnt/usbkey1
>umount /mnt/usbkey1
>cryptsetup remove usbkey1
>
>...and subsequent sessions...
>
>cryptsetup -y create usbkey1 /dev/sdb1
>mount -t ext2 /dev/mapper/usbkey1 /mnt/usbkey1
>...do whatever...
>umount /mnt/usbkey1
>cryptsetup remove usbkey1
>
> The setup and teardown commands have to be done as root, but I've
>chowned /mnt/usbkey1 to waltdnes:users and confirmed that I can create
>and delete files and directories as a regular user.
The create and remove commands with LUKS also require root. They use a session manager in desktop environments to allow users to do it. Sudo with a secure wrapper script might be sufficient for you?
I was wondering. What is the actual reason why cryptsetup has a LUKS and non-LUKS set of options?
--
Joost
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2014-05-07 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 18:31 [gentoo-user] Problems with loop-aes Walter Dnes
2014-05-06 18:45 ` J. Roeleveld
2014-05-06 21:34 ` Walter Dnes
2014-05-07 6:11 ` J. Roeleveld
2014-05-07 18:11 ` [gentoo-user] [SOLVED] Running cryptsetup under mdev Walter Dnes
2014-05-07 18:57 ` J. Roeleveld [this message]
2014-05-08 10:36 ` Andrew Savchenko
2014-05-12 6:51 ` J. Roeleveld
2014-05-12 7:21 ` Matti Nykyri
2014-05-12 7:24 ` Matti Nykyri
2014-05-06 21:50 ` [gentoo-user] Problems with loop-aes Alon Bar-Lev
2014-05-07 4:36 ` Walter Dnes
2014-05-07 6:48 ` Alon Bar-Lev
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=adc2d4fb-ef5a-4c35-a3bf-15064e3586ce@email.android.com \
--to=joost@antarean.org \
--cc=gentoo-user@lists.gentoo.org \
/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