I WIN I WIN I WIN
Feb. 25th, 2004 03:43 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I have finally beat the crap out of that pgp verification of control messages problem. The real issue, of course, was that it wasn't "a problem", it was a whole concatenated shitpile of breakages.
1) The control.org.uk public key is broken, if you're using gpg. You have to remove the extra uid.
2) Our copy of pgpverify is old and broken. The -test option doesn't work, which makes it real fucking hard to debug. (
sweh hacked together a version that did, and I used that for the remainder of my testing.)
3) We didn't have pgpverify set to use gpgv, which is necessary if you're using gpg, oddly enough.
4) We didn't have pgp/gpg keyring location set in innshellvars.
5) We didn't have it set in pgpverify, either. So it was using the default location, which is not where ours is.
6) If you set the keyring directory in pgpverify AND if you let it know you're using gpg, the comments tell you it will look for pubring.gpg in said directory. It lies. It looks for pubring.pgp. Fixed by use of the humble symlink.
I've probably lost a good whomp of SAN working this issue, but I feel this crazed glee, not unlike having slaughtered a shoggoth, I think.
1) The control.org.uk public key is broken, if you're using gpg. You have to remove the extra uid.
2) Our copy of pgpverify is old and broken. The -test option doesn't work, which makes it real fucking hard to debug. (
![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
3) We didn't have pgpverify set to use gpgv, which is necessary if you're using gpg, oddly enough.
4) We didn't have pgp/gpg keyring location set in innshellvars.
5) We didn't have it set in pgpverify, either. So it was using the default location, which is not where ours is.
6) If you set the keyring directory in pgpverify AND if you let it know you're using gpg, the comments tell you it will look for pubring.gpg in said directory. It lies. It looks for pubring.pgp. Fixed by use of the humble symlink.
I've probably lost a good whomp of SAN working this issue, but I feel this crazed glee, not unlike having slaughtered a shoggoth, I think.