From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v3.1c file/swap crypto package
Date: Wed, 18 Jan 2006 17:49:24 +0200 [thread overview]
Message-ID: <43CE6384.284B823C@users.sourceforge.net> (raw)
loop-AES changes since previous release:
- WBINVD assembler instruction is no longer used on Xen builds.
- Makefile changed to probe .h header files instead of .c source files. (2.4
and 2.6 kernels)
- compat_ioctl code updated to handle all 32bit/64bit loop ioctl conversions
on 2.6 kernels. No longer depends on fs/compat_ioctl.c handling them.
- Semaphores are not used/needed anymore on 2.6 kernels.
- Makefile changed to work around 2.6.16-rc1 build breakage.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.1c.tar.bz2
md5sum 3e54b8e66142fe58282e58075f73e58c
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.1c.tar.bz2.sign
Additional ciphers package changes since previous release:
- Makefile changed to work around 2.6.16-rc1 build breakage.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/ciphers/ciphers-v3.0c.tar.bz2
md5sum 8770eb519b448ef0d4a0306e015de283
http://loop-aes.sourceforge.net/ciphers/ciphers-v3.0c.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:[~2006-01-18 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 15:49 Jari Ruusu [this message]
2006-01-20 19:50 ` Announce loop-AES-v3.1c file/swap crypto package Sam Ravnborg
2006-01-21 16:27 ` Jari Ruusu
2006-01-21 22:10 ` Sam Ravnborg
2006-01-28 22:57 ` Sam Ravnborg
2006-01-29 14:47 ` 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=43CE6384.284B823C@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