Frank Hecker on the Mozilla Security Bugs Policy
Thursday May 9th, 2002
"I'll add my personal opinion that we (mozilla.org staff) have not been active enough in publicizing the current mozilla.org policy on security bugs and the firstname.lastname@example.org reporting mechanism. I'll take personal responsibility for that failure; among other things, I neglected to do enough follow-up announcements after we created the security policy originally.
"I've tried to highlight the security bug policy information in the public statement referenced above, and I'll also try to make sure that the email@example.com address and related information get highlighted in appropriate pages on the mozilla.org web site."
#3 The problem is Netscape
Friday May 10th, 2002 5:02 AM
You are replying to this message
The mozilla team has a wonderful security policy, but what would count is *Netscapes* policy for the end-user product they make out of mozilla. Where these security things are really relevant is end users and mozilla is not for end users, right? So what is the use of Mozilla's wonderful policy when Netscape just ignores this? What end users need is a competent and quick reaction from Netscape, not mozilla. So why do I post this here? Because I think that Nestcapes way of handling security issues the MS way will backfire to Mozilla. Netscape has already done immense harm by releasing the early NS6 releases the way the did - I have talked to countless web developers and administrators who have turned their back to NS6 because of this. Now Netscape will make more people get pissed and switch to another browser because of the way the handle security (and other user support and distribution issues, as I have pointed out elsewhere). Its sad, because mozilla really would deserve better. (Remember the old times: <<http://home.snafu.de/tilm…zilla/mozilla-ie-card.jpg>> ? The sign says: "Netscape 72, Microsoft 18").