tag:gpgtools.tenderapp.com,2011-11-04:/discussions/problems/25594-when-your-own-key-is-expired-error-message-is-confusingGPGTools: Discussion 2019-07-01T09:38:26Ztag:gpgtools.tenderapp.com,2011-11-04:Comment/341628532014-08-18T18:03:53Z2014-08-18T18:03:53ZWhen your own key is expired, error message is confusing.<div><p>Hi Ryan,</p>
<p>we've a ticket for this problem:</p>
<ul>
<li><a href=
"https://gpgtools.lighthouseapp.com/projects/65684-gpg-keychain-access/tickets/59">
https://gpgtools.lighthouseapp.com/projects/65684-gpg-keychain-acce...</a></li>
<li><a href=
"https://gpgtools.lighthouseapp.com/projects/65764/tickets/710">https://gpgtools.lighthouseapp.com/projects/65764/tickets/710</a></li>
</ul>
<p>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.</p>
<p>So I totally agree this should exist. It does not, means: we
need dev time to implement this, which currently is really
sparse.</p>
<p>Next: let's elaborate on the button states and the messages they
give.</p>
<ol>
<li>
<p>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.</p>
</li>
<li>
<p>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.</p>
</li>
</ol>
<p>Glad you found out the issue at last. Let's hope we can address
this soon.</p>
<p>All the best, steve</p></div>Stevetag:gpgtools.tenderapp.com,2011-11-04:Comment/341628532014-08-18T19:46:05Z2014-08-18T19:46:06ZWhen your own key is expired, error message is confusing.<div><ol>
<li>
<p>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.</p>
</li>
<li>
<p>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.</p>
</li>
</ol>
<p>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?</p></div>Ryan Novosielskitag:gpgtools.tenderapp.com,2011-11-04:Comment/341628532014-08-18T20:03:07Z2014-08-18T20:03:07ZWhen your own key is expired, error message is confusing.<div><p>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.</p>
<p>If you want to contribute a pull request, the source of the
relevant projects is here:</p>
<ul>
<li><a href=
"https://github.com/GPGTools/GPGMail">https://github.com/GPGTools/GPGMail</a></li>
<li><a href=
"https://github.com/GPGTools/GPGKeychainAccess">https://github.com/GPGTools/GPGKeychainAccess</a></li>
<li><a href=
"https://github.com/GPGTools/Libmacgpg">https://github.com/GPGTools/Libmacgpg</a></li>
</ul>
<p>I'm not sure how trivial this is to fix, but fear it doesn't
really qualify for an easy-hack(TM).</p>
<p>But feel free to browse the bug tracker to find other things you
might be interested in working on: <a href=
"https://gpgtools.lighthouseapp.com/dashboard">https://gpgtools.lighthouseapp.com/dashboard</a></p>
<p>Cheers,<br>
steve</p></div>Steve