[prev in list] [next in list] [prev in thread] [next in thread]
List: pgp-keyserver-folk
Subject: Signature decode failed
From: Erja Kinnunen <ehkinnun () csc ! fi>
Date: 1998-04-27 6:58:47
[Download RAW message or body]
Hi,
when I was initializing our database I encountered the same problem.
I tried to copy the keyring from several servers but the result was the same.
I couldn't find out what caused the problem, but I tell you how I could
bypass it:
- I printed out the index from the pubring
- found out the defected key (the one after the last key that was added
to the db)
- removed the corrupted key using pgp kr
- started the add procedure again
This time all the remaining keys were added ok.
The strange thing is, that I can add the "corrupted key" to the database
using the web browser without any error messages or database corruption.
Regards, Erja
--------
# pksclient /web/var/pks.new create
kd_create: flags=0
kd_create: completed successfully
kd_close: completed successfully
Database files created in /web/var/pks.new
# pksclient /web/var/pks.new add /web/var/ring/pubring.pgp
kd_open: completed successfully
kd_add: flags=100000
display_new_key: new keyid 1 5EEE2CE5
display_new_key: new keyid 2 95E7B69D
.....
display_new_key: new keyid 410 77B85731
display_new_key: new keyid 411 B74D506D
kd_sync: completed successfully
kd_add: completed with error
database add failed: Key block corrupt: signature decode failed
kd_close: completed successfully
*------------------------------------------------------------------------*
| Erja Kinnunen Email: erja.kinnunen@csc.fi |
| FUNET, CERT coordinator phone: +358-9-457 2913 |
| CSC - Center for Scientific Computing fax: +358-9-457 2302 |
| P.O.Box 405 |
| Fin - 02101 Espoo |
*------------------------------------------------------------------------*
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic