Article View: alt.comp.freeware
Article #510Re: {OT} Windows source code leaked to the internet
From: W
Date: Mon, 16 Feb 2004 00:29
Date: Mon, 16 Feb 2004 00:29
44 lines
3564 bytes
3564 bytes
"techie" <none@dontspamme.invalid> wrote in message news:pan.2004.02.15.17.05.40.121655@dontspamme.invalid... > On Mon, 16 Feb 2004 00:49:31 +1000, W wrote: > So you admit that Windows end-users have no way of knowing how much > Windows source code has been scrutinized? Does anyone know how many people are scrutinising the Linux source? What about the userland code? If you compare tit-for-tat in the vulnerabilities department, it is almost 1 to 1, at the moment M$ just in front with a higher number of vulnerabilities usually in stupid locations, derived by their own implementation of RFC, RFD, ISO, ANSI and what ever other standards there are. The key problem with the SDLC of Windows, there is too much of a focus to be `Industry Standard` whilst trying to be unique, and it is this uniqueness that causes the vulnerabilities. Is it the coders fault, is it the testers fault, what about the after market testers, no, with M$ it is a management problem, which is very common in all coporate sectors, know-nothing manager (or worse an manager who does know, but to dumb to think for themselves) setting unrealistic tasks and goal then scratching their heads asking `why did that fuck up?` > How many of these people get to see the source code and how many find > the bugs only by randomly probing what amounts to a black box? Or don't > we know that, either? Considering that the last NDS I read had the threat of legal action if I devulged any information about the product in question, it is a very good possiblity that those involved with the life cycle are not allowed to talk about for fear of legal action. > > > > Seek and ye shall find the answer to the question that has plagued and > > eluded the world - of course there is a NDS/A that needs to be agreed to > > prior to starting. > > So even if someone does find a security vulnerability, they're not allowed to > tell the rest of us about it? Is this an old `tale`, I am sure when I have reported certain things to CERT etc no `suit` came knocking at the door.
Technical Details
Message-ID:
<d7UXb.26$682.1798@nnrp1.ozemail.com.au>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!news1.optus.net.au!optus!snewsf0.syd.ops.aspac.uu.net!nnrp1.ozemail.com.au!53ab2750!not-for-mailReferences:
<de4e2e00.0402130836.2176c954@posting.google.com> <c0l023$184srl$1@ID-200043.news.uni-berlin.de> <c0le3r$190cjo$1@ID-151056.news.uni-berlin.de> <pan.2004.02.14.17.28.30.956489@dontspamme.invalid> <jLyXb.39831$A75.18007@bignews5.bellsouth.net> <slrnc2u6sr.bkl.mathew@alpha.spiesareus.yi.org> <xAGXb.878$FI6.23965@nnrp1.ozemail.com.au> <slrnc2uop2.ckj.mathew@alpha.spiesareus.yi.org> <6DLXb.989$FI6.27137@nnrp1.ozemail.com.au> <pan.2004.02.15.17.05.40.121655@dontspamme.invalid>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 112049,dcd95663ab063248
X-Google-Attributes: gid112049,public
X-Google-Thread: 108c83,eec38556d9f58949
X-Google-Attributes: gid108c83,public
X-Google-ArrivalTime: 2004-02-15 16:28:49 PST
Path: arc1-ca.pugleaf.net!archiver1.google.com!news2.google.com!news.maxwell.syr.edu!news1.optus.net.au!optus!snewsf0.syd.ops.aspac.uu.net!nnrp1.ozemail.com.au!53ab2750!not-for-mail
From: "W" <still_WMJ@none.com>
Newsgroups: alt.comp.freeware,aus.computers
References: <de4e2e00.0402130836.2176c954@posting.google.com> <c0l023$184srl$1@ID-200043.news.uni-berlin.de> <c0le3r$190cjo$1@ID-151056.news.uni-berlin.de> <pan.2004.02.14.17.28.30.956489@dontspamme.invalid> <jLyXb.39831$A75.18007@bignews5.bellsouth.net> <slrnc2u6sr.bkl.mathew@alpha.spiesareus.yi.org> <xAGXb.878$FI6.23965@nnrp1.ozemail.com.au> <slrnc2uop2.ckj.mathew@alpha.spiesareus.yi.org> <6DLXb.989$FI6.27137@nnrp1.ozemail.com.au> <pan.2004.02.15.17.05.40.121655@dontspamme.invalid>
Subject: Re: {OT} Windows source code leaked to the internet
Lines: 46
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <d7UXb.26$682.1798@nnrp1.ozemail.com.au>
Date: Mon, 16 Feb 2004 10:29:53 +1000
NNTP-Posting-Host: 203.102.234.121
X-Trace: nnrp1.ozemail.com.au 1076891209 203.102.234.121 (Mon, 16 Feb 2004 11:26:49 EST)
NNTP-Posting-Date: Mon, 16 Feb 2004 11:26:49 EST