Re: Look at these update from M$ Corporation.
On Fri, Aug 01, 2003 at 10:46:28AM -0700, Alan Connor wrote:
> Colin Watson wrote:
> > On Fri, Aug 01, 2003 at 02:04:28AM -0700, Alan Connor wrote:
> > > Anyone with a C-R program would just put the bug-tracking addresses on
> > > their pass list.
> > >
> > > That's how C-R programs work. The bug-track folks wouldn't even know
> > > it was operating.
> > Speaking as one of the bug tracking system maintainers in question, I
> > can tell you that this is not universal practice.
> It is the "user" of the C-R program that enters the bug-tracking addresses
> (in this case) in their passlist. The C-R program is transparent to the
> bug-track folks, in this case.
> Please do not expect another response from me on this subject. You either
> do not understand C-R programs at all, or are simply prejudiced against
> them and are cleverly spreading dis-information.
I think you somehow misspelled "facts" as "disinformation". I have the
firstname.lastname@example.org mail to prove it, and I know for a fact that your
claim that "the bug-track folks wouldn't even know it was operating" is
not always true, because I am one of those folks and I have known on a
number of occasions that challenge-response systems were operating.
It's true that people who have configured their challenge-response
systems carefully don't cause challenges to be sent places like
owner@bugs. They're transparent if and only if well-configured. However,
just like many other pieces of software, not everybody configures them
Also, people who just fire off one bug report to Debian and aren't
particularly involved in the project usually don't know to expect the
closing acknowledgement from owner@bugs, so they often generate a
challenge in response to the automatically generated message telling
them that their bug has been closed. For practical reasons we have to
filter off mail with an empty return-path into a separate mailbox which
doesn't get looked at very often because they're mostly bounces, so
those people unfortunately almost never get told that their bug has been
closed (in fact I've only just seen a number of the challenges having
gone and looked in said mailbox while writing this post). Those are the
realities of running a large bug tracking system. *shrug*
No more response is fine by me, but I thought I'd clarify my earlier
Colin Watson [email@example.com]