From: Adrian Bunk <bunk@stusta.de>
To: James Morris <jmorris@redhat.com>
Cc: Jasper Spaans <jasper@vs19.net>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, ajgrothe@yahoo.com
Subject: Re: crypto algoritms failing?
Date: Fri, 28 Jan 2005 11:55:50 +0100 [thread overview]
Message-ID: <20050128105550.GL28047@stusta.de> (raw)
In-Reply-To: <Xine.LNX.4.44.0501272023080.7174-100000@thoron.boston.redhat.com>
On Thu, Jan 27, 2005 at 08:43:18PM -0500, James Morris wrote:
> On Fri, 28 Jan 2005, Jasper Spaans wrote:
>
> > On Thu, Jan 27, 2005 at 07:38:43PM -0500, James Morris wrote:
> > > > Is this supposed to happen?
> > >
> > > No. What is your kernel version?
> >
> > Current bitkeeper + latest swsusp2 patches and hostap driver, however, those
> > two don't come near touching the crypto stuff[1] so they're not really on my
> > suspect shortlist, but I'll see if I can find time to build a vanilla one
> > tomorrow (that is, without swsusp/hostap).. right now, it's time to sleep in
> > my local timezone..
>
> Looks like a cleanup broke the test vectors:
> http://linux.bkbits.net:8080/linux-2.5/gnupatch@41ad5cd9EXGuUhmmotTFBIZdIkTm0A
>
> Patch below, please apply.
>...
Ops, yes, sorry.
Where are the broen paperbags?
Signed-off-by: Adrian Bunk <bunk@stusta.de>
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-01-28 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 23:30 crypto algoritms failing? Jasper Spaans
2005-01-28 0:38 ` James Morris
2005-01-28 0:47 ` Jasper Spaans
2005-01-28 1:43 ` James Morris
2005-01-28 9:14 ` Jasper Spaans
2005-01-28 10:55 ` Adrian Bunk [this message]
2005-01-28 1:49 ` Nigel Cunningham
2005-01-28 2:25 ` James Morris
2005-01-28 5:28 ` Nigel Cunningham
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=20050128105550.GL28047@stusta.de \
--to=bunk@stusta.de \
--cc=ajgrothe@yahoo.com \
--cc=akpm@osdl.org \
--cc=jasper@vs19.net \
--cc=jmorris@redhat.com \
--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.