GnuPG 1.9.16/17 (S/MIME and gpg-agent) , importing pkcs12 fails: Invalid digest algorithm

thomas schorpp t.schorpp at gmx.de
Tue Jun 21 11:06:56 CEST 2005


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

hello,

Werner Koch wrote:
> Hello!
> 
> We are pleased to announce the availability of GnuPG 1.9.17 
> Happy hacking,
> 
>   Werner
> 

me too :)

1. verifying telesec/regTP signed t-com bills works.

2. importing mozilla certmngr exported CACert.org cert doesnt work:

(gdb) run
Starting program: /usr/local/bin/gpgsm --import cacert-schorpp.p12
gpgsm: NOTE: THIS IS A DEVELOPMENT VERSION!
gpgsm: It is only intended for test purposes and should NOT be
gpgsm: used in a production environment or with production keys!
gpgsm: gpgsm: GPG_TTY has not been set - using maybe bogus default
gpgsm: gpg-protect-tool: gpg-agent is not available in this session
gpgsm: gpg-protect-tool: error while asking for the passphrase: Invalid
digest algorithm xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
gpgsm: error running `/usr/local/libexec/gpg-protect-tool': exit status 2
gpgsm: total number processed: 0
random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
secmem usage: 0/16384 bytes in 0 blocks

Program exited with code 02.
(gdb)

schorpp at tom1:~/data/tcom$ gpgsm --import thawte-schorpp.p12
gpgsm: NOTE: THIS IS A DEVELOPMENT VERSION!
gpgsm: It is only intended for test purposes and should NOT be
gpgsm: used in a production environment or with production keys!
gpgsm: gpgsm: GPG_TTY has not been set - using maybe bogus default
gpgsm: gpg-protect-tool: gpg-agent is not available in this session
gpgsm: gpg-protect-tool: error while asking for the passphrase: Invalid
digest algorithm
gpgsm: error running `/usr/local/libexec/gpg-protect-tool': exit status 2
gpgsm: total number processed: 0
random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
              outmix=0 getlvl1=0/0 getlvl2=0/0
secmem usage: 0/16384 bytes in 0 blocks
schorpp at tom1:~/data/tcom$

tom1:/home/schorpp/data/tcom# ldd /usr/local/bin/gpgsm
        libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0xb7f7b000)
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xb7f76000)
        libksba.so.8 => /usr/local/lib/libksba.so.8 (0xb7f43000)
        libpth.so.20 => /usr/lib/libpth.so.20 (0xb7f30000)
        libdl.so.2 => /lib/tls/libdl.so.2 (0xb7f2d000)
        libz.so.1 => /usr/lib/libz.so.1 (0xb7f1b000)
        libc.so.6 => /lib/tls/libc.so.6 (0xb7de6000)
        libnsl.so.1 => /lib/tls/libnsl.so.1 (0xb7dd1000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xb7fea000)
tom1:/home/schorpp/data/tcom#

bug? workaround? ideas?

thx
y
tom





-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iQCVAwUBQrfYrGqsze5HSzyoAQNTAwP/WUK8WtVzYwPqRJBEsUh8+WXszzyDx5p/
Tu5R/qpTxMDhQ97Wo8r0x17oJs7ql+CUcqjPL86wlzypu3kviqEuZnw3hxFek3mc
VmILSWHEBDfpF/j5NcGyYxMnEvgrikMCGtqp4OAd86B5i9ZgPgf0lD9puO7q4hJ/
u5gjA+KUEK8=
=B3uk
-----END PGP SIGNATURE-----



More information about the Gnupg-devel mailing list