From: Bill Davidsen <davidsen@tmr.com>
To: Jari Ruusu <jariruusu@users.sourceforge.net>
Cc: linux-crypto@nl.linux.org, linux-kernel@vger.kernel.org
Subject: Re: Announce loop-AES-v3.0b file/swap crypto package
Date: Sun, 16 Jan 2005 23:26:38 -0500 [thread overview]
Message-ID: <41EB3E7E.7070100@tmr.com> (raw)
In-Reply-To: <41EAE36F.35354DDF@users.sourceforge.net>
Jari Ruusu wrote:
> loop-AES changes since previous release:
> - Fixed externally compiled module version multi-key-v3 ioctl
> incompatibility with boxes running 64 bit kernel and 32 bit userland.
> Kernel patch versions were not affected (2.4 and 2.6 kernels).
> - Fixed bug that made v3 on-disk format always use file backed code path on
> some 2.6 kernels that did not have LO_FLAGS_DO_BMAP defined. No data loss,
> but file backed code path is not journaled file system safe. Same bug also
> had cosmetic side effect of "losetup -a" status query always displaying
> file backed v2 on-disk format as v3 on-disk format.
>
> bzip2 compressed tarball is here:
>
> http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.0b.tar.bz2
> md5sum b295ff982cd4503603b38fdc54e604cc
>
> http://loop-aes.sourceforge.net/loop-AES/loop-AES-v3.0b.tar.bz2.sign
>
Is this eventually going in the mainline kernel? I'd like to use it, but
if I'm going to have to maintain my own crypto kernels indefinitely this
probably isn't the one for me.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2005-01-17 4:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 21:58 Announce loop-AES-v3.0b file/swap crypto package Jari Ruusu
2005-01-17 4:26 ` Bill Davidsen [this message]
2005-01-17 5:10 ` Willy Tarreau
2005-01-17 15:08 ` Jari Ruusu
2005-01-17 19:14 ` Fruhwirth Clemens
2005-01-17 19:29 ` Paul Walker
2005-01-17 21:04 ` Fruhwirth Clemens
2005-01-17 21:39 ` Paul Walker
2005-01-18 15:35 ` Jari Ruusu
2005-01-18 17:23 ` Andries Brouwer
2005-01-18 18:38 ` Venkat Manakkal
2005-01-19 0:18 ` Dan Hollis
2005-01-19 0:46 ` Kyle Moffett
2005-01-19 17:03 ` Bill Davidsen
2005-01-19 17:57 ` Fruhwirth Clemens
2005-01-19 21:24 ` James Morris
2005-01-19 22:18 ` Fruhwirth Clemens
2005-01-20 16:42 ` Bill Davidsen
2005-01-17 21:26 ` markus reichelt
2005-01-17 23:11 ` Fruhwirth Clemens
2005-01-18 0:06 ` Daniel Harvey
2005-01-18 23:30 ` Peter_22
2005-01-18 9:49 ` jerome etienne
2005-01-18 15:36 ` Jari Ruusu
2005-01-20 22:38 ` markus reichelt
2005-01-21 18:29 ` Sytse Wielinga
2005-01-17 20:28 ` Andreas Jellinghaus
2005-01-17 21:38 ` Paul Walker
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=41EB3E7E.7070100@tmr.com \
--to=davidsen@tmr.com \
--cc=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