From: Marc Mutz <Marc@Mutz.com>
To: Jon Masters <jonathan@easypenguin.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Crypto in 2.4
Date: Sat, 06 Jan 2001 21:34:32 +0000 [thread overview]
Message-ID: <3A578F68.C4F4ADC7@Mutz.com> (raw)
In-Reply-To: <3A553A03.DCFBCB9@easypenguin.co.uk>
Jon Masters wrote:
>
> Hello,
>
> I am aware of work being done to create crypto patches for 2.4 however I
> am wondering what kind of time scale is likely to be involved before a
> patch for 2.4.0 becomes available and, more importantly, when such a
> patch will be suitable for daily use (disclaimers withstanding
> obviously).
>
> Let's just say I'm cautious after a bad experience with one of the
> previous dud patch releases :P
>
<snip>
A 2.4.0.1 should be on ftp.kernel.org/pub/linux/kernel/crypto/v2.4/. But
it has been heavily re-worked. I haven't got my hands on that one and
will keep quiet as to what extend that patch is produiction-ready, but I
remember that the loop driver in 2.4.0 still can stall your box. Since
the kerneli crypto relies on loop, this would count in favor of "don't
do that yet".
BTW: You might want to join linux-crypto@nl.linux.org (majordomo) if you
are interested in kerneli.
Marc
--
Marc Mutz <Marc@Mutz.com> http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics
PGP-keyID's: 0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-06 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 3:05 Crypto in 2.4 Jon Masters
2001-01-06 21:34 ` Marc Mutz [this message]
2001-01-06 23:29 ` Jon Masters
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=3A578F68.C4F4ADC7@Mutz.com \
--to=marc@mutz.com \
--cc=jonathan@easypenguin.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.