Slashdot Mirror
Windows 2000 & Windows NT 4 Source Code Leaks
PeterHammer writes "Neowin.net is reporting that Windows 2000 and Windows NT source code has been leaked to the internet. More on this as we hear it."
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
Now will everyone stop bitching about Windows not being open source?!
There's plenty of worthless spam on the internet already.
I've been upgraded to "bad"!
Seriously, the previous article lambasting open source for being vulnerable is nothing when compared to eyes backed with malicious intent poring over Windows source code for new exploits. So much for security through ignorance.
A feeling of having made the same mistake before: Deja Foobar
I want a ebuild!
emerge win2000
The funny thing is the fortune that appeared in the appropriate slashbox when I first saw this article.
;-)
"Never trust an operating system you don't have sources for.
-- Unknown source"
...Windows 2000 and Windows NT source code has been leaked to the internet.
The Internet, however, being a polite sort of fellow and completely undesirous of the undoubtedly horrible ramifications of having such a beastie running around loose, gently replaced the source code and gave Windows a friendly pat on the head.
I watched C-beams glitter in the dark near the Tannhauser gate.
We all know the real valuable stuff is in error.h.
So, what does it say?
I wonder how long till hackers go in and fix some of the bugs. That's the real danger to microsoft, if the bugs were fixed people wouldn't have to upgrade.
You have commented all that Microsoft code already. Holy Crap that is fast.
ReactOS have announced they have hit all upcoming milestones and consider their project "feature complete".
Breaking News:
A member of the Slashdot cult has admitted he has stolen the source code to Microsoft's Windows XP operating system. PickyH3D is the handle the low-karma hacker used when bragging of his accomplishment to the world. He has also issued a challenge to Microsoft's legal team with the statement that "there is no evidence". More on this as we hear it.
> I for one would love to peek around in this, more out of curiosity
Morbid curiosity perhaps. Considering the amount of backward compatibility in there, and the generations of tools and code frameworks used over the past decade and longer, I would expect the Windows code to be a BLOODY MESS. In fact it would probably be amusing to just grep for comments--"what does the next line do?!" or "what the h3ll were we thinking?!"
I'm a little curious as to why you seem so uncomfortable saying "Micro". Actually, scratch that. I don't want to know.
In Soviet America the banks rob you!
100 GOSUB 7000 ; * Load stuff
110 GOSUB 900 ; * Show windows logo
120 GOSUB 20000 ; * Prompt for operator login
130 GOSUB 32000 ; * Fill half of memory with DLL's
140 GOSUB 16000 ; * Time waster loop
A feeling of having made the same mistake before: Deja Foobar
Imagine if somewhere hidden in the bowels of the Windows2000 source an intrepid SCO intern finds a sliver of SCO-owned Unix code. Then all hell would break loose...
The server is currently slashdotted, but I managed to download the first few lines of the Windows 2000 codebase. Here they are:
I was expecting the General Protection Fault License.
Libertarianism is rich wolves and poor sheep playing gambler's ruin for dinner.
You must either be new to Gentoo or new to Windows. It would most definately be:
ACCEPT_KEYWORDS="~x86" emerge win2000
"History doesn't repeat itself, but it does rhyme." Mark Twain
What the hell, it's just one big .vbs file!
In Soviet America the banks rob you!
WINEHQ: Early today, a developer who wished to remain anonymous contribued an astonishing amount of source code to the WINE project. Some initial testing performed by WINE core developers revealed that WINE's compatibility with Microsoft Windows applications releasted for Windows NT and Windows 2000 had perfect compatibility, even down to some annoying and well-known bugs that have plagued certain Microsoft DLLs distributed with Microsoft's operating systems.
;)
"This will really make it possible for non-Windows users to run more applications than ever using WINE on alternate operating systems like Linux," said one develper we spoke with.
I would be the most poetically ironic event ever if it turns out that it was a MS Win security hole that allowed a hacker to enter a server and steal the code.
Doubly ironic if it was a hole that MS has known about for months and not bothered to patch.
Triply ironic if someone finds said hole, patches it, and ships patched source back to MS.
__ Someday, but not this morning, I'll finally learn to use the preview button.
AT LAST! The secret to beating Solitaire... This could perhaps be the most significant event of our times!
Don't worry... We're safe. MS can't prove what you're downloading, because no one there can open a tar.bz2!
TAR!? BZ2?! What the hell? That's not ZIP!!!!
Here's my favorite. BY FAR. Who the fuck accepted this into the kernel?
/* //length of male string //just an index variable //temporary pointer for my own pleasure // We skip all spaces and tabs //Fuck off, no fucking
[from drivers/usb/spca50x.c, a usb camera driver]
* Function compares two strings.
* Return offset in pussy where prick ends if "prick" may penetrate
* int "pussy" like prick into pussy, -1 otherwise.
*/
static inline int match(const char* prick, const char* pussy, int len2)
{
int len1 = strlen(prick);
int i;
const char* tmp;
for (i = 0; i len2)
return -1;
if (!strncmp(prick, tmp, len1))
return i + len1;
return -1;
}
To get around stupid slashdot filter:
# mportant Stuff: Please try to keep posts on topic.
# Try to reply to other people's comments instead of starting new threads.
# Read other people's messages before posting your own to avoid simply duplicating what has already been said.
# Use a clear subject that describes what your message is about.
# Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
# mportant Stuff: Please try to keep posts on topic.
# Try to reply to other people's comments instead of starting new threads.
# Read other people's messages before posting your own to avoid simply duplicating what has already been said.
# Use a clear subject that describes what your message is about.
# Offtopic, Inflammatory, Inappropriate, Illegal, or Offensive comments might be moderated. (You can read everything, even moderated posts, by adjusting your threshold on the User Preferences Page)
I prefer win3*23*29+2
Worse still - if you work on any Open Source project, and you look at Microsoft Source code. . . DO NOT COPY IT!!!
We like Linux as it is. Reliable, stable, and fast. Copying Microsoft code in would jeopardize that. Never mind the IP issues. . .
These are my friends, See how they glisten. See this one shine, how he smiles in the light.
Try this torrent
Rakshasa
This is probably old hat now, but....
Real men don't do backups, they just pack their files into windows_2000_source_code.zip and post them to their website.... with torrent links...
If its true (conspiracy theorists) that MS was behind the 50M cash investment into SCO a while back, then its possible MS is trying to provoke the playgournd wimp into picking a fight with the Big Blue bully for the sole purpose of being there first after getting his ass kicked. Its not out of the realm of possibility that the MS world domination plans include purchasing UNIX IP just to burn it in some pagan ritual.
If code is made criminal, only criminals will have the code
Now that was a very satisfying cliche re-use. I hope it was an original cliche re-use.
BTW the server seems ve-wy slow to-day. I think we were just Farked.
"Will future ages believe that such stupid bigotry ever existed!" -- Ivanhoe
"There seems to have been a slight problem with the database. Please try again by pressing the refresh button in your browser."
Refresh, you say? Oh-kay...
This is an attempt to corrupt your ability to write reliable code. It is the software equivalent of a Medusa. Once you've looked at it your mind will be agog to make blue screens. Do not look! For the love of Pete, DO NOT LOOK!!!!!
It's 5:15PM. I got home from work 2 hours ago, and had a nap. It is a beautiful day outside, and the Windows source code has been leaked.
And I have 5 Moderator points.
Today -- today, life is good.
It was a quiet nice evening couple years ago walking around Washington. Someone pointed me to an open door at the white house. 2 telephones sitting side by side. One direct to Moscow, the other direct to central nuclear command.
:-(
People were milling about in the room, I finally took the dive and made a couple of prank calls for pizza. Some other guys managed to get the US up to def con 4. I envied them because I managed to get only arrested.
It seemed real. Very real. Someone had broken into the potting shed, stuffed a key to the nuke room under a bush and escaped with it.
There was some small mention about it on the Drudge too but I couldn't find it right now. It seems the government was able to really sweep that one under the carpet. I wonder how.
There are people around with the phone number still, trust me. I envy them. I would gladly make the call to nuke France. Even though it would be a HUGE task.
So the now Brittany Spear's leaked cell number is mostly just boring and obsolete.
I find this one refreshing...
/* You will be assimilated, suckers */
if (app.exename="NETSCAPE.EXE") system.sluggify();
And this one provides for the future...
if (site.url="www.google.com") {
browser.renderer.togglebuggyrenderer();
browser.fakepopup("www.msn.com");
}
I can't say anything about this one though:
if (user.status==PISSED_OFF)
prick.annoyingpopup("Hello, I noticed you are writing a letter")
Seriously, given the denounces of delayed APIs for Navigator, I wouldn't doubt the first one... could someone with the codes please grep for netscape.exe?
IAAL.
/.! You must be just some miserable karma whore... or then you just made a major typo and forgot the obligatory "N" and ",but".
My god, this is simply not possible - man, this is
Well, I believe the latter must be the case. Be more careful on your next post, OK?
“Wait for Hurd if you want something real” –Linus
...I hear the source code to Linux gets leaked every other day!
OK, it just HAD to be said..
100% compatibility with all Windows programs.
"Don't ask us how we did it!!!"
You, my friend, win for best line I have ever read on slashdot ...
IANAL, but from what I've read on slashdot...
This is good stuff
man
No manual entry for
There's so many more computers running than 2000/XP than 9x, why bother writing any kind of worm that targets 9x?
Is that true? Can you prove it?
For years after Windows 95 came out, there were more Windows 3.1 systems than there were Windows 95 systems. Why is this?
It's probably for the same reason that there are more dead people than live people.
t'nera semordnilap
A)
1. look at the linux source
2. find a mistake
3. send a patch to the maintainer.
4. PROFIT!!
B)
1. look at the windows source
2. find a mistake
3. ???
4. write a worm
5. get caught
6. JAIL=tEH_SuXX0rZZ!!!1!! lolomgrofl
Free as in mason.
what my first thought was:
Because every idiot skr1pt k1dd13 and their lam0r grandmother can code winDOZE viriii, but only 1337 H4XX0rZ can ownzor teh LiNuX and MaC BoXxEn!!!1!!
how it should be phrased:
Successfully designing, implementing and deploying a worm/virus targetting the aforementioned "alternative" platforms Linux and/or Apple would - although being a much more complex undertaking and promising less quantifiable success (for example, infected hosts) than targetting the Microsoft Windows platform - could strengthen the Programmer's social status amongst his peers.
how it should be phrased on slashdot:
Frist psot!
Free as in mason.
Windows 1337+666 seemed to always do it for me...
Due to the source code leak, Microsoft has delayed the release of the highly anticipated Windows 2000 till the summer of 2004.
*time passes*
Due to the source code leak, Microsoft has delayed the release of the highly anticipated Windows 2000 till the fall of 2004.
*time passes*
Due to the source code leak, Microsoft has delayed the release of the highly anticipated Windows 2000 till the release of Half-life 2.
*time passes*
Duke Nukem Forever released...
[sig]www.masterslate.org[/sig]
I think you people are going a little overboard. Windows source code isn't like a virus or something.
Wait a minute....
IT WAS LIBERATED!!!!!!
The "Insert Quote Here" line is almost as predictable as inserting an actual quote.
We have identified over one million lines of our IP in Microsoft's source code. While I cannot share most of them because they are a trade secret, here are three of the most glaring examples:
#include
for( ; ; )
if(!stop) {
Many of these lines have been copied verbatim several thousand times. We do not want to, but are forced to sue Microsoft for unlicensed use of our intellectual property.
We will institute a licensing program called gplSource which will allow Windows users to obtain the legal rights to use our IP. This cost will be significantly discounted to early adopters.
Already at least three Fortune 500 companies have seen the validity of our claims and have paid these fees on a per-CPU basis to continue using Windows. While we cannot divulge their names, they do exist. Really!
Computer Science is no more about computers than astronomy is about telescopes. --E. W. Dijkstra
Coincidently, this is also one of the key reasons that there are more worms/virii released that target Windows than Mac or Linux - why target Mac or Linux when you can target Windows, with many, many times more users?
/dev/kmem.
:Portland.OR.Us.Aolirc.us 372 lamer :- Network Admins:
:Portland.OR.Us.Aolirc.us 372 lamer :- Paul
:Portland.OR.Us.Aolirc.us 372 lamer :- MrSteve
:Portland.OR.Us.Aolirc.us 372 lamer :-
:Portland.OR.Us.Aolirc.us 376 lamer :End of /MOTD command.
:lamer MODE lamer :+wx
:lamer!lamer@aolirc-1FCCF050.client.attbi.com JOIN :#ddos#
:Portland.OR.Us.Aolirc.us 332 lamer #ddos# :
:Portland.OR.Us.Aolirc.us 333 lamer #ddos# smash` 1068679664
:Portland.OR.Us.Aolirc.us 353 lamer @ #ddos# :lamer
:Portland.OR.Us.Aolirc.us 366 lamer #ddos# :End of /NAMES list.
:lamer MODE lamer :+i
/* address size */
/* 0x00417001 0 */ /* unknown */ void __entry_point__;
I have noticed some viruses for linux. One was just a script and it recommended that the indivdual chmod a+x and then run it. The other one you had to type gcc -o virus virus.c and then run the resulting binary in order to get it to work. And then there was that one where it wanted to load a module but it couldn't because modules weren't supported on that kernel, although it did try for
Then there was that one that installed an irc backdoor:
JOIN #ddos# vrfx
MODE lamer +i
MODE #ddos# +nts
23:14 < lamer HTTP server listining on poort: 999 root dir: c:\ Address http://X.X.X.X:999/
Oh, wait. that last one was a Windows thing. But those other ones. Look out. They'll do some nasty things. I mean, it takes a bit of work to get them running. But once you do. Look out. They're dangerous!
$ grep -r -i fuck *x :fucks?sMxl impse_index:fucking?sMjl come/html/webapp.cpp: // HighContrast mode is turned on. This totally fucks our style sheet as most of it will/ shell/windbgrm .c: // The user fucked uph : * !!!!!!!!!!!!!!DOING SO FUCKS THE BUILD PROCESS!!!!!!!!!!!!!!!!n trol/midi/map.c: // !!!this is fucked if a map goes to multiple physical devices
bsc/.glimpse_index:fuck?sMP
bsc/.glimpse_inde
bsc/.glimpse_index:fucked?sM`
bsc/.g
private/shell/applets/we
private/shell/shell32/copy.c:// want to fuck with.
private/shell/shell32/util.cpp:// the fucking alpha cpp compiler seems to fuck up the goddam type "LPITEMIDLIST", so to work
private/shell/shell32/util.cpp:// around the fucking peice of shit compiler we pass the last param as an void *instead of a LPITEMIDLIST
private/shell/shell32/util.h:// the fucking alpha cpp compiler seems to fuck up the goddam type "LPITEMIDLIST", so to work
private/shell/shell32/util.h:// around the fucking peice of shit compiler we pass the last param as an LPVOID instead of a LPITEMIDLIST
private/windbg64/debugger/tl/remote
private/windows/media/avi/verinfo.16/verinfo.
private/windows/shell/co
I'm submitting patches to the 2.6 kernel for the blue screen of death. I'm hoping they make it in to the next release.