https://bugs.documentfoundation.org/show_bug.cgi?id=160184
--- Comment #6 from Patrick Luby (volunteer) <[email protected]> --- Interestingly, I found that the gpg command (which is what the gpgme code uses to access keys and encrypt data) also expects a public key to have Ownertrust set to Ultimate. The following is what gpg outputs when the [email protected] key in the GPG Keychain application is has Ownertrust set to "Full" or lower. What I think we need is to find out if gpgme has some way to force the "Use this key anyway?" set to "yes" behavior: % gpg -r [email protected] --output blah.encrypted --encrypt blah.txt gpg: B35D2E404496652B: There is no assurance this key belongs to the named user sub rsa4096/B35D2E404496652B 2020-05-04 GPGTools Support <[email protected]> Primary key fingerprint: B97E 9964 ACAD 1907 970D 37CC 8A9E 3745 558E 41AF Subkey fingerprint: 1ACA 7D43 C040 6099 0604 C033 B35D 2E40 4496 652B It is NOT certain that the key belongs to the person named in the user ID. If you *really* know what you are doing, you may answer the next question with yes. Use this key anyway? (y/N) y -- You are receiving this mail because: You are the assignee for the bug.
