From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v3.1e file/swap crypto package
Date: Sat, 28 Oct 2006 15:14:21 +0300 [thread overview]
Message-ID: <4543499D.67317564@users.sourceforge.net> (raw)
loop-AES changes since previous release:
- Changed swapon program to use getpagesize() instead of PAGE_SIZE macro.
Fixes build failure on some architectures. Patch form Max Vozeler.
- Fixed some confusing bits in README. Fix from Jens Lechtenboerger.
- Work around vanished <linux/config.h> in 2.6.19-rc2 kernel. Fixes build
failure.
- Changed loop code to use kthread_create() instead of kernel_thread() on
2.6.19-rc and newer kernels.
- Changed losetup and mount programs to output error message if gpg program
does not exist when gpg encrypted key file is used.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.1e.tar.bz2
md5sum 021d6a83e05a13ad84cd601d5e5ecefb
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.1e.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:[~2006-10-28 12:14 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=4543499D.67317564@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