Re: crypto algoritms failing?

[Nigel Cunningham <ncunningham@linuxmail.org>]

Hi.

You normally test cryptoapi functionality while booting?

Anyway, I can confirm that if suspend2 touches anything remotely related
to this, it's unintentional and I'll fix it :>

Nigel

On Fri, 2005-01-28 at 10:30, Jasper Spaans wrote:
> 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
-- 
Nigel Cunningham
Software Engineer
Cyclades Corporation

http://cyclades.com