You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2019. It is now read-only.
When the key server is not available and one got an email which is signed with a key that the extension has never seen, it would report "BAD signature". It makes me feel like there is an active attack going on. However, it is not.
So, would it be making more sense to report "key server not available" in this case?
Here is the screenshot of the error:
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When the key server is not available and one got an email which is signed with a key that the extension has never seen, it would report "BAD signature". It makes me feel like there is an active attack going on. However, it is not.
So, would it be making more sense to report "key server not available" in this case?
Here is the screenshot of the error:
The text was updated successfully, but these errors were encountered: