Article View: ba.config
Article #25Re: Problems with today's control messages and Web site changes
From: Russ Allbery
Date: Wed, 29 Jul 2009 20:00
Date: Wed, 29 Jul 2009 20:00
44 lines
3137 bytes
3137 bytes
"Adam H. Kerman" <ahk@chinet.com> writes: > Today is Day Nine of the alleged existence of ba.broadcast.moderated. > The issue with the bad keys hasn't been dealt with. The issue of the > erroneous control.ctl entry for the hierarchy hasn't been dealt with. > The key file on the Web site and sample control.ctl entry both continue > to refer to ba.news.config and not ba.config, the former defunct since > 1998. Is naming the wrong newsgroup sufficient for the key to fail? Yes. None of the rest of it has gotten dealt with since I have to do something about it, I have friends here from out of town who can only visit once a year (the only reason why I'm replying to this is because I was checking Usenet briefly before a scheduled day of doing things with them, waiting for them to show up), and I have basically no time to work on this during this week. I was hoping to get it done last week inbetween traveling for a conference, which failed when I got sick on the way back from the conference and spent a couple of days groggy on antihistamines. > The Web site has a text file of the message that would have been in a > checkgroups but no checkgroups has been issued reflecting the change in > the recognized set of newsgroups. When I checked the archived, I > couldn't find that a checkgroups had been issued all year. The hierarchy hadn't previously changed in eons, and I don't think it makes sense for rone to issue a checkgroups until the key stuff is sorted out. > Who is hierarchy administrator and why isn't he following this > discussion? rone is well aware of what's going on and has already been in contact with me. But he can't really do anything about it until I get a chance to untangle the configuration and the key on isc.org. The problem is that the key ID on the key we're distributing doesn't match the configuration in control.ctl, so in order to honor the newgroup, people are going to have to change one or the other. It sucks. Neither he nor I caught that; it's been broken for years, and there just haven't been any changes to the hierarchy. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
Technical Details
Message-ID:
<871vnzi7iy.fsf@windlord.stanford.edu>Path:
arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newsfeed.stanford.edu!news.stanford.edu!not-for-mailReferences:
<h463ag$86t$1@news.eternal-september.org> <h46a9v$8ke$1@news.trigofacile.com> <h46ps3$1j0$1@news.eternal-september.org> <h4q51h$ep2$1@news.albasani.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit Path: arc1-ca.pugleaf.net!g2news2.google.com!news2.google.com!newsfeed.stanford.edu!news.stanford.edu!not-for-mail From: Russ Allbery <rra@stanford.edu> Newsgroups: ba.config,news.admin.hierarchies Subject: Re: Problems with today's control messages and Web site changes Date: Wed, 29 Jul 2009 13:00:37 -0700 Organization: The Eyrie Lines: 44 Message-ID: <871vnzi7iy.fsf@windlord.stanford.edu> References: <h463ag$86t$1@news.eternal-september.org> <h46a9v$8ke$1@news.trigofacile.com> <h46ps3$1j0$1@news.eternal-september.org> <h4q51h$ep2$1@news.albasani.net> NNTP-Posting-Host: windlord.stanford.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.stanford.edu 1248897638 15768 171.67.225.134 (29 Jul 2009 20:00:38 GMT) X-Complaints-To: news@news.stanford.edu User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (gnu/linux) Cancel-Lock: sha1:9IQIPuY5oHDQLUweUlfGJqKCdNI=