3 ms·

Yes, it leaked during the Win2K release cycle I believe. And you're probably thinking about the kuro5hin website, where someone claimed to have analyzed it. (ht

by ksk 10y ago

Yes, it leaked during the Win2K release cycle I believe. And you're probably thinking about the kuro5hin website, where someone claimed to have analyzed it. (http://webcache.googleusercontent.com/search?q=cache:3BlVJSk8XV4J:www.theinquirer.net/inquirer/news/1030335/leaked-windows-2000-source-code-analysed+&cd=7&hl=en&ct=clnk&gl=us http://webcache.googleusercontent.com/search?q=cache:3BlVJSk...) >One programmer wrote an article on it saying it was actually good code. "one programmer" commenting about 30+ million lines of code. Yeah. uh-huh. Anyway, you can still find the kernel's source if you care to dig around. Its the Windows Research Kernel but it's mostly unchanged from the commercial codebase. >The problem areas seem to be little hacks they had littered everywhere to keep 3rd party hardware or software from breaking. Those are mostly relegated to the compatibility shim layer. You can turn it off, in any case.

nickpsecurity 10y ago
"Yes, it leaked during the Win2K release cycle I believe. And you're probably thinking about the kuro5hin website, where someone claimed to have analyzed it. " Yeah, my inability to evaluate the skill level or character of source was main drawback of claim. I gave a little credence to it because I knew that they were ramping up QA due to image problems and potential lost sales. Steve Lipner... who did high-assurance security with legendary Paul Karger... came in to turn it around with the SDL. Massive investment in professional programmers to find quality issues across the lifecycle implies it would have fewer issues than average software. https://msdn.microsoft.com/en-us/library/ms995349.aspx https://msdn.microsoft.com/en-us/library/ms995349.aspx ""one programmer" commenting about 30+ million lines of code. Yeah. uh-huh." You can tell a lot by glancing at random samples while digging into a bit fewer. Good, well-commented code with various security checks stands out for people that spend years looking at the opposite. All such a review could say, though, was that people were putting in effort. Actual security would need thorough review. "Anyway, you can still find the kernel's source if you care to dig around. Its the Windows Research Kernel but it's mostly unchanged from the commercial codebase." Will do. Appreciate the tip.
- ksk 10y ago
  >Will do. Appreciate the tip. CDCFKW.zip not saying anything.. just sayin :P

by ksk 10y ago

nickpsecurity 10y ago

"Yes, it leaked during the Win2K release cycle I believe. And you're probably thinking about the kuro5hin website, where someone claimed to have analyzed it. " Yeah, my inability to evaluate the skill level or character of source was main drawback of claim. I gave a little credence to it because I knew that they were ramping up QA due to image problems and potential lost sales. Steve Lipner... who did high-assurance security with legendary Paul Karger... came in to turn it around with the SDL. Massive investment in professional programmers to find quality issues across the lifecycle implies it would have fewer issues than average software. https://msdn.microsoft.com/en-us/library/ms995349.aspx https://msdn.microsoft.com/en-us/library/ms995349.aspx ""one programmer" commenting about 30+ million lines of code. Yeah. uh-huh." You can tell a lot by glancing at random samples while digging into a bit fewer. Good, well-commented code with various security checks stands out for people that spend years looking at the opposite. All such a review could say, though, was that people were putting in effort. Actual security would need thorough review. "Anyway, you can still find the kernel's source if you care to dig around. Its the Windows Research Kernel but it's mostly unchanged from the commercial codebase." Will do. Appreciate the tip.

ksk 10y ago
>Will do. Appreciate the tip. CDCFKW.zip not saying anything.. just sayin :P