From: Etaoin Shrdlu <shrdlu@unlimitedmail.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Encrypting removable media
Date: Fri, 24 Feb 2006 15:42:39 +0100 [thread overview]
Message-ID: <200602241542.39873.shrdlu@unlimitedmail.org> (raw)
In-Reply-To: <20060224141818.GA359@huxley.linguistik.uni-erlangen.de>
On Friday 24 February 2006 15:18, Matthias Bethke wrote:
> I have a bit of chicken-and-egg problem trying to get encrypted
> removable devices to work as "normal" as possible.
> Using Loop-AES and a GPG-encrypted key I had no problems encrypting my
> external FW drive, but to pass all the options to losetup without
> entering them by hand every time, I need an fstab entry. The drive
> shows up as /dev/sda, but putting /dev/sda1 there is no good as it
> would try to use Loop-AES on *every* external drive. So far I could
> just use volume labels in my fstab to distinguish any number of
> drives---well, I used to until hald/dbus made that automatic. But now
> there are no labels any more as they get encrypted as well.
> Has anyone come up with a solution for this yet? I could imagine some
> plugin for the hotplug system that checks /proc/scsi/scsi for a
> certain model before mounting. Not the cleanest solution either but as
> my external drives are different models it would work for me. I don't
> have much of a clue about the hotplug system though...
With udev you can create hardware-specific devices (meaning you can have
a device in /dev that corresponds exactly to some particular hard disk),
based on various hardware-specific information (eg, manufacturer name or
device id and many others) See
http://www.reactivated.net/writing_udev_rules.html
for the details.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-24 14:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-24 14:18 [gentoo-user] Encrypting removable media Matthias Bethke
2006-02-24 14:42 ` Etaoin Shrdlu [this message]
2006-02-24 17:59 ` Matthias Bethke
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=200602241542.39873.shrdlu@unlimitedmail.org \
--to=shrdlu@unlimitedmail.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