🚀 go-pugleaf

"Adam H. Kerman" <ahk@chinet.com> writes:

> Did I misunderstand what Russ stated earlier?
>
> The control.ctl entry and the public key on your Web site continue to
> refer to the long defunct newsgroup ba.news.config. Isn't correcting all
> that a necessary prerequisite to getting the key to work?

Given that nothing that verifies Usenet control messages does so on the
basis of the contents of a web site, no, it's not.

Step one is getting a combination of PGP key and control.ctl entry that
generates a signed control message which then verifies for someone other
than rone.  Once we figure out which key and control.ctl entry accomplish
that, then we can document it, on that web site and elsewhere.

The problem is, there are two different keys, and those keys have multiple
different user IDs depending on which copy of the key you have because a
change of user ID to match the name of the newsgroup was incompletely
propagated.  It looked like the 632E03A9 key with a user ID of
ba.news.config was the path of least resistance, but I may have been
wrong.  (The correspondence between a user ID and an actual newsgroup is
unnecessary as long as all the configuration lines up.)  However, I can
certainly change the ftp.isc.org configuration to use something different
instead.

It would be nice if, once we get this sorted out, we can tell people to
update only *one* thing, either the PGP keyring or the control.ctl file,
and not ask them to have to update both of them.  We might have marginally
more success at getting this untangled.  Maybe it would be better to go
with the F0BD2595 key and change control.ctl to expect ba.config.  That
is more consistent with the current newsgroup names, even though that
doesn't matter from a technical perspective.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>