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. Fix: Install security/pinentry 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.
To which of the 3 ports does your suggested fix apply?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 8 Dec 2010 06:15:28 +0000 Mark Linimon <linimon@lonesome.com> wrote: > To which of the 3 ports does your suggested fix apply? To security/gpgme. Sorry about not stating that. - -- I don't mind being accused of being an "escapist." On a planet that increasingly resembles one huge Maximum Security prison, the only intelligent choice is to plan a jail break. - Robert Anton Wilson -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (FreeBSD) iEYEARECAAYFAkz/J9YACgkQh2Se1CB7M2FHJACfXWPiZhQ1eJZOFiJJHvXzUlN/ Gq8AoIMDB+bFC9RRMH9twCNYlyS566L0 =3zBQ -----END PGP SIGNATURE-----
I don't think adding security/pinentry as a dependency to security/gpgme is the correct way to approach this. Gpgme is sort of a "middle-man" application and this sort of dependency either belongs at the very bottom or the very top. Not every port that uses gpgme requires pinentry, nor is it a requirement for gpgme itself to run properly. Pinentry is required for use with gpg-agent which is part of gnupg 2.x (this is stated in the pkg-message for security/gnupg). The biggest problem with adding security/pinentry as a direct dependency is that it pulls in all the major x11 toolkits by default (gtk1, gtk2, qt3, qt4) and I don't think most users want that. Users should install the flavor of pinentry that goes with their application. I think maybe the best solution would be for the maintainer of mail/sylpheed3 to add a runtime dependency on security/pinentry-gtk2 if the GPGME option is selected (I've CC'd him). - Jason
Responsible Changed From-To: freebsd-ports-bugs->oliver over to sylpheed3 maintainer
Responsible Changed From-To: oliver->ehaupt I will take care of it.
ehaupt 2011-07-27 14:57:10 UTC FreeBSD ports repository Modified files: mail/sylpheed3 Makefile Log: Add security/pinentry-gtk2 as a run dependency if the GPGME option is selected. This does not add any additional dependencies other than security/pinentry-gtk2 itself as opposed to adding security/pinentry. PR: 152888 (based on) Submitted by: Kenneth Lind <exil@sasurai.se>, Jason E. Hale <bsdkaffee@gmail.com> Revision Changes Path 1.182 +3 -1 ports/mail/sylpheed3/Makefile _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
State Changed From-To: open->closed Committed, thanks!