From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v3.2a file/swap crypto package
Date: Tue, 15 May 2007 21:03:08 +0300 [thread overview]
Message-ID: <4649F5DC.87043316@users.sourceforge.net> (raw)
loop-AES changes since previous release:
- loop_twofish.c loop_serpent.c loop_blowfish.c modules included. They are
not built by default. Add EXTRA_CIPHERS=y make parameter to build them.
- Makefile rewritten to always use kbuild method on 2.6 kernels.
- Work around invalidate_bdev() changes on recent 2.6 kernels.
bzip2 compressed tarball is here:
http://osdn.dl.sourceforge.net/sourceforge/loop-aes/loop-AES-v3.2a.tar.bz2
md5sum d0b5b0f104ce0e1ee9e3ba9608f24ec4
http://osdn.dl.sourceforge.net/sourceforge/loop-aes/loop-AES-v3.2a.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:[~2007-05-15 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 18:03 Jari Ruusu [this message]
2007-05-15 21:16 ` Announce loop-AES-v3.2a file/swap crypto package markus reichelt
2007-05-16 4:53 ` 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=4649F5DC.87043316@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