From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Paulo da Silva <psdasilva@esoterica.pt>
Cc: linux-kernel@vger.kernel.org
Subject: Re: util-linux and data encryption
Date: Tue, 04 Oct 2005 08:13:54 +0300 [thread overview]
Message-ID: <43420F92.ABE3C821@users.sourceforge.net> (raw)
In-Reply-To: <4341567E.4050603@esoterica.pt>
Paulo da Silva wrote:
> I had a loop filesystem encrypted with twofish
> algorithm.
>
> Today, trying to mount the file, 'mount' claimed
> I needed to enter a password of 20 chars or more!
> Since I used less chars to encrypt, I was not able
> to recover the information!!!
> I tried CFLAGS="-DLOOP_PASSWORD_MIN_LENGTH=8"
> without any success. This causes 'mount' to accept
> the password, but, somehow, the decryption failled
> because the fs type remained unrecognized!
>
> BTW, I am using gentoo and I also tried USE=old-crypt.
> No way!
>
> I needed to install the version 2.12i to recover
> my information.
>
> Is this related with util-linux or has something
> to do with gentoo patches or something?
Seems like gentoo has merged loop-AES' util-linux patch which has always
used better defaults.
Mainline util-linux compatible mount options for /etc/fstab
encryption=twofish256,phash=unhashed2
Mainline util-linux compatible losetup command options
losetup -e twofish256 -H unhashed2 ......
kerneli.org compatible mount options for /etc/fstab
encryption=twofish256,phash=rmd160
kerneli.org compatible losetup command options
losetup -e twofish256 -H rmd160 ......
mount and losetup programs don't enforce 20 character minimum passphrase
length when using 'rmd160' or 'unhashed2' hash functions.
Both mainline util-linux and kerneli.org compatible setups are broken
securitywise. If there still are file systems using such broken setups, now
is good time to re-encrypt them using stronger crypto.
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
prev parent reply other threads:[~2005-10-04 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 16:04 Paulo da Silva
2005-10-03 22:07 ` Adrian Bunk
2005-10-04 0:14 ` Paulo da Silva
2005-10-04 5:13 ` Jari Ruusu [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=43420F92.ABE3C821@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=psdasilva@esoterica.pt \
/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
Powered by JetHome