From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v3.2b file/swap crypto package
Date: Thu, 25 Oct 2007 21:36:32 +0300 [thread overview]
Message-ID: <4720E230.C05B9252@users.sourceforge.net> (raw)
loop-AES changes since previous release:
- Fixed compatibility detection problem involving separate obj/source trees.
- Fixed request size problem on unencrypted device backed USB device.
- Added initramfs type initrd build option to build-initrd.sh script. Patch
from Fix pr0gress0r AT ngs.ru
- Added gcc version override option to build-initrd.sh script.
- Fixed losetup -P cleartext key option which always failed to work and
printed error message saying so.
- Added util-linux-ng patch.
- Worked around block layer interface breakage on linux-2.6.24-rc1 kernel.
bzip2 compressed tarball is here:
http://dl.sourceforge.net/sourceforge/loop-aes/loop-AES-v3.2b.tar.bz2
md5sum 2c5642ccfa1a780ef4bd76eb873076aa
http://dl.sourceforge.net/sourceforge/loop-aes/loop-AES-v3.2b.tar.bz2.sign
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
reply other threads:[~2007-10-25 18:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4720E230.C05B9252@users.sourceforge.net \
--to=jariruusu@users.sourceforge.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