public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kyle McMartin <kyle@debian.org>
To: James Morris <jmorris@intercode.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: CAST5 Cipher Algorithm for Kernel Cryptographic API.
Date: Mon, 11 Aug 2003 18:40:49 -0400	[thread overview]
Message-ID: <20030811224048.GA30195@imladris.debian.net> (raw)
In-Reply-To: <Mutt.LNX.4.44.0308120830040.13194-100000@excalibur.intercode.com.au>

[-- Attachment #1: Type: text/plain, Size: 750 bytes --]

On Tue, Aug 12, 2003 at 08:31:31AM +1000, James Morris wrote:
> It's already been made into a patch, I just need to get it tested on a 
> non-x86 box.
> 
The CAST5 cipher from the kerneli cryptoapi has been tested against
basically every architecture we could get our hands on, using the
test vectors supplied in the RFC.

If you'd like, I can submit a patch.

On the other hand, there really is no point adding CAST5, as
much stronger, much faster algorithms are already in place.

Lastly, if somebody really wants to put CAST in the kernel, I'd suggest
going with CAST6, the AES candidate specified in RFC-2612.

Regards,
-- 
Kyle McMartin <kyle@debian.org>
0x191FCD8A - 331A 9468 C04D 3A76 5C56  BA68 7EB7 92DF 191F CD8A [DSA]

[-- Attachment #2: Type: application/pgp-signature, Size: 155 bytes --]

  reply	other threads:[~2003-08-11 22:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 14:59 CAST5 Cipher Algorithm for Kernel Cryptographic API kartikey bhatt
2003-08-11 18:56 ` Jeff Sipek
2003-08-11 22:31   ` James Morris
2003-08-11 22:40     ` Kyle McMartin [this message]
2003-08-12  4:05       ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2003-08-13 11:33 kartikey bhatt
2003-08-13 11:49 ` James Morris
2003-08-11 14:58 kartikey bhatt

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=20030811224048.GA30195@imladris.debian.net \
    --to=kyle@debian.org \
    --cc=jmorris@intercode.com.au \
    --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