From: Bryan Andersen <bryan@bogonomicon.net>
To: Vlad Harchev <hvv@hippo.ru>
Cc: J?rn Engel <joern@wohnheim.fh-wedel.de>,
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, 04 Mar 2003 05:07:38 -0600 [thread overview]
Message-ID: <3E6488FA.2050105@bogonomicon.net> (raw)
In-Reply-To: 20030304113106.GC4024@h
Vlad Harchev wrote:
>>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.
Yes it would be encrypted. Unfortunately it is predictable data and as
such it is much easier to crack. Better set that offset at a location
computed from the encryption key.
On a side note I find it interesting that many people sugest compressing
a file before encrypting it. Take a look at the first few bytes of
every compressed file. Unless your going to get rid of that header...
>>cryptofs would go through great pains to take such advantages away.
- Bryan
prev parent reply other threads:[~2003-03-04 10:58 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
2003-03-04 11:07 ` Bryan Andersen [this message]
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=3E6488FA.2050105@bogonomicon.net \
--to=bryan@bogonomicon.net \
--cc=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