mailing list archives
Re: what we REALLY learned from WMF
From: Gadi Evron <ge () linuxbox org>
Date: Fri, 06 Jan 2006 02:11:11 +0200
Susan Bradley, CPA aka Ebitz - SBS Rocks [MVP] wrote:
Don't release a beta patch ....
1. it would get patches into reverse engineering faster [hello look what
happened to the leaked patch]
Don't ask for an untested patch if you are not willing to be there in
the newsgroups, communities and listserves helping the dead bodies after
a bad patch sir.
Do you do/handle change management in your firm? Even in my small firm
I could not handle the 'any time/any day' that patches used to come out
Be careful of what you ask for sir...because if you get what you
want.... ensure your firm has the resources to test/deploy/change
management on a 24 hours a day 7 days a week schedule because exploits
can be built in less than 20 minutes.
If the security issue has been responsible disclosed, there is a process
that is needed to build a patch and test the patch. Some issues take
more than 'days' sir. And testing takes time as well, sir.
For my community I want tested patches sir, and I will argue until
doomsday on that point. Don't hurt my community with a bad patch or a
beta patch, sir.
I quite agree, I disagree on the amount of time it currently takes for
any vendor to release patches. Apparently we "Got used" to slowness,
false positives and many other ills. Maybe it's time that changed?
Full-Disclosure - We believe in it.
Hosted and sponsored by Secunia - http://secunia.com/
RE: what we REALLY learned from WMF Donald N Kenepp (Jan 06)
Re: what we REALLY learned from WMF Florian Weimer (Jan 06)
Re: what we REALLY learned from WMF Gavin Conway (Jan 06)
Re: what we REALLY learned from WMF Matt . Carpenter (Jan 06)