ksba_crl_parse failed: Invalid CRL object

gnupg at ethen.de gnupg at ethen.de
Fri Dec 14 11:19:32 CET 2007


> Dirmngr only supports binary CRLs.  I have not seen anything about
> an ASCII armor requirement in the specs.  You may use dirmngr-client
> to manualy load the CRL:
>
>   dirmngr-client --load-crl --pem  crl.asc
# dirmngr-client --load-crl --pem  /dev/shm/RSA_Security_2048_v3.asc 
dirmngr-client: loading CRL `/dev/shm/RSA_Security_2048_v3.asc' failed: 
Invalid CRL object

dirmngr[20793.0] DBG: -> OK Dirmngr 1.0.1 at your service
2007-12-14 11:07:56 dirmngr[20793] connection from process 8888 (1002:100)
dirmngr[20793.0] DBG: <- LOADCRL /dev/shm/RSA_Security_2048_v3.asc
2007-12-14 11:07:56 dirmngr[20793] ksba_crl_parse failed: Invalid CRL object
2007-12-14 11:07:56 dirmngr[20793] crl_parse_insert failed: Invalid CRL object
2007-12-14 11:07:56 dirmngr[20793] command LOADCRL failed: Invalid CRL object
dirmngr[20793.0] DBG: -> ERR 150995106 Invalid CRL object <KSBA>
dirmngr[20793.0] DBG: <- BYE
dirmngr[20793.0] DBG: -> OK closing connection

Sorry, that didn't work. Is there a way to unarmor the file?
Other ideas?
I'm surprised at rsasecurity doing something unusual.



More information about the Gnupg-users mailing list