Full Disclosure mailing list archives
RE: Public Review of OIS Security Vulnerability Reporting and ResponseGuidelines
From: "Thomas48" <thomas48 () singnet com sg>
Date: Tue, 6 Jul 2004 18:39:48 +0800
Dear all Finally there's going to be a true blue security conference in Singapore that is product and vendor neutral. The Symposium on Security for Asia Network (SyScAN "04) would be held on 16th - 17th December 2004 in Singapore. SyScan "04 would be held at the beautiful Swissotel Merchant Court Hotel, which is located a stone throw away from the financial and the pub districts, and 10 minutes away from the famous shopping belt of Orchard Road. SyScAN "04 boasts a list of expert speakers in their various fields, coming from US and Europe and the topics would be scintillating and mesmerising. SyScAN "04 would be a wonderful avenue for all security enthusiasts from all over the world, especially those from Asia, to gather and fraternise. Please do visit www.syscan.org for more information and register. Thanks! ********************************************* Organising Committee SyScAN "04 Confidentiality Notice: This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you receive this e-mail in error, please delete this message immediately. Further, you should not re-transmit, copy, store, or reveal the contents of this message to any third party. -----Original Message----- From: fred () mobach nl [mailto:fred () mobach nl] Sent: Monday, July 05, 2004 2:57 AM To: bugtraq () securityfocus com Cc: OIS; NTBUGTRAQ () LISTSERV NTBUGTRAQ COM; full-disclosure () lists netsys com Subject: Re: Public Review of OIS Security Vulnerability Reporting and ResponseGuidelines OIS wrote:
The Organization for Internet Safety (OIS) extends an invitation to the readers of the BugTraq, NTBugtraq, and Full-Disclosure mailing lists to participate in the ongoing public review of the OIS Security Vulnerability Reporting and Response Guidelines.
I have problems with the OIS guidelines as I distrust at least one member of OIS since it won't publish verifiable information on Bugtraq since some years. When I combine the policy of that company with the next statement from OIS's about.html page "Does OIS support pre-disclosure of vulnerability information to select groups? No. We believe the software author should be given a chance to create a fix before vulnerability information is made public, but that there should be no further distribution of that information until the fix is complete. This priniciple can be very difficult to adhere to in certain situations, such as dealing with the open source community where there aren't protections to keep vulnerability information secret." I am afraid that that company might take years to supply a fix or even to never supply that. A limit of at most four weeks before disclosure seems reasonable to me. If that company cannot live with that it can opt to die. Another interesting point for me is the statement about the open source community in the same paragraph. Some organizations still have problems with that community, which is reflected by adopters.html webpage of OIS. No representation of the open source community as far as I can see. But please correct me if I am wrong. -- Fred Mobach - fred () mobach nl - postmaster () mobach nl Systemhouse Mobach bv - The Netherlands - since 1976 website : http://fred.mobach.nl Q: servos ad pileum vocare ? A: servos fenestrae ad pileum rubrem vocare ! --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.708 / Virus Database: 464 - Release Date: 6/18/2004 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.708 / Virus Database: 464 - Release Date: 6/18/2004 _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
Current thread:
- Public Review of OIS Security Vulnerability Reporting and Response Guidelines OIS (Jul 02)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines dave (Jul 04)
- RE: [Dailydave] Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines Steve W. Manzuik (Jul 04)
- Re: [Dailydave] Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines Halvar Flake (Jul 05)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines Pete Herzog (Jul 05)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines rsh (Jul 06)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines Nigel Stepp (Jul 08)
- Re: Public Review of OIS Security Vulnerability Reporting and ResponseGuidelines Fred Mobach (Jul 04)
- Re: Public Review of OIS Security Vulnerability Reporting and ResponseGuidelines Randy Bush (Jul 05)
- RE: Public Review of OIS Security Vulnerability Reporting and ResponseGuidelines Thomas48 (Jul 06)
- Re: Public Review of OIS Security Vulnerability Reporting and ResponseGuidelines ET LoWNOISE (Jul 08)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines Georgi Guninski (Jul 05)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines Valdis . Kletnieks (Jul 08)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines Florian Weimer (Jul 05)
- Re: Public Review of OIS Security Vulnerability Reporting and Response Guidelines dave (Jul 04)