GPGMail: using wrong key for signing
I have my default key set to: 4B739609
but every time I send an email it picks A1B0C381 which is my old key.
defaults read org.gpgtools.common is ‘empty’
defaults read | grep -i GPGDefaultKeyFingerprint
gets a hit but I have no idea where this is being set otherwise.
Expected
Expected it to work as it is set up!
macOS 10.12.6 16G29
GPG Suite 2017.1b3 1812 (d43863c)
GPGMail 2.7b3 1215 (d0b5fa0)
GPG Keychain 1.3.3b2 1271 (028a4a2)
GPGServices 1.11 916 (872e77d)
MacGPG2 2.0.30-1b2 887- (4912d26)
GPGPreferences 2.0.2b3 927 (641418e)
Libmacgpg 0.7 782 (536bf51)
pinentry 0.9.7 4 (b75069d)
- 2017-09-02_21-15_DebugInfo.gpg 23.2 KB
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
1 Posted by mike horwath on 02 Sep, 2017 09:17 PM
Screenshot of settings
2 Posted by mike horwath on 02 Sep, 2017 09:21 PM
Added further steps to show problem.
Support Staff 3 Posted by Steve on 02 Sep, 2017 09:21 PM
Hi Mike,
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
Could you please download and install our latest GPG Suite nightly build and see if the problem persists. That page also has sig and SHA256 to verify the download.
All the best,
steve
Disclaimer: This is a development version which has not been thoroughly tested yet - bugs or crashes are to be expected. Thanks for helping us test.
4 Posted by mike horwath on 02 Sep, 2017 09:27 PM
GPGTools 1952n worked.
Is this a known problem?
5 Posted by mike horwath on 02 Sep, 2017 09:27 PM
% defaults read org.gpgtools.common 2017-09-02 16:27:37.205 defaults[94924:31281893]
Domain org.gpgtools.common does not exist
Support Staff 6 Posted by Steve on 02 Sep, 2017 09:36 PM
Yes, it is listed as issue #895 under Known Issues:
https://gpgtools.org/releases/gpgsuite/2017.1b3/pre-release-notes.html
The fix will be included in the next release.
7 Posted by mike horwath on 02 Sep, 2017 09:40 PM
Thank you very much for the quick turnaround.
Support Staff 8 Posted by Steve on 02 Sep, 2017 10:16 PM
No problem. Glad, the fix is working as expected. I'm closing this discussion. Should you need further assistance or have questions you can re-open this discussion here or open a new one any time.
Best, steve
Steve closed this discussion on 02 Sep, 2017 10:16 PM.