Microsoft Windows Source Code Leaked

[Tim Scarfe]

http://slashdot.org/articles/04/02/1...id=109&tid=187

This hasn't been posted yet, so here you go. Some very interesting discussion going on there.

This is a pretty sensitive issue so from a DC stance; we don't want to know if you have seen or downloaded the source code.

--
Regards,
Tim Scarfe <tim@developer-x.com>
http://www.developer-x.com

[Abhi]

Hey,
If what someone posted on some other forum is correct and not bluffing, lots of grep in there, Although Im pretty sure he was having a laugh.

[Tim Scarfe]

The source code was leaked (see official MS press statement), that is not being brought into dispute.

The potential long term implications (legal, and technical) of this event are interesting.

We shall see.

Anyway not much to add on this, I've just spend the fat end of the last hour reading all the SD stuff.

--
Regards,
Tim Scarfe <tim@developer-x.com>
http://www.developer-x.com

[Tim Scarfe]

Also a very funny comment on SD about "backdoors". i.e. FBI1234 and 1234NSA accounts?!

--
Regards,
Tim Scarfe <tim@developer-x.com>
http://www.developer-x.com

[weblogic]

Is this not old news? Wasn't the source obtained about a year and a half ago by a group in Saint Petersburg (Russia)

[Tim Scarfe]

I hadn't heard of that one. As far as I know the last incident of widely distributed source was the leak of DOS 6.22 which was widely disregarded because it was so old by then.

This leak in particular is significant in its magnitude. For example the IE trident rendering engine is in there. Even the source code for solitaire and the screen savers! Unreal.

--
Regards,
Tim Scarfe <tim@developer-x.com>
http://www.developer-x.com

[weblogic]

Here is a reference to what I was talking about.

http://zdnet.com.com/2100-11-525083.html?legacy=zdnn

From what I've heard Microsoft really down played what was stolen, how much was stolen, who stole it, and how. Also, that this new release is just the "polished" spoils of that attempt.

[Brian Nickel]

This is interesting (I grabbed it from a /. comment, I'm not secretly scrounging through the source):
[code:t1ho9pudvx] if (InbvIsBootDriverInstalled()) {

InbvAcquireDisplayOwnership();

InbvResetDisplay();
InbvSolidColorFill(0,0,639,479,4); // make the screen blue
InbvSetTextColor(15);
InbvInstallDisplayStringFilter((INBV_DISPLAY_STRIN G_FILTER)NULL);
InbvEnableDisplayString(TRUE); // enable display string
InbvSetScrollRegion(0,0,639,479); // set to use entire screen
}[/code:t1ho9pudvx]
It is apparently the code to generate the blue screen of death.

<font color="brown"><font face="Courier New">.Brian</font id="Courier New">
<font size="2">Email: kerrick[at]gmx[dot]net - AIM: Brian K Nickel - Yahoo: brian_nickel - Jabber: Kerrick[at]jabber[dot]org - MSN: kerrick[at]gmx[dot]net - ICQ: 118451560</font id="size2">
What sin has not been committed in the name of efficiency?</font id="brown">

[Megaaudio630]

Ahh! The BSOD!

Anyway, I don't think its wise to post ANY of the source to this forum, even something extracted via an intermediary. Of course, the mods know best.

Funny stuff nevertheless; here come the bitmap viruses for lazy turds on non-updated win2000 builds.

-Rob
http://www.abstractia.com

[Tim Scarfe]

Yeah there was some other source regarding office posted which was something like

[code:r7wdbvqneo]
if( irritatingLittlePaperClip.turnedOn || true ) {

irritatingLittlePaperClip.annoyTheUserLots( );

}
[/code:r7wdbvqneo]

heh.

--
Regards,
Tim Scarfe <tim@developer-x.com>
http://www.developer-x.com