When your own key is expired, error message is confusing.
Hi there,
I apparently had not used GPGTools in awhile and my own key had expired. The encrypting and signing buttons showed grayed out. However, the tooltips were both wrong. Encrypting told me that I needed to have at least one recipient, even though I did and their keys were valid. The signing button was also grayed out, but told me (I've lost the exact text now) that I was "missing a private key for ." with just a space there, no mention of what e-mail address' key had expired. I ultimately figured out my own expired, and that solved the problem. I would have solved this 10 minutes earlier though had these errors been accurate.
Thanks for the great product otherwise though!
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
Support Staff 1 Posted by Steve on 18 Aug, 2014 06:03 PM
Hi Ryan,
we've a ticket for this problem:
If this discussion get's closed, it will be re-opened as soon as the ticket is closed so you'll receive a notification. Feel free to open a new discussions should you run into further problems or need assistance.
So I totally agree this should exist. It does not, means: we need dev time to implement this, which currently is really sparse.
Next: let's elaborate on the button states and the messages they give.
encrypt button: did you enter any recipient when you tried that out? because basically that message is correct. You cannot encrypt an email if you do not enter any recipient.
sign button: that message as well is correct. The key expired and expired keys cannot be used to sign anything. Thus the message "you are missing the sec key" is pretty correct. But again, I absolutely agree GPGMail should be much smarter than it currently is and inform the user about the fact that the key connected to the account you are using for signing, now has expired.
Glad you found out the issue at last. Let's hope we can address this soon.
All the best, steve
2 Posted by Ryan Novosielsk... on 18 Aug, 2014 07:46 PM
Yes the recipient was there, which is what made it so confusing, and I verified their key was valid just in case that was the problem.
What was misleading about this is that there was just a blank space where an email address should've been to say which key. I've seen what it does if someone else's key has expired, and it places the email address there before the period. If it had been another key that was invalid, it would have listed the email address there. If it had listed my email address there, it would've been much easier to figure out.
I'm not much of a coder, but I might be able to figure this one out given it's relatively simple. Is there somewhere I should look?
Support Staff 3 Posted by Steve on 18 Aug, 2014 08:03 PM
Ah so the problem with 1. must have been that your own pub key wasn't available. We encrypt all outgoing mail with your own public key, because otherwise you wouldn't be able to read any sent mail later.
If you want to contribute a pull request, the source of the relevant projects is here:
I'm not sure how trivial this is to fix, but fear it doesn't really qualify for an easy-hack(TM).
But feel free to browse the bug tracker to find other things you might be interested in working on: https://gpgtools.lighthouseapp.com/dashboard
Cheers,
steve
Steve closed this discussion on 03 Dec, 2014 07:21 PM.
Steve closed this discussion on 27 Aug, 2018 12:31 PM.