From: Jasper Spaans <jasper@vs19.net>
To: linux-kernel@vger.kernel.org, ajgrothe@yahoo.com
Subject: crypto algoritms failing?
Date: Fri, 28 Jan 2005 00:30:07 +0100 [thread overview]
Message-ID: <20050127233007.GA4678@spaans.vs19.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
Hi List,
When booting I see this in dmesg:
testing tea ECB encryption
test 1 (128 bit key):
0a3aea4140a9ba94
fail
test 2 (128 bit key):
775d2a6af6ce9209
fail
test 3 (128 bit key):
be7abb81952d1f1edd89a1250421df95
fail
test 4 (128 bit key):
e04d5d3cb78c364794189591a9fc49f844d12dc299b8082a078973c24592c690
fail
[..]
testing xtea ECB encryption
test 1 (128 bit key):
aa2296e56c61f345
fail
test 2 (128 bit key):
823eeb35dcddd9c3
fail
test 3 (128 bit key):
e204dbf289859eea6135aaedb5cb712c
fail
test 4 (128 bit key):
0b03cd8abe95fdb1c144910ba5c91bb4a9da1e9eb13e2a8feaa56a85d1f4a8a5
fail
CPU in that machine is an athlon xp, cpu flags according to /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse pni syscall mmxext 3dnowext 3dnow
Compiler: gcc 3.3.5 (debian package 1:3.3.5-6)
Is this supposed to happen?
Jasper
--
Jasper Spaans http://jsp.vs19.net/
00:24:05 up 10207 days, 16:11, 0 users, load average: 6.29 6.03 6.13
There already is an object oriented version of COBOL.
It's called "ADD ONE TO COBOL GIVING COBOL."
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-01-27 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 23:30 Jasper Spaans [this message]
2005-01-28 0:38 ` crypto algoritms failing? 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
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=20050127233007.GA4678@spaans.vs19.net \
--to=jasper@vs19.net \
--cc=ajgrothe@yahoo.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.