Problem with verifying signatures in GPGME

[Todd Zullinger]

Robert J. Hansen via Gnupg-devel wrote:
> I have a not-quite-toy example of GPGMEPP up on GitHub:
> 
> 	https://github.com/rjhansen/egon
> 
> 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)’s GnuPG Made
    Easy library

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

-- 
Todd
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20260403/dbb95dea/attachment.sig>