Date: Tue, 7 Dec 2010 13:43:01 GMT From: Kenneth Lind <exil@sasurai.se> To: freebsd-gnats-submit@FreeBSD.org Subject: ports/152888: ** Sylpheed-WARNING: pgp_sign(): signing failed: Message-ID: <201012071343.oB7Dh13k030789@red.freebsd.org> Resent-Message-ID: <201012071350.oB7DoAtW066510@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 152888 >Category: ports >Synopsis: ** Sylpheed-WARNING: pgp_sign(): signing failed: >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Dec 07 13:50:09 UTC 2010 >Closed-Date: >Last-Modified: >Originator: Kenneth Lind >Release: 8.1-RELEASE >Organization: >Environment: FreeBSD zappa 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Thu Jul 22 18:28:17 CEST 2010 root@:/usr/obj/misc/shared/FreeBSD/8.1/src/sys/FLY i386 >Description: A long-time headache of mine has a solution. Signing and encrypting in mail/sylpheed* with security/gpgme dependent on security/gnupg fails, and gives only the following statement in the sylpheed log: "** Sylpheed-WARNING: pgp_sign(): signing failed: ..." And "gpg --edit-key" results in "gpg-agent[5460]: can't connect to the PIN entry module: ..." Using security/gpgme with security/gnupg1 produces no such error. After searching the web for a while, I found a solution. Adding security/pinentry solved both those problems fairly easy. So where am I going with this? I am suggesting to add security/pinentry as a dependency when security/gpgme is used in conjunction with security/gnupg. Or at least to make it an option. >How-To-Repeat: Install: mail/sylpheed3 security/gnupg security/gpgme Create an account, a key, and try so send a signed and/or encrypted e-mail. >Fix: Install security/pinentry >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201012071343.oB7Dh13k030789>