From: chris <chris@parallelsw.com>
To: dm-devel@redhat.com, redhat-list@redhat.com
Subject: encrypted filesystem not encrypted?
Date: Tue, 31 Jul 2007 19:08:56 -0600 [thread overview]
Message-ID: <46AFDD28.40203@parallelsw.com> (raw)
Hi all,
I was not sure which list to send this to, so I choose a couple that
looked like decent fits, please advise if there is one more specific to
the encryption.
I am currently working on a project where we are converting some of our
filesystems to an encrypted fs using LVM2. We are running RHEL:
"2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:59:08 EDT 2007 i686 i686 i386
GNU/Linux"
We setup an encrypted filesystem using one of the open partitions on the
physical hard drive using "cryptsetup create /dev/sda3" We have
verified this using the cryptsetup status, This shows the filesystem as
being encrypted as aes_plain 256 bit key. We then created an LVM and
mounted the filesystem using the LVM.
All seems to be well, except when our testers ran the following command:
head -c 5000 /dev/sda3
They got some output that includes clear text and obviously not
encrypted data (along with encrypted data). Some things are date
formatted strings like 20050912 which appears quite a few times in the
mounted filesystem, and in the raw device (/dev/sda3).
I can post the exact commands that were used to create the filesystem,
but they are basically
create partition ...sda3
cryptsetup create /dev/sda3 (prompts for passphrase)
pvcreate
vgcreate
lvcreate
mount
(TIA) any help (or light shed on this) is greatly appreciated!
-chris
next reply other threads:[~2007-08-01 1:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 1:08 chris [this message]
2007-08-01 14:42 ` encrypted filesystem not encrypted? Jonathan Brassow
-- strict thread matches above, loose matches on Subject: below --
2007-08-01 16:12 Ellison, Bob
2007-08-01 23:05 ` chris
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=46AFDD28.40203@parallelsw.com \
--to=chris@parallelsw.com \
--cc=dm-devel@redhat.com \
--cc=redhat-list@redhat.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 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.