And for them there needs to be a GUI package. ![]() There are a lot of users out there that will not fiddle with command lines, brew or otherwise. Whether it’s paid or not, my suggestion for GPGTools is to drop MacGPG and start using an upstream version in the Suite. GPGTools are planning to move to a paid release of GPG Suite. Many times when a new version of OS X comes out GPGTools has been a little late in getting a compatible version out. ![]() How would one go about fixing this issue for upstream? Has GPGTools contributed anything regarding this other than the initial discussion about the issue? Upstream still does have the issue which now seems to have been fixed in the fork but in a binary removed from upstream… libexec/gnupg-pcsc-wrapper which has been modified in commit f4c3e1bb to fix the issues of scdaemon hanging in Yosemite. Case in point: Has the fix for gpg-agent / scdaemon hang been discussed upstream at all, ? In MacGPG there is still. Instead they should use upstream and contribute the minimal amount of wrappers or fixes upstream. *I think there is no more reason to develop MacGPG*, i.e. Anyone can easily install either 1.x or 2.0.x via brew or another preferred method of installing their command line tools. Today the situation is very much different. As I recall there were a couple of ports making a working Mac version and MacGPG was / evolved from one of them. MacGPG: Years back there was no easy way of getting upstream GnuPG working on a Mac. I’ve been planning on writing a request to for downsizing / pivoting the project. If one doesn’t use Apple Mail there is no reason to use GPGTools at all. I’ve talked about this setup before in the thread. *just one of the things in the GPG Suite*. I happen to use Mail so for a long time I’ve been using the GPGMail plugin with a brewed upstream GnuPG. GPGPreferences (OS X preferences GUI for some options (gpg.conf) GPGServices (OS X Services menu tools for OpenPGP actions) GPG Keychain (GUI tool for generating and managing keys) GPGTools makes an installer, GPG Suite, which provides the following: Months went by when their Yosemite betas were not available in source at all and development was happening in a separate repository closed from the public. For some time I've disliked the way the project is being run, the communication of what they are planning and the way they have been doing their development for example. I’ve had some concerns about GPGTools for months now. Next message: Please remove MacGPG from due to serious security concerns.Previous message: Please remove MacGPG from due to serious security concerns.Please remove MacGPG from due to serious security concerns Ville Määttä mailing-lists at Please remove MacGPG from due to serious security concerns
0 Comments
Leave a Reply. |