netpgpverify supporting newer gnupg key format

[Jonathan Perkin <jperkin%pkgsrc.org@localhost>]

Hi,

This is a courtesy to note that I'll be committing code to make 
netpgpverify, and thus signed packages, work with gnupg newer than 2.0.x 
shortly to my TritonDataCenter fork.

This is something I've wanted for a long time but didn't know enough 
about PGP key formats to do anything about it, and so have had to 
maintain a crufty old gnupg20 build to keep signed packages working.  
This fails pretty hard since the libassuan 3.x update in pkgsrc a while 
back, and I've had various patches to try and keep it working.

Today I was trying to diagnose another issue with it, and eventually 
gave up and just asked an LLM to enhance netpgpverify to Just Make It 
Work with latest GnuPG, and it did with a single prompt in about 10 
minutes.

Thus, DO NOT take this code and import into pkgsrc or NetBSD, or even 
view it if you don't want to be tainted.  I know some folks pull patches 
from my fork without review, and I just want to make it absolutely clear 
that you should not do this in this instance as the NetBSD guidelines 
are very clear that no LLM code is acceptable (even though in my opinion 
the code changes turn out to be absolutely trivial and could not 
reasonably be interpreted as containing someone else's work).

Obviously this has high chance of bikeshed, so I'll pre-empt that by 
saying I won't be responding further on this thread.  I just wanted to 
make sure that I am not liable in any way should someone go browsing my 
fork and pull things they should not.

Hopefully one day someone other than me will want to ship signed 
packages, and will be able to fix this independently, because trying to 
maintain GnuPG 2.0.x at this point is pretty untenable.

Thanks for reading,

--
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com