From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v2.2c file/swap crypto package
Date: Sun, 24 Oct 2004 20:18:14 +0300 [thread overview]
Message-ID: <417BE3D6.BB54FE7D@users.sourceforge.net> (raw)
loop-AES changes since previous release:
- Added compile time autodetection and workaround for per-thread vs.
per-process rlimits (2.6 kernels).
- Added Gentoo compatible binary key setup option to mount and losetup
'mount -p 0 -o phash=unhashed3' or 'losetup -p 0 -H unhashed3'.
- Added random key setup option to mount and losetup. This can be used to
encrypt /tmp with random keys.
- Added workaround for module_param_array() breakage in 2.6.10-rc
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v2.2c.tar.bz2
md5sum 439a25bd1e85e8053bf0cf3c504279ed
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v2.2c.tar.bz2.sign
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
next reply other threads:[~2004-10-24 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-24 17:18 Jari Ruusu [this message]
2004-10-25 16:55 ` Announce loop-AES-v2.2c file/swap crypto package Jari Ruusu
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=417BE3D6.BB54FE7D@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;
as well as URLs for NNTP newsgroup(s).