gnupg-1.4.9 fails checks in new distribution

[Klaus Singvogel]

Hi,
I noticed that gnupg-1.4.9 fails currently 10 of 27 tests in
openSUSE-11.1.

FAIL: encrypt.test
FAIL: encrypt-dsa.test
FAIL: seat.test
FAIL: encryptp.test
FAIL: armencrypt.test
FAIL: armencryptp.test
FAIL: signencrypt.test
FAIL: armsignencrypt.test
FAIL: conventional.test
FAIL: conventional-mdc.test

The failures didn't occur with openSUSE-11.0 or previous.

Having a closer look into the logfiles of above failed tests,
I see always the same error message:

--------------------------------------------------------------------
encrypt.test.log: Rijndael-128 test encryption failed.
encrypt-dsa.test.log: Rijndael-128 test encryption failed.
seat.test.log: Rijndael-128 test encryption failed.
encryptp.test.log: Rijndael-128 test encryption failed.
armencrypt.test.log: Rijndael-128 test encryption failed.
armencryptp.test.log: Rijndael-128 test encryption failed.
signencrypt.test.log: Rijndael-128 test encryption failed.
armsignencrypt.test.log: Rijndael-128 test encryption failed.
conventional.test.log: Rijndael-128 test encryption failed.
conventional-mdc.test.log: Rijndael-128 test encryption failed. [2x]
--------------------------------------------------------------------


In some logfiles (e.g. armsignencrypt.test.log) I see also the
following message, but I'm unsure if it is relevant here:
--------------------------------------------------------------------
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: weak key created - retrying
gpg: fatal: cannot avoid weak key for symmetric cipher; tried 16 times!
secmem usage: 3360/4064 bytes in 7/9 blocks of pool 4064/32768
--------------------------------------------------------------------

But this additional message is not always present, e.g. in
conventional.test.log missing.

Anybody seen this too? If so, how has it been solved?

Thanks in advance.

Regards,
	Klaus.
-- 
Klaus Singvogel  -  Maxfeldstr. 5  -  90409 Nuernberg  -  Germany
Phone: +49-911-74053-0
GnuPG-Key-ID: 1024R/5068792D  1994-06-27
SUSE LINUX Products GmbH,  GF: Markus Rex,  HRB 16746 (AG Nuernberg)