if things go wrong, error message should differentiate between errors and bad signatures
Reported by Support | October 26th, 2013 @ 10:43 PM
Assigned to Everything #12221.
User reported
- right-click to open an .asc file with GPCServices.service
- signature mismatch reported
- switched to command line
- run gpg --verify
- error message about invalid auto-key-locate configuration
After commenting out the offending configuration line, the command line --verify checked out, and GPCServices.service reported a successful signature check.
It seems like the UI message should definitely differentiate between errors and bad sigs, doesn't it?
Comments and changes to this ticket
-
Shane Green October 27th, 2013 @ 12:46 AM
Thanks very much for your responsiveness and creating a ticket for this issue. I missed the opportunity to respond in the discussion and didn't want to open a new discussion for that, but you folks deserve to know how much your efforts are appreciated. Feel free to not respond and to delete this comment from the bug as I know it doesn't contribute to the actual content. But thanks, in the short time I've been using these tools I've seen them go from being almost beyond a novice such as myself, with many incomplete features, to being almost perfect and easy to use. It's really awesome progress.
-
steve February 24th, 2015 @ 01:23 PM
- Title changed from “Proper error messages so a user actually knows what's going wrong” to “if things go wrong, error message should differentiate between errors and bad signatures”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Alex (via GPGTools)
Luke Le
Shane Green
steve
Support