> > And we, the FreeBSD Project, don't do a thing to help this situation.
> > We change the SSH keys on the freebsd.org machines left and right w/o
> > *ANY* notice to committers that they have been changed. So we've trained
> > our own committers to have sloppy habits that could lead a malicious code
> > added to the FreeBSD CVS source repository.
>
> Is this correct?????
No, in several particulars. "The FreeBSD Project" doesn't change the SSH
keys on the FreeBSD.org machines. Notice is given when they are intention
ally changed. The FreeBSD Project doesn't "train" committers to have
sloppy habits.
David has probably been drinking too much; it's Christmas, after all.
There were a couple of incidents some time back when freefall's SSH keys
were accidentally overwritten due to failure to follow procedure by
individual administrators. The lengthy discussions which followed these
incidents could not possibly have been construed as "training committers
to have sloppy habits".
> Can anyone confirm this.
No. But I'm damn sure that you'd have been fleeing Grover's Mill with
the rest of the sheep.
> JKH, DG, CORE respond.
Jordan is in Europe. David is unlikely to pay any attention to this sort
of noise. Core does not administer the FreeBSD.org machines, and if you
get a response at all, it will probably be "you are talking to the wrong
people".
Regards,
Mike Smith
FreeBSD Project Core team member, FreeBSD.org admin team member.
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
