Most of our users are already running the latest version of GPG Suite, but everyone who hasn't upated to GPG Suite 2015.06 yet, should update to the latest GPG Suite as soon as possible. This security issue has been fixed in GPG Suite 2015.06. We would especially like to thank Bruno Bierbaumer for bringing a bug in one of Libmacgpg's subcomponents to our attention which could be abused by a local user to execute shell commands with root privileges (CVE-2014-4677). Creating, Installing, and Using Self-Signed Certificates in OS 10.4 Tiger through 10.15 Catalina and Mail 2 (Tiger) through Mail 13 (Catalina) with side explorations into Being Your Own Certificate Authority and transferring the Mac-made security credentials to an iPhone 4S running iOS 9. We'll include it in our nightly builds for early testers once available. Work on OS X El Capitan is progressing very well and a first test version will be ready soon. Since this particular bug also affected other components, all of our tools should now be even more reliable. If you used DSA keys to log in to your SSH server and have upgraded your client machine to macOS Sierra (or OSX Sierra if you like), you probably ran into this problem: The answer to this problem.
Well, we're happy to say, we've squashed this bug! The only workaround was to restart your mac. Many of you might have experienced Mail.app no longer signing messages and reporting a "No pinentry" error. If you rely on GPGMail, please refrain from updating to macOS Sierra for the time being' See Cowcides post below for the link to a workaround for those of us who moved to Sierra. We are however very happy to say, that one of our longest standing bugs has been squashed. The current word from the GPGTools team: 'GPGMail, our plugin for securing emails using GPG in Mail.app is not yet compatible with macOS Sierra. Our newest release is mostly a bug fixing release for the most pressing issues.
0 kommentar(er)
