From: Herbert Valerio Riedel <hvr@gnu.org>
To: linux-crypto@nl.linux.org
Cc: linux-kernel@vger.kernel.org, ak@suse.de, axboe@suse.de,
astor@fast.no, hvr@gnu.org
Subject: Announce: cryptoapi-2.4.3 [aka international crypto (non-)patch]
Date: Mon, 23 Apr 2001 16:33:38 +0200 [thread overview]
Message-ID: <200104231433.QAA05348@phobos.hvrlab.org> (raw)
hello!
short version:
this is the international crypto patch, which is built outside of
the kernel source tree. you don't even have to reboot (unless your
kernel didn't have loop devices enabled, or some other unthought
situation exists... :)
As a response to Jari's loop-AES crypto filter for the loop back
device, which claims to be hassle free since no kernel modification is
needed; I've repackaged the all known international crypto patch,
which according to some people suffers from the need to patch the
kernel in order to make use of it and thus may not be ever get into
the kernel since there are still some countries where laws don't
support an individuals need for privacy.
This (re)package has only one major drawback, crypto can only built as
modules so far and it supports only kernel 2.4.3 and later so far...
If you are interested you can get it from
http://www.hvrlab.org/pub/crypto/cryptoapi-2.4.3-hvr4.tar.gz
...as usual, backup your data before playing around with it... :-)
ps: there is an optional patch against loop.[ch] contained, which
fixes current IV calculation bugs and introduces a selectable sector
based IV calculation mode.
greetings,
--
Herbert Valerio Riedel / Finger hvr@gnu.org for GnuPG Public Key
GnuPG Key Fingerprint: 7BB9 2D6C D485 CE64 4748 5F65 4981 E064 883F 4142
next reply other threads:[~2001-04-23 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-23 14:33 Herbert Valerio Riedel [this message]
2001-04-24 11:40 ` Announce: cryptoapi-2.4.3 [aka international crypto (non-)patch] Jari Ruusu
2001-04-25 14:05 ` Herbert Valerio Riedel
2001-04-26 10:47 ` Jari Ruusu
2001-04-26 12:37 ` Herbert Valerio Riedel
2001-04-26 18:28 ` 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=200104231433.QAA05348@phobos.hvrlab.org \
--to=hvr@gnu.org \
--cc=ak@suse.de \
--cc=astor@fast.no \
--cc=axboe@suse.de \
--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