saturneric / GpgFrontend

A free, open-source, robust yet user-friendly, compact and cross-platform tool for OpenPGP encryption. It stands out as an exceptional GUI frontend for the modern GnuPG (gpg).
https://gpgfrontend.bktus.com
GNU General Public License v3.0
450 stars 43 forks source link

during verification "A Signature Not Fully Valid. (May used a subkey to sign)" #120

Closed marcof333 closed 7 months ago

marcof333 commented 7 months ago

In "Computer A", I generate a keypair and I export the" Public key A" as .asc. I use the "Private key A" to sign the doc that I encrypt for "Computer B" (whose "Public key B" was previously imported in ComputerA as .asc). Now in Computer B I import the" Public key A" as .asc. And I decrypt&verify the document above. I got this error message "A Signature Not Fully Valid. (May used a subkey to sign)"

here below the full message. thanks.

[#] Verify Operation [Success] ------------> [>] Signed On(UTC) 2023-11-01T22:31:10

[>] Signatures List: Signature [1]: A Signature Not Fully Valid. (May used a subkey to sign) Signed By: [omitted xxxxxxxxxxxxxx] Public Key Algo: RSA Hash Algo: SHA1 Date(UTC): 2023-11-01T22:31:10

<------------

saturneric commented 7 months ago

From what you've described, it appears that the setup was done correctly. However, the error message "A Signature Not Fully Valid. (May used a subkey to sign)" can indeed be confusing. Let me offer some clarification to help resolve this issue.

One key aspect to check is the Trust Level of the public key on Computer B, especially for the key imported from Computer A. The trust level plays a crucial role in the verification process. If it's not appropriately set, it can lead to verification errors. To adjust this:

  1. Navigate to either "Keybox Tool" or "KeyPair Management".
  2. Right-click on the key in question.
  3. Select "Set Owner Trust Level".
  4. If you're confident about the trustworthiness of the public key you've imported, choose "Ultimate" as the trust level.
image

The operations above may work as I tested it.

I understand that the information displayed can be confusing, and I assure you that we will work on making it clearer in future updates. I appreciate your patience and are grateful for your use of our software.

marcof333 commented 7 months ago

SOLVED. thanks for your feedback. I applied the procedure and now it works, this is the final new message I get (without any error): [#] Verify Operation [Success] ------------> [>] Signed On(UTC) 2023-10-29T11:25:27 [>] Signatures List: Signature [1]: A Good Signature Fully Valid. Signed By: [omitted xxxxxxxxxxxxxx] Public Key Algo: RSA Hash Algo: SHA512 Date(UTC): 2023-10-29T11:25:27 <------------

By the way I take this occasion to highlight you that I have a different graphical interface compare to your screenshot, I attache a pdf with some screenshots. My version is 2.1.1_Linux-5.15.0-69-generic_x86_64_Release MANY THANKS.

ULTIMATE key setting.pdf

saturneric commented 7 months ago

Okay. It's nice to hear that.

saturneric commented 7 months ago

By the way I take this occasion to highlight you that I have a different graphical interface compare to your screenshot, I attache a pdf with some screenshots.

I forgot that I was using an under-developing version which hasn't released yet. ;)