
Prefer most up to date version of pinentry
Reported by Luke Le | March 1st, 2012 @ 11:33 PM
Currently Libmacgpg ships with its own version of pinentry.
The release cycles for Libmacgpg and MacGPG2 are very different
with Libmacgpg
being released with every new version of either GPGKeychainAccess,
GPGServices or
GPGMail and MacGPG2 is only updated for new version of GPG2 or
bugfixes.
As proposed by cfraire (Chris) Libmacgpg should check if the
internally shipped version of pinentry is newer than the one of the
MacGPG2 distribution and choose the newer one.
This would also already solve the problem of a lot of users wanting
to copy & paste into pinentry window which is currently
supported by the Libmacpgp shipped pinentry version,
but not by the MacGPG2 shipped version.
Cfraire also already implemented it.
Comments and changes to this ticket
-
-
C Fraire March 1st, 2012 @ 11:41 PM
I should say that what I implemented was for GPGMail, GPGServices, etc. to prefer their bundled version.
If what is desired is to do bundle version comparisons, that is slightly more complicated, and it necessitates digging into each pinentry-mac's version and writing a comparator for the current GPGTools style version strings (e.g., "2.0a31").
-
Luke Le March 1st, 2012 @ 11:43 PM
I think it's alright to check only the internal version vs. the MacGPG2 version for now.
We've discussed distributing Libmacgpg as separate framework which all other apps use.
If we do that we'll end up with only two different pinentry versions. -
-
Mento March 4th, 2012 @ 02:00 PM
- State changed from open to fixed
-
steve August 14th, 2013 @ 02:42 PM
- Tag cleared.
- Importance changed from to Low
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป