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 16:08:32 CEST 2005
thomas schorpp wrote:
> thomas schorpp wrote:
>
>>Werner Koch wrote:
>>
>>
>>>On Tue, 21 Jun 2005 12:17:37 +0200, thomas schorpp said:
>>>
>>>
>>
>>
>>>>schorpp at tom1:~/data/tcom$ gpg-agent --daemon
>>>>GPG_AGENT_INFO=/tmp/gpg-xXQRRa/S.gpg-agent:14368:1; export GPG_AGENT_INFO;
>>>
>>>
>>> @noindent
>>> The usual way to run the agent is from the @code{~/.xsession} file:
>>>
>>> @example
>>> eval `gpg-agent --daemon`
>>> @end example
>>>
>>
>>
>>schorpp at tom1:~/data/tcom$ /usr/local/bin/gpg-agent --daemon
>>--write-env-file $HOME/.gpg-agent-info --enable-ssh-support
>>can't connect to `/home/schorpp/.gnupg/log-socket': Connection refused
>>GPG_AGENT_INFO=/tmp/gpg-Ugm3lS/S.gpg-agent:17174:1; export
>>GPG_AGENT_INFO; XXX nothing gets exported here! XXXX
>>SSH_AUTH_SOCK=/tmp/gpg-qebPDA/S.gpg-agent.ssh; export SSH_AUTH_SOCK;
>>SSH_AGENT_PID=17174; export SSH_AGENT_PID;
>>
>>schorpp at tom1:~/data/tcom$ export GPG_AGENT_INFO=/tmp/gpg-Ugm3lS/S.gpg-agent
>>
>>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: malformed GPG_AGENT_INFO environment variable ???
>>gpgsm: gpg-protect-tool: error while asking for the passphrase: Invalid
>>digest algorithm XXX catch all error message? XXX
>>
>>
>>
>
>
> http://lists.debian.org/debian-devel-announce/2005/03/msg00020.html
>
> Package: gnupg-agent (debian/main)
> Maintainer: Matthias Urlichs <smurf at debian.org>
> 300128 [ ] [X] gnupg-agent: gpg-agent doesn't set environment
> variable $GPG_AGENT_INFO
>
> aha ;)
>
> anyway.. doesnt solve the problem.
>
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-devel
>
>
ok, pointing the right pinentry is ok:
schorpp at tom1:~/data/tcom$ /usr/local/bin/gpg-agent --daemon
--write-env-file $HOME/.gpg-agent-info --enable-ssh-support --verbose
--pinentry-program /usr/bin/pinentry
GPG_AGENT_INFO=/tmp/gpg-JRoQxZ/S.gpg-agent:18107:1; export GPG_AGENT_INFO;
SSH_AUTH_SOCK=/tmp/gpg-okoL0O/S.gpg-agent.ssh; export SSH_AUTH_SOCK;
SSH_AGENT_PID=18107; export SSH_AGENT_PID;
schorpp at tom1:~/data/tcom$
schorpp at tom1:~/data/tcom$
schorpp at tom1:~/data/tcom$
schorpp at tom1:~/data/tcom$ export
GPG_AGENT_INFO=/tmp/gpg-JRoQxZ/S.gpg-agent:18107:1
schorpp at tom1:~/data/tcom$
schorpp at tom1:~/data/tcom$
schorpp at tom1:~/data/tcom$ 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: error at "bags", offset 24 XXXXXXXXXXXXXXXXX
gpgsm: gpg-protect-tool: error parsing or decrypting the PKCS-12 file
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$
More information about the Gnupg-devel
mailing list