Re: Problem with verifying signatures in GPGME

--===============3420203732475249181==
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="Er0RHNE4ydUFzxTv"
Content-Disposition: inline


--Er0RHNE4ydUFzxTv
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Robert J. Hansen via Gnupg-devel wrote:
> I have a not-quite-toy example of GPGMEPP up on GitHub:
>=20
> 	https://github.com/rjhansen/egon
>=20
> It does nothing except pull down Proton Mail keys from their web API and
> import them into GnuPG. As others have pointed out, there are better ways=
 to
> do this, so I don't recommend using this tool for that purpose: but as a
> minimalist app to get someone started with the C++ bindings for GPGME, it
> might be useful to you.

I noticed the README.md for egon says:

    Egon also uses [GnuPG](https//gnupg.org)=E2=80=99s GnuPG Made
    Easy library

The colon is missing after https, which leads to the link
being generated incorrectly. :)

--=20
Todd

--Er0RHNE4ydUFzxTv
Content-Type: application/pgp-signature; name=signature.asc

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

iHUEARYIAB0WIQSvlwC4tRNlCF6x+moHOcdGE+n45gUCac/6zQAKCRAHOcdGE+n4
5jIEAP9B8KDblx64rVM1G9vxhN8fSA+MsORvRK2mJ/n7fpJH5gEAoIOSjiivoraQ
tbSQwWkPlRTmwPOC0lirmq93RJ0cogA=
=x38j
-----END PGP SIGNATURE-----

--Er0RHNE4ydUFzxTv--


--===============3420203732475249181==
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

--===============3420203732475249181==--