From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org
Subject: Announce loop-AES-v3.1d file/swap crypto package
Date: Mon, 10 Apr 2006 16:53:24 +0300 [thread overview]
Message-ID: <443A6354.F9C720EF@users.sourceforge.net> (raw)
loop-AES changes since previous release:
- Fixed Makefile incompatibility with USE_KBUILD=y build option.
- Fixed incompatibility with CONFIG_PAX_KERNEXEC=y PAX config option.
- Fixed incompatibility with old SuSE 8.0 kernel that caused scheduler
interface to be misdetected.
- Changed mount to honor offset=N and sizelimit=N mount options when they
were used in combination with random keys generating phash=random mount
option. Old encrypted data is used in new keys generation, but earlier
buggy version always read and erased old data at offset=0.
- Added mount patch from Max Vozeler that makes it easier to first fsck and
then mount encrypted file systems.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.1d.tar.bz2
md5sum b4d13d6421382ea048e113ad8a868dfa
http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.1d.tar.bz2.sign
Additional ciphers package changes since previous release:
- Fixed Makefile incompatibility with USE_KBUILD=y build option.
bzip2 compressed tarball is here:
http://loop-aes.sourceforge.net/ciphers/ciphers-v3.0d.tar.bz2
md5sum 65d5e85b3aabd5a36a199814c66cd7f9
http://loop-aes.sourceforge.net/ciphers/ciphers-v3.0d.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-04-10 13:53 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=443A6354.F9C720EF@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).