From: Vlad Harchev <hvv@hippo.ru>
To: J?rn Engel <joern@wohnheim.fh-wedel.de>
Cc: Neil Brown <neilb@cse.unsw.edu.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.4 and cryptofs on raid1 - what will be cached and how many times
Date: Tue, 4 Mar 2003 15:31:06 +0400 [thread overview]
Message-ID: <20030304113106.GC4024@h> (raw)
In-Reply-To: <20030304092031.GB6583@wohnheim.fh-wedel.de>
On Tue, Mar 04, 2003 at 10:20:31AM +0100, J?rn Engel wrote:
> On Tue, 4 March 2003 13:30:20 +0400, Vlad Harchev wrote:
> >
> > Sorry for confusion - I meant loopback-based crypto filesystem - e.g. loop-aes
> > based (loop-aes.sourceforge.net) or CryptoAPI-based (www.kerneli.org) - both
> > are loopback-based filesystem (one has to call losetup(8) to point out chipher,
> > a password..)
>
> Loopback with encryption is not the same as a crypto filesystem.
> Loopback encryption works transparently with any (non-)crypto fs.
Yes, you are right.
> A potential attacker can use this to look for the ext2 superblock,
> which gives him the same data both encrypted an unencrypted. A real
I've got an impression that in case of loopback with encryption the
superblock will also be encrypted.
If one forgets known cleartext attacks, one can place the filesystem at
some offset.
> cryptofs would go through great pains to take such advantages away.
>
--
Best regards,
-Vlad
next prev parent reply other threads:[~2003-03-04 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 10:56 2.4 and cryptofs on raid1 - what will be cached and how many times Vlad Harchev
2003-03-03 9:38 ` Vlad Harchev
2003-03-03 21:50 ` Neil Brown
2003-03-04 9:30 ` Vlad Harchev
2003-03-04 9:20 ` Jörn Engel
2003-03-04 11:31 ` Vlad Harchev [this message]
2003-03-04 11:07 ` Bryan Andersen
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=20030304113106.GC4024@h \
--to=hvv@hippo.ru \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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