FS#31900 - [gnupg] bug importing X.509 certs

Attached to Project: Arch Linux
Opened by André Nascimento (Andrenas) - Thursday, 11 October 2012, 15:57 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 08 December 2012, 03:15 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

Gpgsm and kleopatra fail to import X.509 (.p12) certificates. The gpg-agent is running and all tests done by Kleopatra gave ok.

Gpgsm:

gpgsm --import foo.p12
gpgsm: enabled debug flags: assuan
gpgsm: DBG: connection to agent established
gpgsm: gpgsm: GPG_TTY has not been set - using maybe bogus default
gpgsm: gpg-protect-tool: error while asking for the passphrase: End of file
gpgsm: error running `/usr/lib/gnupg/gpg-protect-tool': exit status 2
gpgsm: total number processed: 0
secmem usage: 0/16384 bytes in 0 blocks


Kleopatra: "Decryption failed"


But if we compile the gnupg with the patch identifyed on comment # 43 of https://bugzilla.redhat.com/show_bug.cgi?id=548528, the error it's gone.


Additional info:
* package version(s):

- gnupg 2.0.19-2;
- kdepim-kleopatra 4.9.2-1;
- uname -a
Linux foo 3.5.6-1-ARCH #1 SMP PREEMPT Sun Oct 7 19:33:50 CEST 2012 i686 GNU/Linux


* config and/or log files etc.


Steps to reproduce:

gpgsm --import foo.p12;

Kleopatra: Import Certificate foo.p12;
This task depends upon

Closed by  Gaetan Bisson (vesath)
Saturday, 08 December 2012, 03:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  gnupg-2.0.19-3 in [testing]
Comment by Gaetan Bisson (vesath) - Friday, 12 October 2012, 03:54 GMT
Before doing any patching, I would like upstream to clarify the status of: https://bugs.g10code.com/gnupg/issue1402

See: http://lists.gnupg.org/pipermail/gnupg-devel/2012-October/026971.html
Comment by Mike Cloaked (mcloaked) - Friday, 07 December 2012, 21:06 GMT
Is there any progress on this? I just started using kmail and was struggling to import my s/mime certificates until I eventually came across this bug report.

Is there currently any workaround until this is fixed upstream or in arch?

Thanks for any help -

Loading...