From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: jerome etienne <jme@off.net>
Cc: Fruhwirth Clemens <clemens@endorphin.org>,
linux-kernel@vger.kernel.org, linux-crypto@nl.linux.org
Subject: Re: Announce loop-AES-v3.0b file/swap crypto package
Date: Tue, 18 Jan 2005 17:36:20 +0200 [thread overview]
Message-ID: <41ED2CF4.C6E4FC0B@users.sourceforge.net> (raw)
In-Reply-To: 41ECDBA9.8030005@off.net
jerome etienne wrote:
> 3 years ago i published a paper describing how an attacker would be able
> to modify the content of the encrypted device without being detected.
> http://off.net/~jme/loopdev_vul.html
>
> i was just curious about the current state of loop-aes. Is it still
> vulnerable to this attack ?
Quote from loop-AES README file
"
Loop device encrypts data but does not authenticate ciphertext. In other
words, it delivers data privacy, but does not guarantee that data has not
been tampered with. Admins setting up encrypted file systems should ensure
that neither ciphertext, nor tools used to access ciphertext (kernel +
kernel modules, mount, losetup, and other utilities) can be trojaned or
tampered.
"
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
next prev parent reply other threads:[~2005-01-18 15:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 21:58 Announce loop-AES-v3.0b file/swap crypto package Jari Ruusu
2005-01-17 4:26 ` Bill Davidsen
2005-01-17 5:10 ` Willy Tarreau
2005-01-17 15:08 ` Jari Ruusu
2005-01-17 19:14 ` Fruhwirth Clemens
2005-01-17 19:29 ` Paul Walker
2005-01-17 21:04 ` Fruhwirth Clemens
2005-01-17 21:39 ` Paul Walker
2005-01-18 15:35 ` Jari Ruusu
2005-01-18 17:23 ` Andries Brouwer
2005-01-18 18:38 ` Venkat Manakkal
2005-01-19 0:18 ` Dan Hollis
2005-01-19 0:46 ` Kyle Moffett
2005-01-19 17:03 ` Bill Davidsen
2005-01-19 17:57 ` Fruhwirth Clemens
2005-01-19 21:24 ` James Morris
2005-01-19 22:18 ` Fruhwirth Clemens
2005-01-20 16:42 ` Bill Davidsen
2005-01-17 21:26 ` markus reichelt
2005-01-17 23:11 ` Fruhwirth Clemens
2005-01-18 0:06 ` Daniel Harvey
2005-01-18 23:30 ` Peter_22
2005-01-18 9:49 ` jerome etienne
2005-01-18 15:36 ` Jari Ruusu [this message]
2005-01-20 22:38 ` markus reichelt
2005-01-21 18:29 ` Sytse Wielinga
2005-01-17 20:28 ` Andreas Jellinghaus
2005-01-17 21:38 ` Paul Walker
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=41ED2CF4.C6E4FC0B@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=clemens@endorphin.org \
--cc=jme@off.net \
--cc=linux-crypto@nl.linux.org \
--cc=linux-kernel@vger.kernel.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