Re: Problem with verifying signatures in GPGME

--===============8178949422336323400==
Content-Type: multipart/signed; boundary="nextPart2783004.lGaqSPkdTl";
 micalg="pgp-sha512"; protocol="application/pgp-signature"

--nextPart2783004.lGaqSPkdTl
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Ingo =?UTF-8?B?S2zDtmNrZXI=?= <[email protected]>
To: [email protected]
Reply-To: [email protected]
Subject: Re: Problem with verifying signatures in GPGME
Date: Fri, 03 Apr 2026 21:24:48 +0200
Message-ID: <2341963.vFx2qVVIhK@daneel>
In-Reply-To: <[email protected]>
MIME-Version: 1.0

On Freitag, 3. April 2026 16:14:49 Mitteleurop=C3=A4ische Sommerzeit Fabio=
=20
d'ORTOLI-GALERNEAU via Gnupg-devel wrote:
> I'm having a problem with a C++ code using GPGME and I was advised to
> ask about my problem here.
>=20
> The program is supposed to verify some signatures inputed in it.
> Basically it works for keys generated with my computer but not for some
> reason on ones that are not (it returns a 0 summary),

A 0 summary is a perfectly valid summary value. It indicates that none of t=
he=20
conditions for a specific bit apply, i.e. the signature is neither "green"=
=20
(which mean it's good and the signer is at least fully trusted) nor "red"=20
(signature is bad) nor is the signature or the signing key expired or revok=
ed=20
or ...

In other words, a 0 summary means: The signature is good (otherwise the RED=
=20
bit would be set), but the signer('s key) is not fully trusted.

> even if I tell it
> to ignore the trust database or to use tofu or whatever trust model.

Did you try with trust model "always"?

> I provided attached a toy version of the code that breaks, can you see
> anything wrong in it or is the problem somewhere else ?

I haven't looked at the code, but if you get a 0 summary for good signature=
s=20
with not fully trusted keys then your code probably works. The only problem=
=20
seems to be that you didn't expect 0 to be a valid summary value. (You are =
not=20
the first person being confused about a 0 summary.)

Regards,
Ingo
--nextPart2783004.lGaqSPkdTl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iJEEABYKADkWIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCadAUABsUgAAAAAAEAA5t
YW51MiwyLjUrMS4xMiwyLDIACgkQsW9ZlRZHSrqzmgD/akZ/khg0G/pdc4IULyvL
ppjAH1Yv8J/f8+b1Cq38alMBAK3jMdMnaESh/p4WsPHzIFqncHdNpa2TU1SnRq4B
NrYD
=gctj
-----END PGP SIGNATURE-----

--nextPart2783004.lGaqSPkdTl--





--===============8178949422336323400==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

--===============8178949422336323400==--