Stefano Mazzocchi wrote:
> Steven Noels wrote:
> > Stefano Mazzocchi wrote:
>
> Different would be to have "f**k [insert your favorite public figure
> here]" or child pornography passing thru the system, but in order to
> happen, the chain of events that should happen are:
>
> 1) somebody do
+---+
| Bugzilla Bug ID |
| +-+
| | Status: UNC=Unconfirmed NEW=New ASS=Assigned
> He's not questioning whether it's encrypted. His point is, doco sends
> an email to an address, and you respond. It gives very little control,
> even if there is a compromise.
AIUI, the proposed solution would allow "anyone" to edit content, and
contribute it as a "patch". Content could inclu
> > The proposed workflow institutionalizes RTC,
> RTC?
Review Then Commit. As opposed to Commit Then Review. I think there are
other variations on the phrase floating around.
> > Perhaps we could require SMTP AUTH over SSL for the
> > moderators?
> Hmmm, I don't really see how this would help
Noel J. Bergman wrote:
don't know, maybe I'm missing something, but what do you think a
possible attack could be?
I don't consider any traffic across the Internet to be secure unless
encrypted. Why do you use SSH instead of telnet if packets are secure?
He's not questioning whether it's encrypted.
