Jameson Graef Rollins wrote: > Hey, Joey. None of the assword modules have been updated recently. The > only thing that has been updated recently that might trigger this issue > is python-gpgme. > > The exception that we're seeing in this case is a by-product of a gpg > signature validation error. It appears that maybe the validity of the > key that signed your assword database has changed. It's possible that a > python-gpgme or gnupg update could have "caused" this, but my guess is > that it more likely has to do with the key validity itself. Do you know > if that has changed at all recently?
It seems that assword fails if the key used to sign the file is not marked as ultimately trusted. Personally, I have no use for gpg's trustdb (it's slow, and I don't trust transitively), and so I have no-auto-check-trustdb set, and had not set a trust level on my key. I think that assword should still function in this configuration. -- see shy jo
signature.asc
Description: Digital signature
