-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 19.08.14 20:17, Ville Määttä wrote: > Yeah. Ok. Assuming the Mac guys / fork referred to here are > GPGTools / MacGPG2 I can see a couple bigger issues there than just > patching in support for bigger keys.
Ack. Nevertheless, I don't like some of the other patches. > 1. The package and gnupg2 version used has not been updated since > October 2013 (2013.10.22). If I’m not completely mistaken the > version is still 2.0.22. As discussed on the list, one of the more > important things would be timely updates. [1] Ack. They use the build system from homebrew. They update recipes from time to time, but their releases normally go only with major Mac OS X updates (e.g. 10.8 -> 10.9), as in last october with 2.0.22. Their main target is the gpg-plugin for Apple mail, I think. I have cloned their build system, modify their recipe (mostly take out some patches) and can keep my gpg2 very recent with minimum effort from my side. The supplied pinentry is highly integrated in Mac OS X look and feel and works reliable - no background/foreground issues like the one from gpg4win. But I assume, thats windows' fault, mostly. There is no visible work towards an adoption of gupg 2.1 in their repository. Ludwig -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCgAGBQJT86sOAAoJEA52XAUJWdLjcX8IAKfXKT9OUtvA648kiYSc+vyE Pk160V3NO6C0Tb68wPuaswHUlNtd1ummjqPzhOYlEn99VwYdttODH58RqhwF46CZ A737H7iU3fRL3HRC97dZ+ZbmDvEloYRha0+HRlrUJ2cUm1zbsO3ExulPK8Nhhn1F 4az6GFEZOs2C3lwpBaY7hDeuH+JB+epqpjvBk1DAX452oaMhja1r39s0ja24w9wI mp+k0orZoUEDtlO9LX7YjRzVqkoY/VsFGVTp8wNP/LxmfV75ZaRWG7lir+uWw9x1 1IDfPGrKu9D3birQf1NeJpBLE3vpkC21QoUSdNxgHJqtebGpKZ9OOkSbPI4Eze4= =8ArK -----END PGP SIGNATURE----- _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
