GNOME Bugzilla – Bug 519825
Cert level isn't set when signing a key
Last modified: 2009-03-31 17:51:24 UTC
When signing a key, Seahorse asks for the certification level ('How carefully have you checked this key?'), but regardless of what your choice is, this setting is not added to the signature. This behaviour can be observed by signing a key through Seahorse and then editing a key with command-line gpg. (From Debian bug #468450)
I haven't been able to replicate this with TRUNK i.e. what will become 2.24.0. I did notice when mucking about at the command line that after revoking sigs sometimes the validity isn't changed until you quit and run gpg --update-trustdb. Any signature you make on a key with your own should render it fully valid. If you're talking about trust that's entirely different than what the signing dialog presents to the user. Please let us know if the problem is still present in the latest release (2.23.9x) but I think to fix the issue to the reporter's satisfaction a more detailed report is necessary. Namely because the term 'cert level' isn't used in GPG.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!