From: Jose Luis Domingo Lopez <linux-lvm@24x7linux.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] encryption in LVM2
Date: Mon Feb 17 14:34:01 2003 [thread overview]
Message-ID: <20030217203406.GA6846@localhost> (raw)
In-Reply-To: <3E510115.C2FF3B83@silicide.dk>
On Monday, 17 February 2003, at 16:34:45 +0100,
Jon Bendtsen wrote:
> I only have experience with LVM1, but naturaly i've heard about LVM2,
> and the device mapper.
> Has anyone built in encryption into the device mapper ?
> Is anyone working on it ?
>
I don't know of anyone working on block-based encryption for LVM2/DM,
but by now you can try one of the several filesystem-level encryption
solutions out there. I have personally used loop-aes, it is simple to
set up and works ok on my boxes.
Hope it helps.
--
Jose Luis Domingo Lopez
Linux Registered User #189436 Debian Linux Sid (Linux 2.4.20-xfsip)
next prev parent reply other threads:[~2003-02-17 14:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-17 9:35 [linux-lvm] encryption in LVM2 Jon Bendtsen
2003-02-17 14:34 ` Jose Luis Domingo Lopez [this message]
2003-02-17 18:46 ` Goetz Bock
2003-02-18 2:51 ` Jon Bendtsen
2003-02-18 2:48 ` Jon Bendtsen
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=20030217203406.GA6846@localhost \
--to=linux-lvm@24x7linux.com \
--cc=linux-lvm@sistina.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