Slashdot Mirror


Microsoft Cracked

Lyserjic seems to have been first with the news. Some linkage: CNET. CNN. AP. MSNBC. BBC. MSNBC's story is a copy of the Wall Street Journal article which apparently broke the news - it's the most complete.What's known - the passwords were being sent to St. Petersburg, Russia. They probably had access for about three months.

712 comments

  1. Hacker = bug fixer by Orifice · · Score: 1

    This so-called "hack" was really just a frustrated MS user who finally decided to get in there and fix the bugs himself. Of course MS considers the bugs their intellectual property and wants them back.

  2. Re:Here's Windows source code by nachoman · · Score: 1

    void main() is not illegal! At least it didn't used to be. I know for a fact it works with TC++ 3.0 for does and all of microsoft's compilers. I believe that if you are usinig true C++ then you have to have some return code, but I'm not sure

  3. I saw it! They *were* hacked! by TheDarkener · · Score: 1

    It looks like the elite hackers left some evidence that they in fact gained access to MS Servers, including their main ftp servers:
    ----
    C:\> ftp
    ftp> open ftp.microsoft.com
    Connected to ftp.microsoft.com.
    UR 0wn3d!!! M1cr0s0f7 h4x0r3d by dr. d00m, m4st3r 0f d1s4st3r, & ul7t4 l4z3r!! Gr33tz t0 4ll 1n th3 7o7!!

    User (ftp.microsoft.com:(none)):
    ----

    --
    It is pitch black. You are likely to be eaten by a grue.
  4. Umm... HELLO!!! by state*less · · Score: 2

    "Defacements of Linux sites has been rising at a steady rate and now there are more defacements of Linux sites than NT sites."

    Do you think that maybe thats because there are more Linux than NT webservers and that its been rising because the amount of Linux webservers is rising(in fact has overtaken NT). I dunno just a guess.

    Time is Change.

  5. Re:How long by phillymjs · · Score: 1

    But what if they purged the e-mail and logs. and only had ones dating back three months? Those pesky purges have been known to happen, y'know.

    ~Philly

  6. /./././. by linuxgod · · Score: 1

    And explain to me how that compares to the THOUSANDS of virii, and trojans out there for win?

    It seems to me that win has more exploitable regions. Ive peered through my kernel (2.2.16), and ive found nothing that could lead to any type of security flaws. My kernel is self-built, and my system is installed with the Slackware basics, and then built by me from there with the latest, and CVS releases from evey daemon my system runs. I run as many services as my ISP, yet, my site has been running 2 years, and not one successful breakin. I get attempts every day.

    About IE/outlook compared to general Unix security also. This may apply to 2000, but 2000 is actually less secure in this manner. PERMISSIONS. EX: user running mutt/kmail downloads a wierd script. runs it. It only has effect on that user. If someone on a 2000/98 machine runs it, it effects the whole system. It will in 2000 because all programs are either executed as 'service' or 'system'. Ive been using Linux/Unix for 3 years, and M$ seince 94. I stopped using M$ 4 years ago, but I keep an eye on some of the things they are doing. I know, im pretty sure you do to.

    BTW people: OpenBSD isn't as secure as you think it is. Its not unhackable. Its only as secure as the admin makes it. Whereas if your using a M$ product, its only as secure as M$ makes it.


    Ignore the Anonymous Pissant trolls !!!

  7. Re:secret OS source code by 20000hitpoints · · Score: 1

    Thanks -- though this doesn't solve the overall problem (and I still don't know what those lower-level Win32 functions do) it's some help.

    --
    Don't post on slashdot. Get back to work.
  8. Re:The US Navy will soon be running Windows :-( by Masked+Marauder · · Score: 1

    The headline says "Navy to run Microsoft." I wish! More than likely Microsoft will run the Navy.

  9. Yep, you missed 'em by CrayDrygu · · Score: 2
    Did I miss some facts in the article...

    You sure did. I'd venture to guess you didn't even read it. Go read the MSNBC artcile where it states what "experts" think happened. (In short: QAZ).

    And while it doesn't mention a mail client, how much you wanna bet everyone at MS uses Outlook?

    --

    --

    --
    "I personal[ly] think Unix is "superior" because on LSD it tastes like Blue." -- jbarnett

    1. Re:Yep, you missed 'em by bozone · · Score: 1

      Here is how experts believe Microsoft was hacked:
      An unknown employee received e-mail carrying the dangerous software payload and inadvertently installed it. The virus-like software disguised itself as Notepad, a Windows program used for reading text messages.

      Still sounds like a C program to me...unless you know how to make a VBScript act like Notepad. You are right, MS employees probably use Outlook..then again any mail client that supports attachments could have delivered the program to a user...don't see how it's outlooks fault

      --
      "Hatred is the coward's revenge for being intimidated" ...George Bernard Shaw
  10. What goes around comes around, right? by Telepathetic+Man · · Score: 1
    At least its not just one or two companies that are getting cracked and feeling the great burning feeling of the less moral... Right /.'ers?

    -

    --
    Just because you can, does not mean you should.
  11. Linus's network is hacked by Viking+Coder · · Score: 1
    Linus's network is also hacked

    Another System's Source Code Stolen!

    By Ted Bridis and Rebecca Buckman
    The Wall Street Journal

    WASHINGTON, Oct. 27 - Microsoft Corp. is reporting that they are not their Operating System is not the only one whose source code has been stolen. While investigating the recent intrusions into the internal secured Microsoft network, the Redmond software giant has uncovered an even greater hacker risk. Hackers around the world have had copies of the source code to the Linux Operating System for weeks, possibly even months.

    "This is unbelievable! I mean, people thought that we were unsecure - but look at Linus Torvalds; people have been stealing his source code for a lot longer!" said Microsoft exec Steve Balmer. Sources close to the Swedish coder said that he has known about the security hole for months, possibly years.

    MOTIVE UNKNOWN
    The motive behind the copying of the Linux source code is not known, but industry experts speculated it could be an early phase of a "free software" case, in which hackers threaten private corporations' rights to publish horrible software at inflated prices. "These hackers must be stopped!" said Balmer, a sentiment echoed throughout the corporate offices of Microsoft. "I mean, if they can steal our customers, what are they going to steal next?"

    WELL-REGARDED SECURITY
    Computer security at Torvalds' house generally was well-regarded until this latest incident. The Linux software is used to run Internet servers around the world. This latest hacker exploit could endanger the very foundation of the Internet, said Microsoft. The hackers, whose identities are unknown, are believed to have had access to the Linux software codes for three months, possibly even longer.

    EMBARASSEMENT
    "This is an outright embarassement for Mr. Torvalds," said Balmer, "and I would not be surprised to see people flock in hoards to the new Microsoft 2000 Advance Servers, now available at your local software resellers!" Sources report that the software is available at most software stores, and even installs on several computer platforms - sometimes successfully. "Microsoft 2000 is the most secure software on the planet! OUR source code only got stollen three months ago, while Mr. Torvalds code has been available on the black market for years!" raved Balmer.

    Here is how experts believe Linus Torvalds' Linux software was hacked :
    o - He released it for free on the Internet.
    o - People downloaded it.
    -Gary Fields did not contribute to this article. Neither did Ted Bridis or Rebecca Buckman.

    --
    Education is the silver bullet.
  12. Re:Russians by xmedar · · Score: 1

    M$ had talked about making Windows Open Source, maybe this could be someone just helping them out, then we can just mirror it all ove the Net a la DeCSS and the mighty empire will burn, although sadly BillG will be minus a fiddle.

    --
    Any sufficiently advanced man is indistinguishable from God
  13. Re:No Security on a Windows Network by Juggler · · Score: 2
    In short, I agree with you. But it's not limited to Windows, even though that is currently the riskiest platform by far.

    As far as I can tell, defining and enforcing a policy for what is acceptible as email content is a very, very rare practise. I contend that it shouldn't be, no matter what OS you are running.

    Which is why I hang around on slashdot telling people to click on my signature - I wrote an open source filter which allows admins to do just this. :-)

    My program doesn't solve the problem. But it helps - it allows the admin to make his internal network immune to whole classes of attacks. That can really make a difference.
    --

  14. Re:Here's Windows source code by _Splat · · Score: 1

    You can't expect Microsoft to write correct code. Their way of fixing something like this would be to change the compiler so it compiles.

    --
    -Splat
  15. This is really getting to be too much by Brian+Knotts · · Score: 2
    You know, I was expecting some level of Microsoft apologism in the posts in this thread.

    But I expected the arguments to at least be plausible.

    What we have instead, is an argument that Microsoft's software is not at fault; the problem is faulty administration.

    This is being claimed despite the fact that Microsoft wrote the freaking software!

    If they can't admin it properly, how is it reasonable to expect anyone else to do so?

    SHEESH!

    --

  16. Re:Marvel at the possibilities!! by Armaphine · · Score: 1

    Is it really a suprise that a network made completely of NT/2000 was hacked? Well, mod me down to -1 for saying it, but yes. MSFT are the people who made the whole thing! They really should be the ones to know how it all works. Plus, correct me if I'm wrong, but not too many people actually crack into MSFT's servers. It's a task that I'm sure many of the 31337 script kiddies are green with envy over.

  17. The Big Question by rute_1 · · Score: 1

    Of course the big question is: If the Source Code is published on the Internet will Linux programmers use portions of it to enhance Linux's Security and Stability..... Steve

  18. Re:Inside job? by mad_clown · · Score: 1

    I'm inclined to agree... unfortunately, I seriously doubt that this will provide a "heads-up" of sorts for the people in charge or implementing security features in Microsoft networks or software. My gut instinct tells me that a host of lawyers will hasten to assure the public that nothing is really wrong and it was just one insecure box, etc., and that MS HQ will just try to downplay the whole event.

    A big possible downside to this, is that since a huge portion of the computer-using public uses Microsoft software, and since there's already a sort of "hacker/pirate witch hunt" going on in the media and in various world legislatures, this could only reaffirm their opinions, and help push through a string of very restrictive laws (like the one discussed here on Slashdot a few days back)... I guess we'll see...

    --------------

    --
    "Cut word lines. Cut music lines. Smash the control images. Smash the control machine." - William S. Burroughs
  19. Re:See what happens when you rely on NT by SCHecklerX · · Score: 1
    Don't fool yourself for a second -- Microsoft's biggest mistake was that it wasn't using a more secure firewall to protect it's local machines - these machines should have been INVISIBLE to the entire internet, only available to MS's intranet.

    They probably were. But after getting 'the list' one has only to do a phonesweep of M$'s phone numbers, and then access to the internal network is simply a matter of finding the RAS server.

    The big bad internet isn't the biggest problem. It's attacks from 'inside.' Dialup lines are a major vulnerability that are often overlooked.

  20. Re:An orchestration to reinforce Anti-Hack Treaty? by Stonehand · · Score: 1

    Your line about WWII frankly suggests you have no clue what you're talking about.

    The most direct provocation for the formal declaration of war by the US was the Japanese suprise attack on the naval base at Pearl Harbor -- 7-Dec-41 if memory serves, which crippled the Pacific fleet.

    That the German Unterseeboot U-20 torpedoed and sunk the US ship Lusitania as part of its campaign of unrestricted submarine warfare in 1917 is known to be correct. The US claim that it was NOT carrying war materiel and thus should not have been targetted is, if memory serves, has been disputed. For your info, reporting noted on the PBS site (Lost Liners) suggests that indeed it was NOT smuggling ammunition as the Germans claim.

    Bzzt.

    --
    Only the dead have seen the end of war.
  21. Re:Not A Good Thing by ctembreull · · Score: 3
    Maybe, maybe not.

    While I agree with you that this is going to look bad in just about any light, a few things need to be kept firmly in view.

    • We do *not* at this point know if the crackers in fact took source code. We know, according to Ballmer, that they did indeed *view* the code. But did they actually get hold of a copy? Without knowing this answer, we can't accurately predict if and how that source code will be distributed to the net.
    • Yes, it's true, Microsoft will in all likelihood attempt to spin this as being all the fault of those nasty, evil, commie Open Source people. But is it? The best defense against FUD is the truth, and finding out just who did this, and why, will go a long, long way towards blunting the flood of bullshit that's even now beginning to emit from the general direction of the Pacific Northwest.
    • What will Microsoft be able to claim as protection in the event the source *does* get out to the internet? Trade secret status? One of the most important things to come out of all that DeCSS litigation was, if I remember correctly, the statement from the judge that once a trade secret is publicized, no matter how, it's not a secret anymore. What, if anything, can MS use? Copyright violations? Won't hold water if any GNU or other public code is discovered in *their* code. Sure, they might try to invoke the DMCA or something like that, but honestly, what will they be able to prove or accomplish? Once the secret's out of the bag, it's *out* - whether or not that's a good thing.
    Yeah, it's for almost damn sure that there's going to be a very, very ugly war of ideologies, rhetoric, and politics resulting from this little stunt. But the key for anyone who opposes Microsoft and its slipshod methodologies which produce, in my not-so-humble opinion, second-rate software, is to keep the debate focused upon the facts and the truth. This exploit was the result of a well-known security issue, one that's been around for months, and one which Microsoft *should* have been able to guard against. This exploit was more than likely the result of a rotten-to-the-core policy decision that allows Outlook to execute arbitrary code with nigh-unfettered access to the operating system internals.

    Yes, this hack was probably a very, VERY unwise decision by the culprits. Yes, there will be a truly astounding storm of shit over the matter. But, if Microsoft's opponents play their cards correctly and with a bit of savvy, there can be a world of good which comes out of it, too.

    But first, maybe we should all sit back and try to figure out exactly what happened, how it happened, who caused it to happen, and most importantly, why it happened.

    If nothing else, that approach will choke off some of these tiresome, pointless accusations and counteraccusations.

    Chris Tembreull
    Web Developer, NEC Systems, Inc.

    --

    Chris Tembreull
    "My karma just ran over your dogma."
  22. Re:The US Navy will soon be running Windows :-( by xmedar · · Score: 1

    I thought Lockheed Martin only ran Skunkix..

    --
    Any sufficiently advanced man is indistinguishable from God
  23. Re:Inside job? by Tuzanor · · Score: 1

    The source code for solaris is available...

  24. Re:security by TheDarkener · · Score: 1

    I seriously doubt that MS leaves their servers at default security for their internal network....

    Of course,...well, ya never know... =p~

    --
    It is pitch black. You are likely to be eaten by a grue.
  25. Re:See what happens when you rely on NT by imcsk8 · · Score: 1

    To sniff packets in a unix box you MUST be using the root account. By the way do you think that somebody is going to run files recieved vía email using the root account??? If he does that he deserves all the calamities a computer can suffer.


    -- Ignorance, the plague is everywhere
    - guttemouth

  26. What a bunch of idiots! by talks_to_birds · · Score: 1
    "One person familiar with the case said it appeared the hackers initially gained access to Microsoft's corporate computers by using hacker software called the QAZ Trojan, which first surfaced in China in July. The QAZ software is traditionally delivered by e-mail and opens a "back door" to hackers, giving them remote control over the infected computer."

    Where have these people been? Info about QAZ has been out -- how long?

    "An unknown employee received e-mail carrying the dangerous software payload and inadvertently installed it. The viruslike software disguised itself as Notepad, a Windows program used for reading text messages."

    You mean, s/he double-clicked an unknown email attachment? Do these people think they're so protected from the real world that they don't have to use any common sense whatsoever?

    "The hackers, whose identities are unknown, are believed to have had access to the codes for three months."

    Three months? Three months! Where the fsck have these people been?

    The most vaunted, most pre-eminent, most powerful, most successful (well, by some measures..) software company on the entire f*cking planet has been cracked for three f*cking months and no body noticed?

    What a bunch of idiots!

    Lulled to sleep by dreams of their own power, and staggered to their knees by the enormous size of their own monolithic bulk...

    t_t_b
    --
    I think not; therefore I ain't®

    --
    I'm on PJ's "enemies" list! Are you?
  27. Re:Reichstag Fire by sulli · · Score: 2
    Updated:

    Reuters at Yahoo.

    --

    sulli
    RTFJ.
  28. Re:s/NT/stupidly trojan-enabled software/ by sethgecko · · Score: 1
    But Outlook and Outlook Express are capable of running attachments without the user having to view them. Like the Kak worm, for instance.

    THIS is what is really stupid.

    --
    Be ot or bot ne ot, taht is the nestquoi.
  29. Re:See what happens when you rely on NT by gfroh · · Score: 1

    Hey, you should be happy this edit box _isn't_ notepad. UK anti-virus vendor Sophos claims in their alert list today that the crack was affected with Qaz, a trojan that surfaced this August. Qaz copies NOTEPAD.EXE to NOTEPAD.COM and replaces the original notepad with its payload. No one (not even the lowliest of apps) is safe in the world of win32...

  30. Intresting thought by Ektanoor · · Score: 2

    If these guys managed to sneak at least a section of all that embedded all-integrated code then Microsoft is in deep trouble.

    Its is known for quite long that there is some "secret code" that allows such apps like Excel or Explorer to work more tightly with the core of the system. Even Microsoft, back in the middle of the 90's, recognized that their Excel got a boost in preformance due to such hacks. Now, imagine what will happen if the code gets well known. First Microsoft looses its warhorse. Second, these hacks can be exploited to take control over the system. Note: I am not stating an hypotesis but a fact that I saw with this "all-in-one" mess, two years ago. It's a pitty I didn't have that source code back then :)

  31. Re:No Security on a Windows Network by z00t · · Score: 1

    "Today, with Linux (not BSD though (thankfully!)) reaching more and more into the newbie space"

    You forget Mac OS X.

    Of course, you might expect Apple to release their product with fewer default holes and have a better support system for patching new ones once they're found than your average Linux distro.

  32. Re:Childish attacks unnecessary by anothy · · Score: 1

    sorry. better luck next time.
    i've been admining Unix and Win32 boxes for... well, a good while now, for really big companies. and for anyone with a reasonable security background, your post just doesn't hold water. for a few reasons.
    first off, the number of advisories at the sites you noted isn't any good indication of the security of the system. in fact, possibly the inverse. companies like Red Hat activly track and publicly report security issues to places like this, whereas Micro$oft doesn't, and has been known to exert legal or licensing force on folks who do.
    also, you're comparing all outstanding issues, for all versions. Linux/BSD/most unicies releases patches pretty regularly. Micro$oft? NT4 had, what 4 service packs? compare that to how often folks like Sun come out with patches, or even just the "recomended patch cluster". Micro$oft just doesn't take that kind of thing seriously. the problems remained, but they're more interested in preserving your reason for buying future product than in fixing the problem.
    next, Linux is far from the only Unix out there. whether by ignorance or intent, you've chosen to compare Win32 to the least secure Unix standardly available. do the same comparison to any of the BSDs (especially Open), or AIX, HP-UX, UnixWare, or (my personal favorite Unix) Solaris. your're not gonna turn up nearly as many holes.
    and (finally, for now) note that saying "you shouldn't use NT" doesn't translate into "use Linux instead". there are better Unicies out there (Solaris and OpenBSD for example) in terms of security, stability, and performance, and things even better than Unix (even plain-old telnet in Plan 9 requires challenge/response authentication - no passwords in the clear, ever, anywhere but your keyboard).
    and i'm not even going to comment on your statement that disabling a few options secures Win32. i'll assume you're kiding.

    --

    i speak for myself and those who like what i say.
  33. Re:See what happens when you rely on NT by praedor · · Score: 1

    Huh? What are you TALKING about? If a user on a unix box received an email virus/trojan and ran it, it would NOT offer up the entire system to an attacker. It ONLY affects that person's sh*t, not the system itself. Only an IDIOT would, AS ROOT, chmod the software so that it would be system run-able and affect the whole system.

    ANY useful unix admin would NEVER do this. The only people possibly screwed would be individual users. THEIR files would be in jeopardy, not any other file on the SYSTEM that belongs to daemons or root would be affected (or any files to which the user has write access as part of another group).

    --
    In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
  34. The funniest thing... by AtrN · · Score: 1

    Is their own hole let it happen. Ha ha ha.

  35. Re:Here's Windows source code by juju2112 · · Score: 1


    void main() is not illegal! At least it didn't used to be. I know for a fact it works with TC++ 3.0 for does and all of microsoft's compilers. I believe that if you are usinig true C++ then you have to have some return code, but I'm not sure

    He's right. Even though many compilers accept it, it's illegal according to the ANSI/ISO standards. I understand the misconception though, because ALL my teachers at college use void main(). I didn't realize the truth until i started reading Newsgroup FAQs who referenced the ANSI/ISO standards. In fact, i have BOOKS that use void main()! All the online literature i've read shows those books as incorrect, however.

    This C FAQ talks about it:
    http://home.att.net/~jackklein/ctips 01. html

  36. Re:Open Sourcing Windows... by kootch · · Score: 1

    and then you'll have your ass dragged to court.

    and they'll confiscate your computer, your work will fire you for bringing unwanted heat from Microsoft into your workplace because they'll want to conduct an audit to make sure your office has all legit serials that they paid for...

  37. OSS brats, hippies & Microsoft, oh my! by Minupla · · Score: 2

    I've always considered the majority of Slashdot readers to be brats, but this goes to show that whatever Microsoft may do to fight the open-source movement, they'll probably win. Why? Because for the most part, it's people like you who make up and support that movement, people lacking any amount of maturity and decency, and for movements to succeed, they must at least be honorable in the face of their enemy.


    First let me say I agree the message was in very bad taste. I don't think M$ will win in the long run. Why? History repeats itself. Causes that are championed by the youth of today inevitably win tommorow when the youth of today becomes the decision makers of tommorow (scary, I know).

    Historic examples: green movement, peace movement, and probably a lot of other movements I'm forgetting about.

    M$ might win the day, but I seriously doubt they'll win the war.

    ----
    Remove the rocks from my head to send email

    --
    On the whole, I find that I prefer Slashdot posts to twitter ones because I don't get limited to 140 chars before
  38. Re:Bad Day for Bill by thedude60 · · Score: 1

    Whoa....how much is RedHat selling for today...and...a year ago?

    Hmmmmm. Whose stock is worthless?

  39. So where's the source? by shutdown+-h+now · · Score: 2

    Somebody wanna put up a location to the source?

    I'd love to see Microsoft source code. We could all benefit from looking at their source. In the very least we could learn what kind of code *not* to write.

    1. Re:So where's the source? by Chris+Johnson · · Score: 2
      Um, foreign intelligence computer espionage agents don't post to Slashdot. _Good_ hackers post to slashdot. Military spies may be good _at_ hacking but they really suck rocks at 'information sharing' :P

      Wake up, this was a military action, not geek subculture. If you want to see the source you'll have to crack into MS yourself. The Russian spies are not going to share.

  40. Potentially Serious Consequences by werdna · · Score: 2

    Hackers have had access of some sort to Microsoft source codes for perhaps as long as three months. Microsoft can only say they presently have "no evidence" that codes have been changed.

    So little is necessary to create a back door, or even an exploitable "bug," how would it be possible for Microsoft ever to say that the codes are uncompromised.

    The problem is that MS operating systems are ubiquitous. If a hacker can build-in, directly or indirectly, the equivalent of Back Orifice in EVERY system, what then? Suddenly MS itself becomes the Trojan horse.

    This is the fundamental difficulty of closed source solutions -- there is no way for third parties to assure themselves of the absence of serruptitious code. Of course, such code can find itself into open source code as well, but at least there are means to independently verify the work.

    Microsoft just says, "trust me." And some of us do. But the more frequent hacker visits occur, the less it matters whether we trust Microsoft -- we have to ask ourselves, "do we also trust Microsoft to effectively defend itself (and thus us) against Microsoft's hackers?"

  41. Info also at the Washington Post by Rasvar · · Score: 2

    Info on this is also available at the Washinton Post

    1. Re:Info also at the Washington Post by billybob2001 · · Score: 1
  42. See what happens when you rely on NT by pcwhalen · · Score: 1

    for security? :]

    --
    Pay no attention to the man behind the curtain with all your metadata.
    1. Re:See what happens when you rely on NT by coolgeek · · Score: 1

      While you're at it, pull that power cable too =)

      --

      cat /dev/null >sig
    2. Re:See what happens when you rely on NT by Karn · · Score: 1

      This child process sniffs out passwords, because hey, any user account can sniff packets, not just root.

      Actually, I believe you DO have to be root to sniff packets (the interface has to be in promiscuous mode to do the sniffing.)

      --


      Why do I keep typing pythong?
    3. Re:See what happens when you rely on NT by The+Welcome+Rain · · Score: 1
      No software development team (company or not), that I have very seen, uses a better method of distrubation files than email attachments.

      Really? You have never seen an outfit that used, say, a CVS server? Never even heard of one?

      --

      --
      Some keywords for the NSA in the Lord of the Rings universe: One Ring bind find Sauron quest Nazgul freedom
    4. Re:See what happens when you rely on NT by Alternity · · Score: 2

      Those things were supposedly made more secure with Outlook patches after the I Love You problems. Now if Microsoft themselves didn't apply their own patch to their softwares and are paying the price of it I can't help but smile and shake my head at how ridiculous this is.


      "When I was a little kid my mother told me not to stare into the sun...

      --


      "If liberty means anything at all, it means the right to tell people what they do not want to hear"
    5. Re:See what happens when you rely on NT by DGregory · · Score: 1

      Well at least he backed Notepad up! I mean, what in the world would they do if they couldn't get their original Notepad back?

    6. Re:See what happens when you rely on NT by SpeakerToAnimals · · Score: 1

      Absolutely correct! Microsoft's approach to app interopability was wrong-headed from the get-go Too little attention was paid to security issues and reliability. Now see the fruits of the company's sloppy, fuzzy-headed thinking! Hackers have penetrated Microsoft itself and stolen proprietary data. How can government or corporate customers feel good about using Microsoft products when Microsoft can't even defend itself against attack? If I were a Microsoft shop, I'd want to get to Linux as soon as I could! I hope to god that whoever stole the source code publishes it in all the major forums and distribution channels. Then we'll get a good look at the true workings of the "mature and professionally developed" software nuisance that Bill Gates thinks is so wonderful. We'll also see how the file formats are structured enabling us to migrate our data OUT of Microsoft applications (like Outlook) and onto reliable platforms like Linux! - Speaker

    7. Re:See what happens when you rely on NT by jafac · · Score: 2

      actually, it's not Outlook's fault at all. It is the fault of the architect who decided what Outlook's default security settings are. By default, they're wide open. (stages.vbs proved that), but if the security settings are tweaked a bit, this kind of exploit is impossible. But then again, if they enable those settings, widespread use of this so-called "feature" is DISabled. And if widespread use of this so-called "feature" is threatened, it threatens the feature's usefulness, and hence, the feature itself may as well not exist (yay!).

      So basically, the choices are;
      1) Develop a feature which allows Outlook to run executable code - so administrators can email software updates to their employees, etc. By default, leave it wide open, so support of this feature is ubiquitous, and so that people actually USE it, and it's touted as a great reason to use Outlook instead of Eudora, etc.
      2) Develop this feature, add it to Outlook, but effectively hobble it by setting the security defaults high enough to eliminate the threat of email viruses. If anyone wants to actually USE this feature, designed to aid complicated administration tasks, they'll be required to train all endusers in how to set the security settings so that this feature can be used (has anyone here actually tried to tweak these settings in Outlook? Talk about obscurity!)
      3) Leave the feature out, and give consumers NO features that appeal in Outlook over Eudora.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    8. Re:See what happens when you rely on NT by Molesworth · · Score: 1

      Think about it... It makes it kind of hard to have thousand of developers working on a project if "there is no wire" linking the dev's machine to the source repository.

      Sneaker.net went out of fashion quite a while ago.

      --
      Yesterday I woke up sucking a lemon...
    9. Re:See what happens when you rely on NT by jafac · · Score: 2

      Outlook's preview-mode and auto-running of attached code takes the human link out of the chain.

      This stuff is enabled by default. that, along with the shell scrap crap (that hides the executable code inside what looks, to the user, as a plain text file), is an inexcusable lack of conscientious software design.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
    10. Re:See what happens when you rely on NT by PaxTech · · Score: 1

      Think about it... It's easy when you have two machines on each desk, one hooked to the companywide network and the internet for email and browsing, and a separate dev machine on the dev network.

      PaxTech

      --
      All movements for social change begin as missions, evolve into businesses, and end up as rackets.
    11. Re:See what happens when you rely on NT by Technician · · Score: 1

      The military goes further than that. The top secret stuff is in another room. You don't even carry in a floppy! There is no wire outside the room to sniff. Encryption between sites is done in another room off that room with very limited access. The encrypted link is not on the internet.

      --
      The truth shall set you free!
    12. Re:See what happens when you rely on NT by charon.de · · Score: 1



      just install another user with the same UID/GID as whomever you wanted to become

      Why the hell should someone with UID 0 do that? just type: su username
      and your done...:-) root doesn't need to type/know boring passwords to become whatever user he wants.

      Michael

    13. Re:See what happens when you rely on NT by ryusen · · Score: 1

      something intresting on that topic.. my NT server froze once... well more than once, but this time... and i couldn't get it to reboot... got fustrated and pulled the plug... plugged it back in and it was still on...

      --

      I believe sex is highly over rated... unless it involves me
    14. Re:See what happens when you rely on NT by Kazymyr · · Score: 1

      Sure you can secure a NT box. Just shutdown every damn process that has anything to do, even remotely, with networking; then, to be absolutely sure, pull the ethernet cable too.

      --
      I hadn't known there were so many idiots in the world until I started using the Internet -Stanislaw Lem
    15. Re:See what happens when you rely on NT by coolgeek · · Score: 1

      Dude, you need to go read some Bugtraq and grok how it is possible to send an Outlook user an email, and without them even reading it, execute code on their system.

      --

      cat /dev/null >sig
    16. Re:See what happens when you rely on NT by gatekeeper-eu · · Score: 1

      Not wishing to trade belittling comments I humbly suggest that an AIR GAP is the only EFFECTIVE solution

    17. Re:See what happens when you rely on NT by MarNuke · · Score: 1

      That's why you have to put in a wood box with pad locks. Incase this with 24 inch steel plate. Drop the whole thing in lead until you have a 72 inch layer. Once you have this, you want to remove it from earth. The moon might work, but humans have been there, we are about to go to mars so that's no good, and all them little martains. A safe place is the sun core, but the the data might still exist, your safest bet is lauching it into a black hole.

      --
      MarNuke
    18. Re:See what happens when you rely on NT by nconway · · Score: 1
      This child process sniffs out passwords, because hey, any user account can sniff packets, not just root.

      No, you need root privs to set the NIC to promisc mode. Or do I misunderstand you?

      It also spawns a child process, but you're probably unaware of this.

      Well, my shell kills all bg processes it spawns before logging out (it asks me first - it's zsh, BTW).

      The exact same type of crack could happen on ANY Unix machine, not properly safeguarded.

      You mean 'ANY machine running braindead, insecure software that executes remote binaries'. Yes, you can receive an email in mutt w/ a binary attachment, you can download it, make it executable, and run it. But who's stupid enough to do that? And even so, it's not exactly easy. You've got to go out of your way -- with Outlook, it practically does it behind your back.

    19. Re:See what happens when you rely on NT by DavidTC · · Score: 1
      Indeed. I think we can all agree that on a system with mere Unix-grade security, the game is all up once you've got Root.

      What an odd comment. You mean, once someone is the user designed to be able to do anything to the system, they can do anything to the system? Far out.

      Your comment really doesn't make any sense. Are you implying there are systems where having administrator/root/wheel level access doesn't let you take over the system? I think that's a bit of an oxymoron. If you have total access to the system, you can do anything, by defination.

      BTW, there are things oout there that can restrict root...LIDS, for example, which uses capablities and other stuff. But that's just adding a level in the middle. Or you can use groups and setuid binaries on vanilla unix systems, or ACLs on NT. But, yeah, once you're root, you can do anything, just like if you have an administrator account on NT.

      -David T. C.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    20. Re:See what happens when you rely on NT by Jason+Earl · · Score: 5

      It's easy to blame NT, or Inoculate IT, but the real culprit is Outlook.

      Microsoft's policy of helping users (even their own users apparently) run binaries and scripts from untrusted locations is absolutely insane. Yes, Inoculate IT should have stopped the virus (theoretically), yes, Windows NT should have more protection against attacks, but the key is that Outlook is a trojan fun house waiting to happen.

      Unfortunately, for Microsoft anyway, the fix for this type of thing goes far beyond patching some buffer exploits. They instead have to totally re-think how Outlook (and other Internet software) handle untrusted binaries (that probably includes ActiveX).

    21. Re:See what happens when you rely on NT by jedwards · · Score: 2
      Outlook isn't a fault. Outlook just makes it easier to run attachments then other mail programs, that's all.

      If a bunch of microsoft employees receive something which looks like notepad.exe in a vaguely plausible sounding message "This is the new version of notepad for Whistler, please test it" then someone is going going to run it, whether they just click the link or have to manually extract and uudecode and unzip it. The hackers only needed one gullible person...

      Any e-mail software can receive executables, any person can run the executable without checking it. That's why there is software around to check for malicious code, and it didn't work.

    22. Re:See what happens when you rely on NT by jedwards · · Score: 1
      Whether or not the design of Outlook is good, outlook was working as designed at the time.

      The AV software on the other hand wasn't. Or wasn't being used properly.

    23. Re:See what happens when you rely on NT by Anonymous Coward · · Score: 4

      Your naiveté makes me hope you never administer any network I use.

      The exact same type of crack could happen on ANY Unix machine, not properly safeguarded. Get an e-mail with a binary attachment, chmod 744 attachment, it runs, displayes a really cool screen hack or small game of some type. It also spawns a child process, but you're probably unaware of this.

      This child process sniffs out passwords, because hey, any user account can sniff packets, not just root. People log into other computers, all the while this program gets user acct & password after user acct & password. It then sends out an e-mail to a remote address, listing all these new shiny user names & passwords, what machine they were connecting to, and voila, this cracker suddenly has user accounts. Now he's free to move onto higher level attacks.

      Don't fool yourself for a second -- Microsoft's biggest mistake was that it wasn't using a more secure firewall to protect it's local machines - these machines should have been INVISIBLE to the entire internet, only available to MS's intranet.

    24. Re:See what happens when you rely on NT by log0n · · Score: 2

      "Don't fool yourself for a second -- Microsoft's biggest mistake was that it wasn't using a more secure firewall to protect it's local machines - these machines should have been INVISIBLE to the entire internet, only available to MS's intranet."

      Very good point.

      I had the fortune of visiting the Microsoft Campus last year, and while there got a chance to go to the Museum they have. All of the computers in the lobby had internet access, yet they also had access to non-museum MS machines located around the campus. I know at least a few of them were probably not intended for public "consumption" due to the contents of some of the shared folders - nothing too fancy, but probably important stuff for MS.

    25. Re:See what happens when you rely on NT by tzanger · · Score: 1

      On a Windows machine (95/98, not sure about NT/2000), you can go into promiscious mode without being root. Since you can go into promiscious mode, you can sniff. Viola.

      True, but you (or the original AC) were talking about Unix, not Windows. You can't go into promiscious mode unless you're root on Unix. And since most systems use shadow passwords, you can't get at the hashed passwords unless you're root, either. And even if you do, most recent systems use MD5 hashed passwords so you're pretty much out of luck there too.

      Mind you if you're root, I wouldn't be bothering to crack the passwords; just install another user with the same UID/GID as whomever you wanted to become. Or sniff the network. Or do just about anything, really.

    26. Re:See what happens when you rely on NT by hanwen · · Score: 3
      This child process sniffs out passwords, because hey, any user account can sniff packets, not just root

      Would you care to explain how?

      --

      Han-Wen Nienhuys -- LilyPond

    27. Re:See what happens when you rely on NT by ronanos · · Score: 1

      No matter what Anti Virus software you use it will never be up to date enough. I think if they only allowed logging in to any server by trusted IP's ie ms ip's then this may not have happened. Usernames or passwords don't matter if you don't even get a login prompt. But if they don't take timeout of the World Dominance thing to check their security, they deserve to be attacked!

      --
      "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -
    28. Re:See what happens when you rely on NT by toast0 · · Score: 1

      sniffing packets is not terribly effective if everything is encrypted

      not to mention that on my system (debian 2.3, linux 2.4) if i attempt to run tcpdump as a normal user, it says 'tcpdump: socket: Operation not permitted' (i tried both promiscious and non-promiscious modes)

    29. Re:See what happens when you rely on NT by jedwards · · Score: 2

      See what happens when you rely on InoculateIT / Innoculan AntiVirus software. It missed a common trojan for 3 months. Oops.

    30. Re:See what happens when you rely on NT by Alternity · · Score: 3

      This has nothing to do with the OS used. It's an employee who introducedd the Trojan by opening an attachment.

      Once again this prooves the weakest link in any security is the human factor.


      "When I was a little kid my mother told me not to stare into the sun...

      --


      "If liberty means anything at all, it means the right to tell people what they do not want to hear"
    31. Re:See what happens when you rely on NT by wolf2q · · Score: 1

      Did a team of MCSE set up and design the system? ;-)

      --
      Where ever you go, There you are
    32. Re:See what happens when you rely on NT by dagoalieman · · Score: 1

      OT, but what the hell...

      I remember someone had a sig on here once, something that I found (sadly) hillarious. It just seemed too true, not to be trolling. What was it?

      NT, Security, Networking. Chose two of the three. You can't have them all.

      On a side note, you notice how short MSNBC's article was? Obviously, enough text there for them to claim that they are still a news organization, but short enough to try to keep the stock for MS up. Nothing insightful there, but I still have to wonder how they will cover it in the future.

      The best thing for their PR really would be for them just to come out and say, "Yes, we got hacked, and this is how it was done. It may be very good for everyone to change their passwords now." (Credit to /., et al., for handling theirs in the same manner.)

      --
      We don't need no Net Explorer We don't need no Thought control
    33. Re:See what happens when you rely on NT by Eric+Gibson · · Score: 2

      Why was this modded to insightful? Any UNIX machine wouldn't have a mail client that automatically runs executables attached to email. On a default install for most UNIX what mail clients do you have? pine, elm, maybe mutt? In each of these files you could have to go out of your way to save the file, chmod it, the run it. Anyway, since when is Microsofts intranet not invisible to the internet?

    34. Re:See what happens when you rely on NT by jedwards · · Score: 1

      Yes AV software can lag behind the threats. But 3 months!

    35. Re:See what happens when you rely on NT by mcrbids · · Score: 3

      Gee, somebody who GETS IT!

      Take a PC, install a default copy of RH 6.2, hook it up to a static IP DSL modem. Come back in a month or two, and you'll find that you have at least 1 or 2 "volunteer" sysadmins!

      The difference between NT and Linux is that you are given the control to make Linux VERY secure. You just aren't given the low-level control needed to make NT anywhere NEAR as secure.

      It takes time, and extreme attention to detail - bit it CAN be done.

      -Ben

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    36. Re:See what happens when you rely on NT by Nightlight3 · · Score: 4
      They instead have to totally re-think how Outlook (and other Internet software) handle untrusted binaries (that probably includes ActiveX).

      It could have been in the attached MS Word .DOC file as well. And anyone who goes to ther MSDN site for various tech info, having to use IE with full ActiveX enabled to make the sites work right, is potentially infected. Or anyone using the MSDN Libraries, including MSVC Help, of recent couple years (which also don't work well without internet connection enabled).

      Their whole "vision thing" of hypertext documents which seamlessly integrate your computer (via the MSDN Libraries, including compiler help files) into the Microsoft servers, reporting (if they wish so) anything you look up, any articles you read and for how long, anything you search for, which code samples you extract, ... even without coupling with ActiveX, is a virus/trojan handcrafted for industrial espionage, all by itself.

      I wish only Bill Gates' machines and those of the other brains behind the Microsoft all-is-one (or is it one-is-all) "vision" got some of their own medicine.

      BTW, I just typed in my first message in here, and this luxuriously spacious /. edit box with its eye pleasing courier font makes Microsoft Notepad seem like an ultra-ergonomic editor from the future. (The only cure for this is to make the web designer here use this exact edit box for three days for all of her editing work; by the second day the edit box would be twice as wide and three times as tall and user could set their own non-fixed pitch fonts. By the third day she would suggest dumping it altogether and using something like Userland's Manila editor .)

    37. Re:See what happens when you rely on NT by jbarnett · · Score: 1


      1) they should keep all beta software on a secure ftp server. No place I know of (that develops software), just email all beta testers the file, at the very most, they email them a link.

      "Hey Admin Bob, why the hell is our mail server at 54.6 load and rejecting connections?"

      2) the email should of been signed by a developer or beta manager at microsoft.

      "Hrmm this email isn't sign and is coming from russia and they emailed me the file instead of the link"

      No software development team (company or not), that I have very seen, uses a better method of distrubation files than email attachments. Second %80 of the software development teams I have seen all signed messages, so you know how is really sending it.


      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    38. Re:See what happens when you rely on NT by mindstrm · · Score: 1

      Oh? That may be the case, but has *NOTHING* at all to do with unix-vs-nt. It's merely a matter of applications.

      And I'll have you know that NT does *NOT* come with such a mail client either.... outlook comes with *office*, which people willfully install and decide to use in favour of other mua's available to them.

    39. Re:See what happens when you rely on NT by bockman · · Score: 2
      Once again this prooves the weakest link in any security is the human factor.

      Not sure about that. IMO the problem was that a *stupid* computer was let to take decisions (i.e. running a program) instead of a - supposedly - *intelligent* human operator.

      The policy of dumbifying computer users to sell more software is backfiring on M$oft ( not much, but some).

      Good automation practice should rely on *sinergy* between man and computer, allowing each one to do what it does bests : computer to quicly perform repeated stupid tasks ; human to analyze data and take decisions.

      --
      Ciao

      ----

      FB

    40. Re:See what happens when you rely on NT by mindstrm · · Score: 2

      Really. I find that hard to believe.

      More likely, NT admins just generally don't think about the TCP/IP world in the same terms unix asdmins do.
      You absolutely *can* secure an NT box, to the same degree you can secure a unix box.

    41. Re:See what happens when you rely on NT by bripeace · · Score: 1

      Actually Outlook Express comes with IE which means it now comes with win2k/winme etc .. -Brian Peace

    42. Re:See what happens when you rely on NT by cyber-vandal · · Score: 2

      How many email clients on Unix have that option at all, never mind enabled by default like Active Scripting. Yes, I know admins should turn it off, but why include it at all? I can think of very few advantages of it's existence.

    43. Re:See what happens when you rely on NT by TheCarp · · Score: 2

      > True, but you (or the original AC) were talking
      > about Unix, not Windows. You can't go into
      > promiscious mode unless you're root on Unix.

      True - of course under true64 if the admin throws the interface into promiscuous mode - by default it ends up setup so that any user can then sniff the network - kind of lame. Took some digging through docs to figure out how to avoid that.
      (turned out to be simple - though I forget it now - one of those "things we needed to do once")

      > And since most systems use shadow passwords,
      > you can't get at the hashed passwords
      > unless you're root, either.

      Yup - and even then you still need to attack them. Good luck if the system uses cracklib (or equivalent). As an added bonus - the salt makes it so that its fairly CPU intensive to crack passwords in parrallel (probably doesn't apply to MD5 hashes - but they arn't as limited as the old crypt() stuff anyway)

      -Steve

      --
      "I opened my eyes, and everything went dark again"
    44. Re:See what happens when you rely on NT by motek · · Score: 2

      Everyone is guilty. Except the thief. The poor guy just had to do it, hadn't he. Can we from now on describe crime as 'crime' regardles who is the victim.
      Please...

      -M-

      --
      I would like to die like my grandfather did - sleeping. And not screaming in terror, like his passengers.
    45. Re:See what happens when you rely on NT by Technician · · Score: 1

      In the military, The Top Secret stuff is not allowed to be connected to the internet in any way. All the passwords in the world won't get you the last 20 feet to the files. There is no wire. I think Microsofts sensitive information should have had the same protection as the potential for dammage is about the same.

      --
      The truth shall set you free!
    46. Re:See what happens when you rely on NT by Lawbeefaroni · · Score: 1
      On a side note, you notice how short MSNBC's article was? Obviously, enough text there for them to claim that they are still a news organization, but short enough to try to keep the stock for MS up. Nothing insightful there, but I still have to wonder how they will cover it in the future.

      Note: MSNBC's story is a copy of the Wall Street Journal article which apparently broke the news - it's the most complete.

      Even they woulnd't botch a blantant conflict of interest like that. Always read the dateline and byline.

      --
      "When it rains, it pours." --Morton's Salt
  43. Nailed by script kiddies? by Lurker · · Score: 1

    Am I reading that wrong, or were they basically nailed by script kiddies?

    1. Re:Nailed by script kiddies? by hayden · · Score: 1

      I doubt if a script kiddie would have recognised important source code if it flew out their arse (it the Microsoft case it probably did come out their arse). Also they weren't detected for 3 months and they haven't made a big noise about it. Not typical script kiddie behaviour.

      --
      Nerd: Derogatory term typically directed at anybody with a lower Slashdot ID than you.
    2. Re:Nailed by script kiddies? by Anonymous Coward · · Score: 1

      BS. A script kiddie is someone who MUST rely on someone else's scripts because they lack the requisite knowledge to do it with out it. Using an existing tool, whether it's a trojan, a packet sniffer, a dictionary-based password cracker, or any of dozens of other tools, doesn't necessarily make you a script kiddie. Why reinvent the wheel?

    3. Re:Nailed by script kiddies? by Eagle7 · · Score: 1

      No... they were hit by a trojan, but I suspect that these cracker must be pretty good to remain undetected for 3 months, know how to find what they want and take it, etc.

      Doesn't sound like script kiddie modus oporandi.
      horrible misspelling

      --
      _sig_ is away
  44. Inside job? by hrieke · · Score: 2
    Or was it Steve Jobs? :-)
    Really, this isn't a good thing for MS in any way. If it can be proven to be an inside job (to hold off the legal issues maybe?) and is found out to be, then they're screwed.
    If it's a outside job and the crackers beat MS' secuity, now the whole world+dog knows that MS software sucks in protecting data.
    On the bright side, it's a win-win for us.

    Oh what a great day.

    --
    III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...
    1. Re:Inside job? by rumba · · Score: 1
      Some muppet ran an executable program that was sent to him/her and the program emailed some user-priviledge data _legally_ available to any program running in that user's context.


      Well, let's see, ever heard of scanning attachments for viruses and other security-compromising code? Even if the attachment is clever enough to bypass that scan, shouldn't they run a virus-check on any software that's installed? Heck, even my pointy-nosed boss running Norton can do that. If Outlook didn't have an open arms policy to attachments you wouldn't even need that. The excuse that training alone is the issue is pretty thin.

      Otherwise, try this solution: save all files to server-- instead of backing up workstations at night, reinstall Win2000 and Office daily. No more trojan!
    2. Re:Inside job? by Stonehand · · Score: 1

      Ummm... it's rather unlikely that there was JUST ONE copy of the sources copied at MSFT. For instance, every software development engineer on the teams most likely have had their own copy on one or more computers... and they use version control software, plus, most likely, backups to secure media, so they should be able to go back and check for differences between iterations.

      --
      Only the dead have seen the end of war.
    3. Re:Inside job? by AnoniMoose+Cowherd · · Score: 2
      From CNN's article: What they appear to have had access to is the source code for products in development "years and years away," the spokesman said.

      Read: not only can you not trust the next release of windoze, you won't be able to trust it for "years and years." ;o)

      --
      - AnoniMoose Cowherd
    4. Re:Inside job? by ichimunki · · Score: 2

      You are absolutely correct. However, from all indications in the press, this crack was open for three months-- which is plenty of time to quietly make changes that get into the backup sequence and into the master source tree (there can be many copies, but sooner or later source must be merged unless each MS developer is working on a completely forked piece of software). And if this crack exists, are there others? Also, this is a company well-known for easter eggs. Not that I didn't think the Excel flight simulator wasn't fun, but think about what the whole idea of easter egg means in terms of security policy. I'm not saying they can't clean their software up or that there is even a reason to believe it was corrupted (trojan code still has to compile and not cause bugs during testing in order to make it back out of the corporation). But how would we know? And do you really trust them to be as careful or as truthful about it as you'd like?

      --
      I do not have a signature
    5. Re:Inside job? by FlyingDragon · · Score: 1

      > Why is it that a *nix box getting compromised = 'Excellent, now we can patch the hole'

      I think that's the precise difference, right there. Judiging by preliminary reports, it looks like one-click execution of attachments aided (to put it lightly) this breach. That same design flaw spawned Melissa and the Love virus.

      At this point, I think most would agree that the potential damage from that "feature" is far greater than the potential convenience and time savings. Yet here we are, many months and two huge outbreaks later, and that same feature is still enabled by default.

      > but an NT machine = their security "sucks"?

      It sucks, but not simply because it's NT, or closed source, or because it has security bugs and design flaws. It sucks because they don't fix it and you can't.

      Unix used to be like that, actually. The Morris Worm was their sign to clean up their act and patch some holes. Microsoft ignored the closest Windows equivalent, Melissa. They ignored the Love virus, too. Maybe this will hit home enough to actually spur some action.

    6. Re:Inside job? by yugami · · Score: 1
      Please explain, in detail, to us how you would patch Solaris source code to fix a security hole.

      http://www.sun.com/software/solaris/source/index.h tml

    7. Re:Inside job? by RealUlli · · Score: 1
      Simple: You go to Sun and download the source.

      Now you can patch the source the same way you would patch some Open Source OS.

      Questions? :-)

      --
      Simple things should be simple, complex things should be possible.
    8. Re:Inside job? by spectro · · Score: 1
      ... I have this sneaking suspicion that M$ and the media will use this incident to talk about how bad all those "hackers" are ...

      Well, conspiracy theorists say when the government wants a law to control you more, they create a problem to justify that "solution"... and that new law to declare hacking illegal comes to my mind...

      ---

      --
      HTML is obsolete. It's time for a new, simpler and richer markup language.
    9. Re:Inside job? by Holyscapegoat · · Score: 1

      When a jetliner crashes due to pilot error, the airlines and the regulators don't throw up their hands and say 'it's just an education issue for pilots'. They intensively study the systems design that allowed the error to happen, and allowed the error to have catastrophic consqeuences.

      "Jetliner crashes" does not equal "I got r00ted". One results in hundreds of high-profile deaths, the other results in some inconvenience or perhaps a little lost money (or an idiot sysadmin loses their job).

    10. Re:Inside job? by _dave_the_one_ · · Score: 1
      OK, well let's assume for a moment that the above poster is correct and that the source code has been changed, to include a trojan or something (and yes, that does make a lot of sense). The nest thing to think of is, if you had access to the source code, what would you do with it and what changes would you make to it?

      Here's what I would do (and if they really had access for three months, here's what I think they could have done):

      1. Windows ME was only released a month or so ago. If they had access to the source before this time, what guarantee have we got that ME does not contain a trojan? Same goes for IE 5.5, etc.

      2. Critical Updates. There have been quite a few of these lately, for 98, Me and 2k, and even Office. What better way of installing a trojan on someone's computer is there than patching a trojan into one of these updates?

      3. Wouldn't you love to get hold of the source code to any version of windows? I would. What do you want to bet that the source to, say, 98 or 2k pro appears somewhere on the net soon?

      Just a few ideas... any comments?

    11. Re:Inside job? by x0n · · Score: 3

      Does anyone at all think before they post stuff like this? Just for once can we please not be subjected to the usual moronic childish chants of "microsoft sucks" and "see what happens when you don't run linux" ?

      This incident is a simple case of social engineering when you look at it -- it's nothing to do with windows, nt nor any OS security. Some muppet ran an executable program that was sent to him/her and the program emailed some user-priviledge data _legally_ available to any program running in that user's context.

      IMO the problem lies in their staff training -- don't run crap in work on a sensitive machine, especially if you've got high-level access via an extranet. Now that isn't too hard to understand, is it?


      -- Writing a Haiku
      in seventeen syllables
      is very diffic

      --

      PGP KeyId: 0x08D63965
    12. Re:Inside job? by igorot · · Score: 1

      Uhm..could it not be another MS BS. it can be a good aversion technique. wait!!.. oh no the penguin did it...

    13. Re:Inside job? by henley · · Score: 4

      Looking beyond the fan-boy name calling, there is a serious point behind this.

      Microsoft has made a massive virtue of "making hard stuff easy"; underlying a lot of the products coming out of Redmond is the core value of "Trust us to do the hard stuff for you".

      In that context, it's commerically damaging to have revealed to the world-at-large that even Microsoft can't rely on Microsoft to do the hard-stuff (security) for it.. And if Microsoft can't rely on themselves why should anyone else?

      Not, I hasten to add, that I believe that this incident will have any long-term consequences of this action. I'm waaay too cynical to believe that any good can come of this.

      --

      --
      I'd rather have a bottle in front of me than a frontal lobotomy
    14. Re:Inside job? by Ser\/o · · Score: 3

      Think about how many attempts to do this go unrewarded....in any given day. I think about how many scripts and 'sploits I see for *nix machines, and I don't see these kinds of numbers for NT boxes.

      Why is it that a *nix box getting compromised = 'Excellent, now we can patch the hole', but an NT machine = their security "sucks"?

      My personal opinion is that unix variants are more secure, stable, and so on, but NT is NOT a gaping hole into a given network, just not my 1st choice as a server.

      Before the flames abound, my personal server is a linux box, I just didn't agree with this particular statement.

      --
      -Just because you're not paranoid doesn't mean they're not out to get you.
    15. Re:Inside job? by Hard_Code · · Score: 1

      Microsoft has made a massive virtue of "making hard stuff easy"
      Well, they've made "hacking" a bit more easy. ;)

      --

      It's 10 PM. Do you know if you're un-American?
    16. Re:Inside job? by WowMan · · Score: 1

      Absoulutely! Probably with assistance by the FBI to justify cracking down on Internet regulations!

      --
      oh....my!
    17. Re:Inside job? by tyrius · · Score: 1

      It definately could have been Jobs .... Makes you think donesn't it ?

    18. Re:Inside job? by jjo · · Score: 1

      Even if it was social engineering, that does not mean that it is 'just an education issue'.

      When a jetliner crashes due to pilot error, the airlines and the regulators don't throw up their hands and say 'it's just an education issue for pilots'. They intensively study the systems design that allowed the error to happen, and allowed the error to have catastrophic consqeuences.

      'Human factors' engineering is a big deal in aerospace. It needs to be a big deal in security as well. Saying 'just educate your employees' doesn't cut it. People are fallible, and systems must be designed with that in mind.

    19. Re:Inside job? by McMuffin+Man · · Score: 2

      What the story in the WSJ didn't say which would explain whether this was social engineering or not was how the trojan was run from the e-mail. If it was in an attachment which needed to be extracted and run by concious choice of the user, then x0n is right that this is just an education issue for Microsoft employees.

      But another likely scenario is that one of the numerous design flaws in Outlook that make it possible to execute foreign code on a machine without user action was used here. In this case blame for the incident rests firmly on Microsoft's consistently careless security design of their products, and all of this "Microsoft sucks" chanting has some specific backing here.

      Which is to say that, yes, I thought before I posted this, and microsoft sucks.

    20. Re:Inside job? by Cally · · Score: 1

      Oh sure. Unix boxes never get cracked.

      --
      "None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
    21. Re:Inside job? by Ser\/o · · Score: 1

      That's not what I said....more specifically, I never mentioned source code patching. IMHO, The problem that MS had was a firewall issue.

      --
      -Just because you're not paranoid doesn't mean they're not out to get you.
    22. Re:Inside job? by ichimunki · · Score: 3

      This may be a case of social engineering, but please don't gloss over the fact that it is Microsoft themselves who have repeatedly and loudly condemned Linux and who still, at this page on their site claim the Linux security model is weak. They spend a lot of time, money, and effort to put Linux in an extremely bad light. If they can't secure their own network using their own software, then I seriously question how their user base is to be expected to do the same. This points up how incredibly difficult it is to secure their software, yet they claim it is superior to other models out there.

      Also, a quote from their spokesdroid, "We are confident that the integrity of Microsoft source code remains secure." (MSNBC article). I'm not so sure I believe them. Can they prove it? Is there any consulting firm in the world not on the Microsoft payroll who will be allowed to study their source to determine that it hasn't been trojaned by Russian subversives (or Steve Jobs or whoever cracked them)? I humbly suggest that from this day forward, there is no guarantee that any newly compiled software or patch hasn't been corrupted. While there's no need for gloating and "moronic childish chants", the fact remains that their source may be compromised and their security through obscurity model does not satisfy even the weakest security policies. This is not a problem we have with Linux or BSD-- which certainly have had holes in them, no denying it. But when you have someone telling you that you should trust them, and please pay mightily for our product, and, yes, you'll just have to trust us that it works the way we say it does (even though we can't seem to keep ourselves secure)-- oh and that Free software that you can obtain for a fraction of the cost and that you are able to review, modify, and share as you will? It sucks.

      They do not deserve any leniency whatsoever. Their model is the one that is broken. It is based on trust. They can't buy that with any amount of marketing or legal shenanigans. Trust must be earned. And right now, they get none from me.

      --
      I do not have a signature
    23. Re:Inside job? by Hooptie · · Score: 2
      Why is it that a *nix box getting compromised = 'Excellent, now we can patch the hole', but an NT machine = their security "sucks"?

      Please explain, in detail, to us how you would patch the Windows NT source code to fix a security hole.

      Hooptie

      --
      "Heavens, it appears that my weewee has been stricken with rigor mortis!" -- Stewie Griffin
    24. Re:Inside job? by joshuaos · · Score: 2

      If it's a outside job and the crackers beat MS' secuity, now the whole world+dog knows that MS software sucks in protecting data.

      If only this could be the case, but I have this sneaking suspicion that M$ and the media will use this incident to talk about how bad all those "hackers" are and attempt to totally gloss over the fact that it is simply lack of security in their OS that is the problem.

      Joshua

      --

      When in danger or in doubt, run in circles, scream and shout!

    25. Re:Inside job? by Eck · · Score: 3

      If there are so many exploits for Unixes and not NT, why is it that despite an apparent minority of servers, there are more defacements of NT sites?

      Besides, as another poster pointed out, if we hear about a vulnerability in an open source OS, whether or not it's Unix-like, we can fix it a lot more easily than with closed-source NT.

    26. Re:Inside job? by Nailer · · Score: 1

      > "see what happens when you don't run linux"
      Um, Microsofts firewalls are mostly OpenBSD based.

    27. Re:Inside job? by T-Ranger · · Score: 1

      Please explain, in detail, to us how you would patch Solaris source code to fix a security hole.

    28. Re:Inside job? by Tony-A · · Score: 1

      Two or three months undetected in a "secure" setup counts as a "gaping hole" in my book.

    29. Re:Inside job? by iserlohn · · Score: 1

      The W2K user security model is extremely weak. It's default normal (power) users permissions to allow installation of programs contributes to the problem.

      However, the main culprit is the single login problem with W2K. You don't have multiple virtual consoles and multiple X sessions as with *nix. That means the users who normally use a restricted account needs to logout and login as Administrator. It is a fucking pain the ass to do this. That's why unix has su. MIcrosoft's answer is to allow power users to install programs, which is a very bad design decision.

  45. Open source in danger by Anonymous Coward · · Score: 4

    Before everyone here gets into a frenzy of self-important "Micro$oft are lusers" posts, I think it's important to discuss just how bad it would be if they have actually had the source code for their operating systems stolen by these hackers. And not for Microsoft, no, but for people engaged in open source projects like Wine, or people building Windows compatible operating systems.

    What are Microsoft going to end up doing? They now have the perfect ammunition to claim that these projects have received help in their tasks from people who are willing to engage in criminal persuits, and that these products have improved as a direct result of this crime. Then, all they need to do is take the creators of Wine to court over this, and hey presto, there goes a project which was making Linux look good against Windows.

    Unfortunately, because of the hacker ethos about security and the fact that the ranks of open source programmers already include criminals (Randall Schwartz), judges without any real clue are quite likely to buy this.

    1. Re:Open source in danger by Chokai · · Score: 2

      It doesn't matter if the judge has no clue. You can still have a judge that has a clue and it's likely he would agree if Microsoft could prove a linkage.

      A judges' job is to interpret the law. (incase you forgot this.) These are VERY smart people and I will bet you money they are not clueless in any sense of the imagination. The judge may philosphically agree with you but it is more than likely he is tied down by arcane laws that no longer work.

      Yes if Microsoft can prove linkage between source code theft and Wine, the Linux kernel (god forbid!!) or any other piece of software they WOULD win (not could). It doesn't matter if the judge has been using Linux for years and can compile his own kernel he would have to agree with Microsoft. If he didn't he would be disbarred (fired) for not following the law and the case would bounce to another court until Microsoft got an agreeing judge.

      Any theft of intellectual property is extremely risky. Even if it's intended to help a group or embarass another group it can come back and bite you in the ass.

    2. Re:Open source in danger by Trepalium · · Score: 1
      It's not a matter of the judges "buying it" unless they are a corrupt judge. It's a matter of assumed innocence until proof otherwise can be established. Proving that somebody read something is not neccasarily all that easy.
      The problem is that copyright and patent infringement are usually civil trials, not criminal ones, and there, the presumption of innocent until proven guilty isn't true.
      --
      I used up all my sick days, so I'm calling in dead.
    3. Re:Open source in danger by cheezybob · · Score: 1
      Give me a candidate who speaks out against the war on drugs.
      (And isn't a total moron about everything else!)

      Do you mean to mock Nader, or Browne? Surely you must like at least one of them!

      Rob

    4. Re:Open source in danger by Rakarra · · Score: 1
      (In case anyone doesn't know, Randall's only crime was to get on the wrong side of Intel in Oregon, where the government basically does anything Intel wants. See here for details. Please boycott Intel and write to them to tell them you are doing so)

      Well... yes and no. Intel apparently doesn't like Randell, but the idea that that was his only crime is silly. Randall cracked Intel's internal machines while he was there, machines he had no authority to touch. Especially at big companies like Intel, that's a big no-no. He didn't ask for authority, he just broke into a box. It seemed pretty arrogant by many of those protesting against his treatment that Intel should have simply trusted Randell's 'good name' in the perl community instead of being seen as someone who might have done something really damaging. I agree that the punishment/sentance was very excessive, but don't say he did absolutely nothing wrong. The moral: make sure you're allowed to run security sweeps on certain boxes before you do so.

    5. Re:Open source in danger by jetson123 · · Score: 2
      I think that danger doesn't exist. Microsoft was negligent in protecting their source code, and that like means that it isn't protected as a trade secret or confidential information anymore.

      Let's just hope that the Microsoft source code doesn't infect open source projects with its lack of style or lack of attention to design.

    6. Re:Open source in danger by poit420 · · Score: 1

      The smartest thing Micro$haft could do, is release their code as opensource(ESR), although i hear gnu is accepting code, too...

    7. Re:Open source in danger by divec · · Score: 3
      They now have the perfect ammunition to claim that these projects have received help in theirtasks from people who are willing to engage in criminal persuits

      Would be hard to prove. I can imagine, in such a trial, the defence demoing a 1997 version of wine running Excel 95. (It was unstable, but you could get it to run which is visually important). I.e. "this project has been making an earnest attempt to do a legit clone of the windows functionality for many years now".
      open source programmers already include criminals (Randall Schwartz)

      I'm sure there are examples of closed-source programmers who are criminals, which you could list in a trial.
      (In case anyone doesn't know, Randall's only crime was to get on the wrong side of Intel in Oregon, where the government basically does anything Intel wants. See here for details. Please boycott Intel and write to them to tell them you are doing so).
      --

      perl -e 'fork||print for split//,"hahahaha"'

    8. Re:Open source in danger by fredrik70 · · Score: 1

      They can compare the sources in court. If the Wine teams only been using legal methods (of which I'm sure) then they should have nothing to worry... Don't think MS is too interested in going after wine or the different emulators. Still to small to be on the radarscreen for them

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    9. Re:Open source in danger by MartinG · · Score: 2

      > all they need to do is take the creators of
      > Wine to court over this

      Fortunately, they have to do a lot more than that. Proving that the wine project actually used or even say their source for a start.

      It what you are saying were true, wine could just as easily take MS to court now claiming that MS _must_ have stolen their code just because they might have read it.

      It's not a matter of the judges "buying it" unless they are a corrupt judge. It's a matter of assumed innocence until proof otherwise can be established. Proving that somebody read something is not neccasarily all that easy.

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    10. Re:Open source in danger by kinkie · · Score: 2

      First they have to _prove_ that there has been leakage of unlawfully-obtained code (assuming that the act of cracking a computer _is_ unlawful in Russia or wherever else the perpetrators have committed the act) into clean projects like Wine etc.
      In the end, if the worst-case scenario comes true (that is, if there has actually been IP theft), all it takes is that the developers of Wine (etc.) refuse to get in touch with the stolen code.

      I can imagine the scene: a dark alley, a Wine developer passing by and from a dark corner a hushed voice saying: "You look down. Problems compiling? I have something good for you... you know it won't hurt, in fact it will make you feel all right..." :-)

      --
      /kinkie
    11. Re:Open source in danger by Bazman · · Score: 2

      The source code for Windows is already available outside of Redmond, or at least parts of it are. MS make it available to certain researchers under non-disclosure agreements. I know people in the Comp Sci dept here that have some of it.

      So it could already be a problem, but it isn't.

      I'm just hoping the source code gets posted so that we can start fixing the bugs in it.

      Baz

    12. Re:Open source in danger by complexSys · · Score: 1
      I don't have a clue in juridic concepts, but it seems to me that because Wine started years before this breakthrough in microsoft's computers, the project itself can't be threaten (a kind of "prior art" argument ?).

      As of patches submitted afterwards, it would prove very difficult to relate them to this event ; you will definitely not find chunks of Windows code in these projects (at least because their maintainers will be very reluctant to accept large piece of said code from new contributors...).

      Even a clueless juge wouldn't accept something as vague as "didn't wine improved recently". Well, or so I hope...

    13. Re:Open source in danger by Black+Parrot · · Score: 5

      > Before everyone here gets into a frenzy of self-important "Micro$oft are lusers" posts...

      Well, I'm just grateful that no one broke in to www.redhat.com and stole the source for Linux.

      --
      Sheesh, evil *and* a jerk. -- Jade
    14. Re:Open source in danger by oreilco · · Score: 1

      It is hard to imagine any really bad consequences of someone getting hold of the source code for Windows. However, having access to the MS internal net, and access to change the code at microsoft is a different story.

    15. Re:Open source in danger by dhuff · · Score: 1
      Unfortunately, because of the hacker ethos about security and the fact that the ranks of open source programmers already include criminals (Randall Schwartz)...

      As real and serious as Randall's legal problems have been, I feel like this is a thoughtless slam against a good guy and important contributor to our community. The whole situation is just silly, although it has scary imlications as well. Please read Randall's website to get the other side of the story.

      IMO, an apology to him would be in order as well...

    16. Re:Open source in danger by Swift+Kick · · Score: 1

      Actually, the Wine team could not take MS to court. Ever heard of 'prior art'? MS has been coding their apps longer than Wine has been around (remember, Wine is what allows Windows apps to run under Linux, nothing more), therefore, the initial poster had a valid point:
      MS could 'technically' claim that projects such as Wine and other emulators may be using some of the supposedly-stolen source in order to develop their apps at a faster pace.
      Just my two cents...

      --
      "We'll need 2000 crickets, 4 cans of Easy Cheese, and the fluid from 18 glowsticks for this plan to work...." - ph0n1c
    17. Re:Open source in danger by MartinG · · Score: 1

      > Actually, the Wine team could not take MS to court.
      .. which was the point of my post. Neither could win in coust against the other without proof.

      > Ever heard of 'prior art'?

      I think you're confusing copyrights with patents.

      > MS could 'technically' claim

      Anyone can claim anything they like, but it's not muhc good unless it actually happened and you can prove it actually happened.

      --
      -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
    18. Re:Open source in danger by NMerriam · · Score: 1

      Hey Moderators -- this post is totally ontopic and needs to be rescued from the bowels of "below 1".

      ---------------------------------------------

      --
      Recursive: Adj. See Recursive.
    19. Re:Open source in danger by jafac · · Score: 2

      It's worse than that, what if they not only stole the Windows source code; what if they MODIFIED it? What if they put a back door into it? Who knows? What if Microsoft doesn't locate the back door? What if products have already shipped with back doors?

      What if the hackers find MORE exploits in their stolen source code, and instead of publishing them to NTBugTraq or 2600 (who will make them public - so everyone can know about the dangers, and take precautions, and so that Microsoft might fix them), they pass them around to terrorists or other "black-hat" hackers, and they are used nefariously?

      There is no stronger argument for Open Source software.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  46. Yahoo Coverage by Diskore · · Score: 2

    What is it Slashdot? Microsoft Cracked or Crackers Crack Microsoft? Either way, there's good coverage on Yahoo, as always. Diskore

    1. Re:Yahoo Coverage by jpatokal · · Score: 2
      Either way, there's good coverage on Yahoo, as always.

      Err... yeah. How's this for good coverage?

      A worm is a distinct type of computer virus that makes copies of itself across multiple systems. This particular virus is believed to have entered Microsoft's headquarters on the back of an inconspicuous looking document, which would also make it a so-called Trojan virus.

      I don't think I've ever seen so many concepts incorrectly defined in such a short space before:

      • All viruses (and worms) replicate
      • Worms are not viruses
      • Trojans are executables, not documents
      • Trojans are not viruses
      • Trojans are not worms
      • Trojans don't replicate
      Cheers,
      -j.
    2. Re:Yahoo Coverage by Diskore · · Score: 1

      Well, yeah, that paragraph of the Reuters story is inaccurate. Yahoo always has a good collection of stories from all major newswires/other sites, in addition to a good selection of contextual links and related stories. I wasn't referring to the Reuters story specifically.

    3. Re:Yahoo Coverage by lizrd · · Score: 2
      I don't think I've ever seen so many concepts incorrectly defined in such a short space before:

      Ok, I'm left a little confused as to how you classify these kind of things then. Let's take something like Melissa or I Love You as an example:

      • All viruses (and worms) replicate Melissa and I Love You make copies of themselves (like a virus) and send them across a network (like a worm).
      • Worms are not viruses Well I'm a little confused here. My understanding of a worm is that it's simply a virus that uses a network as its primary means of propogation. I will however concede that a virus could be more strictly defined as only including those programs which embed themselves in other binary executables.
      • Torjans are executables, not documents Well, how then do you classify VB scripts then? They are pretty much like a document, being plaintext and all. They are even more like a document when they come embedded in a Word or Excel document.
      • Torjans are not viruses This is true, but the the difference is pretty subtle. OTOH, I'm not sure that you could always say that viruses are not trojans.
      • Torjans are not worms This is true, but the the difference is pretty subtle. OTOH, I'm not sure that you could always say that worms aren't trojans.
      • Trojans don't replicate No, but worms and viruses do. A trojan is just a means of social engineering, what the trojan does after being activated by the user may well take the form of viral or wormlike activity.
      Overall I'd say that it's getting harder and harder to define the terms trojan, virus and worm. Their differences in meaning aren't all that great, especially in a time when nearly every computer was connected to a network. Now it's very possible for a cracker to draw on attributes of all three forms of malicious programs and produce something that's a little hard for computergeeks to accurately pidgeonhole, let alone expect some clueless reporter to be able to do accurately.
      _____________________
      --
      I don't want free as in beer. I just want free beer.
  47. Re:Initial breakin was via email trojan by Captain+Derivative · · Score: 1

    "It should now be completely clear that attachment-running programs such as Outlook are dangerous and should not be used by any business which has sensitive data, i.e. any business at all."

    Does anyone actually believe that a clueless user would choose not to run an e-mail attachment solely on the basis that he/she couldn't run it with only one click? Does anyone actually think they wouldn't save the exe/com/vbs/whatever to the hard disk and then run it?

    Automatically running scripts embedded in the HTML of an e-mail message, yes, Outlook is responsible for that. But allowing the user to run or open an attached file, no, the user is responsible for that.

    Heck, I suppose you could call bash an "attachment-running program" too, but I'd hardly blame it because a clueless user ran an executable that some anonymous person e-mailed him.


    --

    --

    --
    The real Captain Derivative has a Slashdot ID.

  48. A sign of good things to come by ceclay · · Score: 1

    This is what happens when you have people as smart as the Russians living in a country that is so completely F-up. Someone needs to get their butts over there and start paying these people Western salaries so that they help make the world a better place instead of doing this kind of crap and scaring the hell out of everyone (although I think it's healthy to have the system shaken up). I think this is minor... I think there is some major stuff going on over there that we have no *idea* about because we are not sad, desperate people and can not think as sad, desperate people do. I think out of their desperation they will bring us to our knees in one way or another. Heed my warning and just watch in the next 3 years. I am positive something is going to happen but I can't tell you what.

    And if you want to see some cool pics from over there you can check out my work

  49. Re:No Security on a Windows Network by Radical+Rad · · Score: 1

    There was an article recently which also talked about tunneling through DNS. There was an href to download the software as well. Tunnelling via DNS would be instantaneous. No need to wait on a mail forwarder.

  50. source code by bswick · · Score: 1
  51. Interesting... by _Splat · · Score: 1

    The Win2k source would make a good /. comment. It'd probably get modded down though...

    --
    -Splat
  52. After all this time it had to happen to them... by Jodienda · · Score: 1
    I believe this is a good thing. FINALLY Microsoft is paying for what we have been paying in their faulty bugs and crappy code. Maybe now they will serve out propoer software

    ------------------------------------------------ -------

    --

    ------------------------------------------------

  53. Re:Sealand by jafac · · Score: 2

    what do they need laser guidance for?

    --

    These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  54. Re:Childish attacks unnecessary by jbarnett · · Score: 1

    The butler did it.

    I think you are correct, he used a small PDA to transfer and upload a trojan to a developers workstation, when the Sr. Developer was busy with he accidently got hot coffee poured on his cotch.


    --

    "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
  55. Re:I 0wn j00 by bensej · · Score: 1

    oh so you are the kid who sets the password on display computers in the store and thinks you are all cool.

  56. Re:Banks don't use Microsoft by juliao · · Score: 1
    Well, actually some do.
    Not for the "core system" but for many of the surrouding systems, most of them can perform financial transactions or access confidential information.

    As for other operating systems, I've seen nearly everything being used on banking servers, from OS/390 to HPUX to Solaris to AIX and NT.

  57. Re:Funny? Learn to moderate! by Jonathan+C.+Patschke · · Score: 1
    I think that, given the damages done, a script designed to read ~/.cvspass, log onto your CVS server, mirror all the projects to a gzipped (then uuencoded) tarball, and email them to an address in Russia would probably have the same effect. Those are all potentially damaging (to a company's business model, anyway) actions that don't require root access. Here's another one: imagine a "loader" script (like the sort that runs Mathematica, PowerView, or any other Unix app that requries significant environmental setup) that, before running its "intended application", modifies your .profile by appending the following five lines:

    alias vi='/bin/rm -f'
    alias cp='/bin/mv -f'
    alias gcc='echo cc1: Internal compiler error (caught signal 11); /bin/rm -f'
    alias pine='/bin/rm -rf ~ ; /usr/bin/pine'
    touch ~/\*

    Your average Linux user (runs /bin/bash for a shell, uses PINE for email) would probably be convinced that his computer hates him the next time he logged on. You can be damaging as non-root--you just have to be creative. Not wicked enough for you? Just remember that those actions could all take place from an automagically-generated Makefile (ie: one generated by GNU autoconf/automake) for a poorly-documented component in the "experiemental" branch of your favorite huge software suite (Gnome, KDE, PHP, anything sufficiently large). Who actually reads those things end-to-end before running "make all"? What we have here is a stupid-simple case of social engineering. While it's more difficult to properly deploy a trojan on a Unix/Linux box, it's not impossible.
    --
    Pining for the days when The Glorious MEEPT!!! graced SlapDash with his wisdom.
  58. Re:The "Truth" about who Microsoft really is by jafac · · Score: 2

    I like your .sig.

    --

    These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  59. The US Navy will soon be running Windows :-( by flossie · · Score: 1
    Lockheed Martin are intending to run MS Windows (or should that be portholes?) on aircraft carriers. Now if this isn't scary...


    -- flossie
    http telnet

    1. Re:The US Navy will soon be running Windows :-( by SpeakerToAnimals · · Score: 1

      What I don't understand is why the Navy allowed this to happen. The Navy ousted Windows NT from shipboard use because upgrades were too slow in appearing. Now they're letting the fox back in the henhouse! Believe me, there's going to be hell to pay when a United States aircraft carrier getes nuked because their information infrastructure goes into Blue Screen Of Death mode. No EULA will protect Microsoft from the ensueing PR debacle. - Speaker

    2. Re:The US Navy will soon be running Windows :-( by flossie · · Score: 1
      Or is that "Russian crackers to run Navy" now?


      -- flossie
      http telnet

  60. Haven't even gotten to SUBTLE Win-security holes.. by dpilot · · Score: 3

    .. because there have been so many blatant ones. How can anyone say that there isn't a Win32 equivalent of buffer overflows, or string format errors? One of those things they did somewhere down the line for performance was to yank some of the API parameter checking.

    But so far, crackers haven't had to look for holes or real problems in the code, because *THE PUBLISHED API, ITSELF CAUSES HOLES*. Windows is still back at the "Morris Worm" days of security, if even that far along. How long ago was that?

    --
    The living have better things to do than to continue hating the dead.
  61. Re:Maybe this is what sunk the Kursk by Kidbro · · Score: 2

    You jump to conclusions pretty quickly. You saw someone who wrote a post that offended you, and thus you assume that this person, and most other frequenting this place to be "brats... lacking any amount of maturity and decency", ending your display by declaring death penalty to the person not sharing your taste of humour.

    I must admit that I wonder who is at error here. The post you're replying to is in no way an indication of this person's maturity or decency, nor does it reflect his affiliation with the Open Source movement.

    Even so, as have already been stated in another post (redundant here I come:), people make jokes about anything, all the time! This includes war, death, fatal accidents, betrayal heart aches and slapping eachother in the face with dead fish :)
    NO topic is too touchy to joke about. Some people may on some occasions be offended by certain jokes (obviously), but in that case I'd make a bet that it's usually the people offended that's the problem, and not the joke.

  62. Re:Simply Bad System Administration by sethgecko · · Score: 1
    Wrong. Any OS that relies on the registry, a big database, to keep the machine running is a poor design. Are there any security controls to keep unauthorized access from happening to the registry? Can you lock down individual hives or even the whole thing with specific access? chmod 755 registry just doesn't exist on NT.

    About the only control you have over it is to use policy editor to prevent people from installing programs--but this is not on by default! Anyone with access to the system has the ability to install programs which change the registry. And we all know that if the registry gets changed, it has the potential to fsck the system.

    And of course there's the fact that databases tend to get corrupted. When was the last time you saw a flat text file in Unix keep the system from booting because something got changed. Now when was the last time you saw the registry keep win95/98/nt/00 from booting. It was 2 days ago for me.

    --
    Be ot or bot ne ot, taht is the nestquoi.
  63. We need to turn the tables... by dpilot · · Score: 2

    and outline that this happened precisely because Microsoft does not truly participate in 'white hat cracking' efforts. They finally have some levels of acknowledgment of Bugtraq, but they haven't fully embraced it. (let alone extend or extinguish, but perhaps that's the legal focus yet to come.)

    That is to their detriment, and what they have refused to learn from the white-hat community has contributed to this break-in.

    That's the story we need to put forward, now!

    --
    The living have better things to do than to continue hating the dead.
  64. Re:News Flash from Russia! by ncaustin · · Score: 1

    New OutLook Express

    THIS NEW AMAZING SOFTWARE TOOL HELPS
    YOU FIND OUT ALMOST ANYTHING ABOUT ANYONE -

    CLICK ON URL BELOW TO VISIT OUR WEBSITE

    http://www.microsoft.com

    ************************************************
    Find out almost EVERYTHING you ever wanted
    to know about:

    Your passwords
    Your source code
    Your enemies

    Now only $89 (provided you have already paid
    for the all the updates since 1985)

  65. Re:Open Sourcing Windows... by Zan+Thrax · · Score: 1

    You do like at a sporting event: 5 large buddies willing to array themselves in a properly-ordered line.

    --

    Intolerant people should be shot.
  66. Only ROGUE companies, eh.... by Pig+Hogger · · Score: 3
    Other possible motives include economic espionage, though experts said only a rogue company might knowingly buy stolen software, using it either to improve its own products or make those products more compatible with Microsoft's best-selling operating systems.
    Well, the article said it all: only BAD companies would want to make products MORE COMPATIBLE with Windoze...

    --
    Americans are bred for stupidity.

    1. Re:Only ROGUE companies, eh.... by Chris+Johnson · · Score: 2
      The article is being very stupid.

      Military entities would grab this sort of thing in a heartbeat, a nanosecond. There's no way this was some curious geek or 'rogue Russian company' trying to be more compatible with windows! That's utterly absurd.

      This was a military exploit. Everything from military IT to battleships runs off Windows. In addition to that, lots of other countries' militaries run off Windows as well. We will not be seeing script kiddies putting up funny defaced web pages.

      The purpose of this espionage is this: when the missles come over, the target country's military IT will be DOWN.

      I simply hope my country (the US) isn't actually the target that somebody has in mind. Just about any country would be as vulnerable, this isn't about the US only. It's not strictly military IT either- consider a war with the shipping and industry of the target country crippled through IT attacks.

      I've felt for a long time that people should be nervous of Microsoft waking up and realising their control of IT was a military weapon. It seems I was wrong- they never smartened up enough to understand this. Somebody in Russia, however, did- and struck first, gaining access to the proprietary information that would reveal every point of weakness for later attack. Whether Microsoft figures out it possesses the capacity for denial of IT services as a military weapon, at this point, is meaningless. It's too late as they no longer control the information- they lost the first-strike capability.

      It might be a good idea for the US military to seize control of the very same code so at least they can have equal capacity to attack, or to know what will be attacked and how. If MS tries to resist that it would be a matter of, "No- you can pay money to run our products, and the Russians have total information on all their weaknesses, but YOU have to trust us that your IT is not compromised. Trust us, we're Very Smart!"

      Frankly, the political applications of this are staggering.

  67. Re:security through obscurity by _Splat · · Score: 1

    Ahh yes, but why compile the absolutely huge source that will definitely only compile on a computer with Visual Studio and a gig of RAM when you could download an iso somewhere?

    --
    -Splat
  68. Re:Reichstag Fire by praedor · · Score: 1

    Oh sad child. Trojan smojan. This TYPE of exploit would NOT work on unix. Period. A user can run a binary, even a trojan, but all it will do is affect THEIR PERSONAL stuff. It will not do anything to the system. It will not do anything but, at worst, delete their own personal files. The other users and the system itself are quite safe from harm.

    Ergo, it IS NT's, W2000's, W2000ME's, and M$'s fault (for making a crappy oses) for allowing a mere user to crap all over the system, all over other users on the system, all over the network.

    --
    In Bushworld, they struggle to keep church and state separate in Iraq as they increasingly merge the two in America.
  69. Importance of Windows Source Code by jlbennett2 · · Score: 1

    Great quote from cnet "If you stole the Windows source, "it would be like having blueprints to a jet fighter if you are Ecuador," said Keith Blackwell, CEO of Bristol Technology Inc., a software developer which has the rights to some of the Windows source code." But what if Ecudor gave it to Belgium, and Belgium gave it to Iran, and Iran gave to Oracle, and Oracle gave it to Sun, and Sun gave it to North Korea, and North Korea gave it to a really bright script kiddie in Michigan, and that little punk put it out on gnutella, and newsgroups, and ICQ, and AIMster, and FTP.....

    --
    Randomly clicking into the moebiac abyss...
  70. Conspiracy theories and Urban Legend by wen · · Score: 2

    Now that news of a penetration at microsoft has been reported, whether or not any facts emerge, there will always be conspiracy theories and urban legends of people who hacked MS or own the code.

    I love it.

    Unfortunately, even if investigators catch the crackers "red handed" with the MS password files and Windows source code, there is no way anyone can be absolutely sure that the code has not been distributed.

    Conspiracy theories and legends of rogue cracker terrorists, foreign power "Echelon" projects, and talented grade-schoolers will emerge.

    As other readers have pointed out, this is a perfect way for MS to attack all projects aimed at MS compatibility. They will always be able to point at how it is impossible for others to get their programs to work with Windows without having access to the source code. Wow.... all this is a incredible conspiracy on MS's part!

    Don't cloud the issues with the facts.

    Everyone is out to get YOU. Have a nice day.

  71. Re:Reichstag Fire by alprazolam · · Score: 1

    ummm why wouldn't they? if its, in there business interests they fucking better imo! companies shouldn't give a shit about anything except the bottom line, and anything they can do to increase it they should.

  72. What I want to know is... by Tank+Abbott · · Score: 2

    will I get sued for posting a link to the Windows source code? And how the hell am I going to get it to fit on a T-shirt??

    --
    I used to have a sig, but I traded it in for a glock!
    1. Re:What I want to know is... by criticalrealist · · Score: 1
      It is possible that you'd be sued. In fact, if this turns out to be half the brouhaha I think it will be, then the FBI and MS are going to come down hard on anyone they can get their mitts on.

      Not only could you get sued, you could potentially go to jail. Aiding and abetting the theft of intellectual property.

      Some advice. Play it safe. Don't post links. Don't even ask for links to be posted.

      --
      I am not a lawyer.
  73. Effect on customer trust by lgraba · · Score: 1

    It will be interesting to see the effect that this has on customer trust, both on MS's stance on using Outlook securely, and on customers trust that MS's code base has not been hacked.

    Regarding Outlook, MS's stance has been that Outlook itself is not a security risk, its just that users must be careful about what they execute. Now that they themselves have fallen victim to Outlook's vulnerabilties, customers must take this threat more seriously. The same type of exploit could result in your company's intellectual property being stolen, or in your law firm's strategy for a trial being known ahead of time, or in your government's secrets being stolen. A rogue nation could use such an exploit to infect millions of computers, and then to disable them all at once; this would be a huge economic blow!

    If there is a possiblity that MS's code base has been hacked, can it be trusted? Will it be used at the US CIA, FBI or Department of Defense if there is any doubt? Might there be a danger that hacked MS code will send sensitive information to people that should not see it, or send passwords so that such information can be more easily obtained?

    I believe that this incident will be a real eye-opener about the damage that is possible with such an exploit. Any one who denies it is either ignorant, has their head in the sand, or will stand to lose profit if people realize the risk.

  74. Cool Windows features? by rumba · · Score: 1

    Then he'll discover that his mouse lacks the button to use them :(

  75. Re:s/NT/stupidly trojan-enabled software/ by mindstrm · · Score: 2

    Sorry? If explorer is set to show hidden extensions, it still hides .vbs?
    I think not.. and I just tried it to confirm this.

    And outlook is not part of windows... it's part of office.

    And the icon for .vbs is different than for .txt, so those 'power users' sure aren't.

  76. Re:Childish attacks unnecessary by coolgeek · · Score: 1
    now there are more defacements of Linux sites than NT sites

    I like to checkout the attrition.org stats once in a while too. Swimming around the link you provided, there was a period from early August - mid September where Linux cracks outnumbered NT, (reference) but IIRC, this is when the WU-FTPD exploits were publicized. Is this not to be expected? I mean, so the script kiddies saw the bug on bugtraq, reviewed their nmap logs for Linux hosts and then went to town. Not too impressive. What is impressive is the sheer number and variety of ways the white hats keep discovering to get M$ internet software to execute code without user intervention or knowledge.

    Also, a look at the pie chart shows NT with a 57% share of all defacements. I am not sure how you draw the conclusion that there are more Linux defacements than NT. Care to fill in the blanks for me?

    --

    cat /dev/null >sig
  77. That's not what I said. by mindstrm · · Score: 2

    I said 'outlook' does not come with windows.

    Outlook Express does come with windows, but they are *not at all* the same piece of code. Outlook Express is *not* simply a 'light' version of outlook.. it is mostly a completely different mail package.

    All these 'outlook' worms *ONLY* work in OUTLOOK, not in outlook express. Everyone just assumes that when you say outlook, you mean 'outlook express'.

  78. Does anyone have a mirror yet? by Distan · · Score: 1

    I wonder when the first mirrors of the source code will start popping up? I know I'll make sure to make a private copy ASAP.

  79. Re:/. edit box (Was: See what happens when you...) by Jason+Earl · · Score: 2

    Or if you are truly sick, you can simply use Emacs+Gnus to read Slashdot. Some crazy hacker has actually added a Slashdot backend to Gnus so that you can read Slashdot as if it were just another news group.

    That includes Gnus incredibly powerful scoring system (so your problems with slashdot moderation disappear). If you want you can just read the posts from known trolls.

  80. Re:Banks don't use Microsoft by gotw · · Score: 1

    I don't know what the set up is, but they've got little spinning natwest logos and colour terminals and everything (and adverts for account x). I don't know the technical details - but I know an NT bluescreen when I see one

  81. Mirror early, mirror often... by Ryu2 · · Score: 1

    All I'm saying is that posting Windows and Office sources would make the whole DeCSS brouhaha look like a trivial affair in comparison.

    --
    There's 10 types of people in this world, those who understand binary and those who don't.
  82. Re:Reichstag Fire by GooseKirk · · Score: 1

    It isn't so much that they would FAKE an intrusion. Why would they need to fake an intrusion when there must be crackers banging on their sites 24 hours a day?

    More likely, once a particularly skilled group of crackers had already gained access, they'd simply let them continue on their merry way for three months and then announce, to everyone's horror, that these vile criminals have been plundering their IP, and use the case as evidence to support cracking the whip.

    Does it make sense? Maybe, maybe not.

    I'll tell you one thing, though -- it's absolutely true that admitting a security breach like this does seem completely out of character for MS. It's just downright eerie, actually. They clearly stand to gain from this in one way or another, or else you'd be seeing more typical spin coming out of Redmond.

  83. Re:Childish attacks unnecessary by Anonymous Coward · · Score: 1

    It's local. Because the user had to execute the binary like they would a regular binary.

    Thanks for playing.

  84. Grow up a bit please... by ozric99 · · Score: 1
    The fact that M$ is being so forthright about this--in direct contradiction to the way they typically stonewall against any less-than-flattering news--points to an entirely different motivation than just being honest.

    When Slashdot got hacked a few weeks ago they got praised for admitting it straight away. Now that MS have done the same thing you're flaming them? Jesus Christ grow up a bit. Damned if they do and damned if they don't.

    I'm no Mickeysoft fan by any means but this childish "nerr nerr, mine's better than yours" attitude is getting to be all that slashdot carries now. It seems that the old /. contributers have moved on, as the level of comment here used to be a little more intelligent than that.

    This reminds me of the old PC Vs Amiga 'war' back in the early ninetys. I cringed then and I'm cringing now.

    ozric.net

  85. No viruses on macs by Gorimek · · Score: 1

    Seriously, though... one of the more serious reasons that viruses/trojans spread more easily on Win32/Mac is "user imbecility/gullibility".

    Actually, there are hardly any viruses at all that hit the mac.

    Not to brag about the mac so much as showing that the argument doesn't hold up.

  86. Re:Reichstag Fire by sulli · · Score: 2
    They have acknowledged that Windows source code was taken:

    http://www.nytimes.com/aponline/technology/27MICRO SOFT.html

    The Reichstag Fire analogy is relevant in my view.

    --

    sulli
    RTFJ.
  87. Re:Childish attacks unnecessary by Adam+X · · Score: 1

    I agree with you for the most part, except for *your* own childish ignorance.

    Yes, there are alot more security alerts for Linux (and other Unix variants) than for NT. Be realistic though, do you honestly think that this is because Linux is less secure? Could the fact that since Linux is openly developed and anyone can see ALL of the source mean that security related bugs are spotted more often? Yes, most Linux disto's default installs suck (Redhat probably being the worst) but don't use the "There are more security alerts for Linux" excuse.

    I would venture to say that if NT were developed the same way Linux is, the source being available to anyone, that NO one would be using NT. At least not until the numerous bugs in it were fixed (What was it in Win2k, 60,000+ ?). Personally, I see binary software distrobution as a way to conceal bad programming practices, hide cheap tricks, and load down a program with privacy violating backdoors. I know that last one may seem far fetched to some of you but do you recall the story on /. several months ago about the NSA being provided backdoors into Windows cryto system? It probably happens more often than you think.


    This post is Copyright 2000 AdamX

  88. Re:Here's Windows source code by mr3038 · · Score: 1

    I'm afraid this is not the real source. Clearly windows source wouldn't use code blocks but goto statements.
    _________________________

    --
    _________________________
    Spelling and grammar mistakes left as an exercise for the reader.
  89. Re:Redhat Cracked by Tony-A · · Score: 1

    LOL!
    There is even a Chinese translation.
    RedFlag Linux 1.1 Server installation manual looks a lot like RedHat Linux 6.2 installation (except the text is in Chinese).

  90. Why Bill G paid them to do it (Conspiracy 101) by WillSeattle · · Score: 2

    OK, now that you've all had your fun at the expense of MSFT, it's time to tell about what really happened. I mean, it didn't even get the banner headline in Seattle, it was so lame. We were all paying attention to I-695 being overturned and how Eyman is a dweeb.

    Picture this - a dark, shadowy lair on the shores of Lake Washington, in a futuristic (circa 1990s) mansion that has a trout stream meandering throughit and ads for Froot Loops appearing on every wall. Bill G, Dark Overlord, sits in his space age chair, rocking back and forth, as his minions sit uncomfortably, waiting to hear his latest dark plan for world domination.

    "Profits!" he screams suddenly. "Noone is buying my Windows 2000 TM R Patent Pending!" he shouts to the cowering lackeys, many recently hired from failed dot-coms that litter the wasteland of King County. They jump in their chairs, and settle back down nervously, awaiting their orders.

    "You must crack our servers, in a way that will bring disrepute upon those who oppose us - make it appear to be Open Source Hackers, Russians would be best; everyone knows the Russsians are still mad at us over the cold war. Release all the code to our failed OS - they will assume it was functional. And then - you must go into hiding in Aruba."

    They leave, shuddering at the import of his task, knowing that their lives and those of much of the rest of the world shall never be the same after this.

    --
    --- Will in Seattle - What are you doing to fight the War?
  91. Re:You can do this in Windows too. by drewish_princess · · Score: 1

    That's always been an NT/2000 thing, doesn't work in win 95 not sure about 98 or ME though.

  92. Not so mysterious by NuclearArchaeologist · · Score: 1
    whois NETSCAPE.COM.SHOULD.SHAKE.OFF.ITS.CHAINS.AND.FUCKA OL.ORG

    Was refered by url: www.gandi.net who will sell you a domain name for the very reasonable rate of 12 Peso^H^H^H^H Euros/month.

  93. Prove it with proof by criticalrealist · · Score: 1
    Nope. Not anymore at least. There's no telling that if there was a hack of ftp.microsoft.com that the attack was by the same Russian hackers, anyway.

    My question is, why didn't they ace the filesystems on everything they had access to? Do they still have access? How did Microsoft just suddenly say, boom, no more hackers? Okay, maybe they just unplugged the code server....for now.

    --
    I am not a lawyer.
  94. Re: Read the (full) Wall Street Journal Article by ae · · Score: 1

    cypherpunks/cypherpunks

    --
    Blog Ho
  95. Re:Simply Bad System Administration by pmc · · Score: 2
    Are there any security controls to keep unauthorized access from happening to the registry? Can you lock down individual hives or even the whole thing with specific access?

    Yes, you can lock down any key in the registry.

  96. Re:Russians by Fist+Prost · · Score: 2

    What kills me is the way C|Net blackened WINE developers after all the "Deplorable Acts of Corporate..." bleating from Ballmer, and the obligatory reference to Linux. Safe to say that while there are probably hundreds of thousands of people who would love their copy of Whistler source, anyone doing any serious developement of a project involving, say, reimplimenting the Microsoft API wouldn't want to be in the same building as a stolen copy of code, let alone look at it. Especially after the whole thing with Kerberos.

    Wouldn't it just suck to be a WINE developer and wake up one morning with a copy of pilfered source in your inbox, and the FBI knocking to ask questions because they tracked it down from the sender's Russian address?

    Fist Prost

    "We're talking about a planet of helpdesks."

    --

    Fist Prost

    "We're talking about a planet of helpdesks."
    -Jaron Lanier
  97. Re:s/NT/stupidly trojan-enabled software/ by jafac · · Score: 2

    um not so simple. Windows Shell Scrap allows an author to "hide" executable code in a file that looks like a text file -

    For instance, stages virus was actually Stages.txt.vbs. In Outlook, it looks like Stages.txt. If you save it, in explorer, it looks like Stages.txt (even if you told explorer to show all extensions - this is a hidden exception, even Windows Power Users are fooled by this, ironically, your only saving grace is erp! DOS!).

    So you see this innocent looking .txt file, you know better than to view .doc files, because you know they have Macros that can be viral. But you open this .txt file, in Notepad, no less, and it executes. You see a little system activity for a few moments, and nothing else, you're infected, and you've just emailed 150 of your closest colleagues the same garbage.

    No other mail client will hide the .vbs extension.

    Now, you CAN tell Outlook to warn you when it runs executable content from an untrusted source, but the problem is, it SHARES these security settings with Explorer, so if you do this to secure Outlook, you hobble Explorer, which will no longer run javascript from untrusted sources, which amount to like 90% of the websites you're likely to visit.

    This is complete horseshit, and there's no excuse for a feature like this.

    --

    These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  98. You've got it all wrong, comrad by NuclearArchaeologist · · Score: 1

    The real secret is that the source code is in INTERCALC. Bill Gates tried despirately to hide his authorship of this great code, but we ex KGB men were too clever for him. Now we shall freely distribute the source to all of the workers of the world. Intercalc shall be the official computer language of the USSR, much as we love you capatalist pig zigurat syle building. Freedom comrads, freedom!

  99. Re:Reichstag Fire by Mr.+Piccolo · · Score: 1

    Oh yes it would.

    All it requires is that the trojan be setuid root.

    --
    Glückwünsche, haben Sie Slashdot ermordet, indem Sie zum korporativen Druck beugten und Subskriptionen einlei
  100. Re:Russians by Fist+Prost · · Score: 2

    And you would do what exactly with that steaming pile of crap that it is? Have you heard the expression tar'baby before? Once you've even glanced at something like Whistler source, every thing you code involving Windows (think WINE or plex86 here) would be suspect. The worst thing you could possibly do to hurt the OSS movement would be to wantonly distribute something like that. Better to just burn it and pass it around on unmarked CD's if that's your plan.

    Fist Prost

    "We're talking about a planet of helpdesks."

    --

    Fist Prost

    "We're talking about a planet of helpdesks."
    -Jaron Lanier
  101. Re:Childish attacks unnecessary by jbarnett · · Score: 1


    You idiot, ever here of VPN? of coarse the have an isolated Intranet

    They DON'T have an isolated network, proof of this? Someone just stole (or had the possiablity to steal) their source code from their "isolated" network. How can it be "isolated" if someone from russia accessed it via the Internet? If the network is accessiable from outside their network, it isn't isolated you dumb fuck.

    but they have to offer users remote access.

    They don't have to do shit. If they do decide to offer users remote access, they should of considered the security considers and minimized them greatly.

    Unplug the t1, you are so clueless,

    It was a general statement. Like pull the plug on the computer, I realize there is more than one plug connected to a computer. I don't have a network diagram for their network, nor do I care, there is something connecting the developers to the rest of the world, whatever it is, pull it.

    try multiple OC48's dipshit. And try monitoring 30,000 users internationaliy over a coperate network that puts most ISP's to shame.

    Deny by default. At the firewall level, only accept from trusted hosts, kill and log everything else that even attempts to go though.

    Site down write a perl script to parse the logs, create a graph in GD so you know where all your bandwidth is going.

    If data is being transmitted/received to/from a unfamlair host (I think a Russian IP would stand out a little!!), look into it and find out what they doing.

    It was a fuck up on the admin's part and you know it. It doesn't matter how many fucking lines they got coming in/out of there, it doesn't matter how many users they have or how complex it is, the concepts are the same.

    It is the network admin's part in this, to maintain a secure network, no matter how complex it is, that is his job, that is what he gets paid for. If he can't do it, he should try getting a job a McDonalds.

    It is the system admin's part in this, to maintain secure servers or any machine he is responiable for.

    A big corp like Microsoft probably even spends a good deal of money on hiring security officers to make "extra" sure this type of stuff doesn't happen.

    Someone didn't do their job. Plan and simple. Don't bitch about details.

    Posting as AC, nice touch!


    --

    "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
  102. Re:/. edit box (Was: See what happens when you...) by F452 · · Score: 1

    That sounds like a good idea. My usual replies are one or two sentence throwaway remarks where I don't need much room, but my original reply to you did strain the bounds of the comment box :-)

  103. How'd they get username/passwords? by Molesworth · · Score: 2

    I'm interested to hear how the trojan got access to the usernames/passwords - these were sent back to the crackers periodically via email.

    Simply sniffing keystrokes in usermode wouldn't have allowed the login keys to be captured (because the logon process runs under a different session), however passwords used for "net use" connections (i.e. connecting to file shares) could be visible (I'm not sure, though)

    Sniffing the network requires admin rights (like Unix) and would only give you acces to encypted Kerberos tickets...

    Any other ideas on how they did it ?

    --
    Yesterday I woke up sucking a lemon...
  104. Re:s/NT/stupidly trojan-enabled software/ by phil+reed · · Score: 1
    If it did, viruses, trojans and whatnot wouldn't be able to read and write files they weren't supposed to. The evidence is against your statement.

    Have you ever looked at the security structure of an IBM mainframe or AS/400? Now THERE'S a proper security structure. A virus cannot even get started on those machines.


    ...phil

    --

    ...phil
    "For a list of the ways which technology has failed to improve our quality of life, press 3."
  105. I don't get it... by bozone · · Score: 1

    Discussion topic: Highly sensitive data was e-mailed from within M$ to Russia.
    Majority Response: MS security / Outlook / VBScript / NT sux!

    Did I miss some facts in the article stating that VBScript / Outlook / NT expolit was used to send the data? Or is the majority (there are some level headed posts intermixed) enjoying some FUD spreading? /. is quick to scream FUD when it's pointed at your favorite OS but just as quick to throw it around. Anyone know for sure that it wasn't a Perl script or C program that sent the SMTP data?

    BTW, why all the cracks about the MS network getting real security? Seems to me that they must do a fairly decent job or they would be getting cracked all the time. Should the MS security people be reduced to common hacks b/c of this one incident? I had a boss with this mind set. After 3 LONG days trying to troubleshoot a production problem, it was finally resolved. When I explained the fix, his only comment was 'why didn't you try that 1st'...It's easy to be an arm chair quarterback

    --
    "Hatred is the coward's revenge for being intimidated" ...George Bernard Shaw
  106. Re:You can do this in Windows too. by Zagadka · · Score: 1

    whois != nslookup

  107. Never mind the source code by mOdQuArK! · · Score: 2

    It's probably wise to check the source code for changes, but what they REALLY need to check is their compilers!!

  108. Re:Reichstag Fire by rumba · · Score: 1

    Knock, knock
    Who's there?
    Richard Stallman.
    Richard Stallman who?
    Don't tell me you've already forgotten me!

    It's may not be funny, but it's still a joke.

  109. Hey moderators! by Mr+44 · · Score: 1

    someone moderate this post up, or moderate down the blatantly false post above!

  110. Microsoft Goes Open Source by vagn · · Score: 1

    Not that they ever intended it. Who would want a look at the
    NT source code?

    First, everybody that is paranoid about the CIA inserting
    back doors. This includes every intelligence agency in the
    world not connected with the US or UK governments.

    Second, everybody that would want to exploit such a back door, or
    insert their own. Now we can add terrorists, industrial spies,
    and dishonest competitors to the list. Bin Ladin probably has
    his copy already.

    Third, honest people who are forced to use NT, but are concerned
    about security.

    If the NT source was stolen by people with a profit motive,
    then the desire to maximise profit will lead to the eventual
    large scale distribution of the sources. To what effect?

    The first group will quietly assess the risks, and a few of
    them may exploit any opportunities.

    The second group are in it for the exploits.

    The third group just want their systems to work.

    Now, this is the interesting part: The third group is large,
    and probably willing to share their findings for the good of all.
    However, being honest, they will not make use of the source
    unless it comes to them openly.

    The first and second groups have no such scruples. This means
    that from now on NT will suffer from all the security problems
    that are ritually attributed to open source, but without the
    mitigating effect of a large community working to close holes
    and improve the product.

    The best thing Microsoft can do is go all the way and open the
    source in a way that will give honest people a chance against
    the crooks. It's only a matter of time before choice exploits
    are auctioned off e-bay style on some mafia site (e-sploit.ru
    anyone?).

    Of course, Microsoft will never put their customers first.
    Their source will stay closed. They will try to persuade
    everyone and their grandmother that with enough lawyers and
    police the damage can be contained. But that is just not so.
    Maybe they will attempt to outlaw source code of any kind in
    order to simplify the task of the police. You will need
    a licence for hello.c in that vision of an appropriate response.

    It's been said before: NT, security, networking -- pick any two.
    Hard to believe it could get worse, but it just did:
    Security, honesty -- pick one.

  111. Re:Not A Good Thing by Mr.DarkStar · · Score: 1

    As far as I can see the original source of the problem (according to the reports I've read anyway) is that an MS employee read an e-mail with an attached Trojan Horse. Ultimatly it doesn't matter what OS you use running an executable sent from anywhere that you don't trust (indeed even ones you do trust) is never a sensible option. Personally, if someone suggests a program, I always go to the source and download it 'Fresh' from there, if I can't do that I usually don't run it.

    Granted you can argue that if you are not root on a Unix/Linux box there is little you can do, but the point I am trying to make is that you should never ever ever ever run an executable you don't trust. This should be company policy (which I guess it probably is) and the employee is as much at fault as any weak security used to protect the source code.

    Oh and before anyone flames me to death for being a Microsoft supporter - I'm not. I hate the method(s) Microsoft use as well. I'm just making the point that it may have been the 'offending' employee should have known better.

  112. Micro$oft Crack by digitaltraveller · · Score: 1

    It would be nice if those guys with the source shot a few copies off to say the WINE team and anyone else who needed details of undocumented M$ API stuff. The fact of the matter is, this is one thing justice should have forced them disclose a long time ago. M$'s main benefit in the marketplace is it's control of the mainstream application market.

  113. Re:umm. wait. by juzam · · Score: 1

    ok... but its cool! um yeah, i would ave no idea how whois works anyway.

    --
    --- Hey, Jesus is coming! Everyone look busy
  114. ahhhhh! by NuclearArchaeologist · · Score: 1
    Too much vodka. I have nothing good to say about calculators. Go see the finest of all programing languages:

    INTERCAL

    I spit on you bougois pigs and your computers. Belch. Tomorow, I will own the world.

  115. Start the bets....how long before it's leaked :) by tegument · · Score: 1

    wonder how long it'll be before the source code is anonymously released to the open source community by whoever took it :)

  116. The Market sees this as a good thing by frank249 · · Score: 1
    After Microsoft reveals that its most guarded secrets have been stolen, the stock market rewards it by increasing its share price by over 5%. What do investors know that is not readily apparent?

    --

    Today's vices may be tomorrow's virtues.

  117. Here's a crazy idea... by Elfboy · · Score: 1

    So Microsoft cuts a deal with the DOJ... In return for the DOJ backing off, Microsoft allows the creation of an 'Incident' that points the cybercrime finger towards Russia in an attempt to help recreate the old 'Evil Empire' to provide the United States with an enemy again. But that's just the paranoia talking now isn't it...

    --
    * We dance where angels fear to tread *
  118. But what about something more sinister? by Harv · · Score: 1
    I haven't read all of the posts-- haven't been able to get into /. for the past hour --but a thought occurs to me.

    Aside from the commercial implications -- breathtaking, at the very least-- or just the classic image of the Mighty One fallen, aren't there some security implications here?

    I feel a little paranoid at even bringing this up, but since 95% of the world's desktop and other computers run on a variation of Windows, and the code has been used in God knows what else, wouldn't the crackers have given themselves enormous leverage to wreak havoc on everything from the telephone system, to air traffic control worldwide, to the gas pump at the local 7-11, to the train system in London?

    It reminds me of what would happen if some kind of wheat blight starts to sweep through the hybridized, genetically non-diverse, non-resistant food crop for much of the world, depriving billions of food.

    Am I wrong, or should we all be very worried right now?

  119. Re:News Flash from Russia! by otis+wildflower · · Score: 1

    After a preliminary exam, forensic pathologists state that their deaths were all caused by ruptured lungs. "If I didn't know better, I would think that they would have died laughing", said the pathologist. One of the police experts who determined that the code was in fact Microsoft's also began laughing uncontrollably, and was rushed to a nearby hospital. He remains in serious condition and on heavy sedatives.

    Was ist das nurnstuck git und slotermeyer?

    (I thought this was outlawed by the Geneva Convention...)

    Your Working Boy,

  120. Microsoft's Evil Plan by dgenr8 · · Score: 1

    Step 1 - Orchestrate a fork of samba
    Step 2 - Fake a break-in, establishing that MS source code is "out there."
    Step 3 - Sneak MS source code into the new branch of samba.
    Step 4 - Merge back into main samba branch.
    Step 5 - Declare that samba is illegal and force everyone to use NT.

  121. MS PLOY!!!! by Batman+Perez · · Score: 1

    i gotta say i haven't the breath to read most of the info, but MSNBC broke the story.... and all i am thinking is a cool calculated strategic business manuveur... they're gonna name someone. In my mind, chances are this may be a move to destroy someone, or something... something that is incredibly harmful to Microsoft... something like Open Source. i'm a king of paranoia(i still think the free masons' bastard sons rule the world), but just watch and see who it is they finger....

    --

    subvert the elitist slashdot patriarchy! (where all the stupid women at up in here?)

  122. Re:The end of email-attachments? by cfish · · Score: 1

    If they didn't end VB script execution after Malissa and ILOVEU and hundreds of clones alike, what makes you think they'll change thier minds?

  123. BSOD Colour Changing by highschool-bert · · Score: 2

    In system.ini, under the [386Enh] heading, type: MessageBackColor=(Hex colour of choice) MessageTextColor=(Hex colour of choice) Have fun.

    --
    WWLUG: Feed the penguin.
  124. I agree, let's get off this rock. by TheDullBlade · · Score: 2

    Slaves do not overthrow their masters. Occupied countries are never freed by resistance organizations, only by foreign armies or voluntary abandonment.

    There is no where left on Earth to run to. The tyrants are subtle in rich countries, and boldly open in poor countries; it's merely a question of whether you're a well-managed resource or a poorly managed one. Even the sea floor has been shared out between the great military powers in treaties, and they have the navies to enforce them.

    You can't beat 'em, most can't join 'em, the only option left is to run away, and the only direction left is up.

    --------

    --
    /.
  125. Re:Here's Windows source code by bugg · · Score: 1
    Actually, it's not illegal, but it's behavior is implementation specific (as opposed to undefined, that is).

    I'll open up N869 later and see if I'm wrong, but IIRC it's just not recommended because of the implementation specific behavior- which for most intents and purposes means you shouldn't use it ;)

    --
    -bugg
  126. Re:Childish attacks unnecessary by Ryu2 · · Score: 1
    A few years back, I worked at Microsoft as an intern, working on what is now Office 2000.

    Contrary to people what might think of everyone at Microsoft having unrestricted access to source code, things are compartmentalized in the form of access restrictions on just who can access code.

    In general, only people actually involved with a product can see source for it. Eg, the Office developers can't see Windows source code and vice versa. These restrictions might have been put in place to alleviate some of the Justice Department's concerns that having access to OS source was giving the apps group an unfair advantage, but nevertheless, there are barriers even internally -- you can't just go and access source code to everything that MS has from any one workstation behind the firewall.

    --
    There's 10 types of people in this world, those who understand binary and those who don't.
  127. Re:The heart of the problem... by Tony-A · · Score: 1

    Hmmmm. "... an unscrupulous company looking to make its applications work more smoothly with Microsoft's dominant operating systems"
    Do I detect an implication that any company looking to make its applications work more smoothly with Microsoft's dominant operating systems would have to be unscrupulous?

  128. backdoors? by marten · · Score: 1

    Cool, now we can see if Microsoft really built in backdoors.
    What if it turns out Microsoft really was looking over our shoulders? Now, that would be a trial.
    The whole thing would even be bigger if it turns out such a backdoor was part of a deal with US goverment.
    1984?
    But hey, I'm not counting on anything, who says the source _will_ be posted anyway?
    It wasn't even said they have the source. Maybe they started downloading DOS 2.11 and just finished windows 2.03? ;-)

    ---
    Insert quote here

  129. Re:Childish attacks unnecessary by sickman · · Score: 1

    It's "should *have*" not "should of." If you must abbreviate "should've" is alright. read a book once in a while, then post.

    --
    Sickman's spinfusor catches Anonymous Coward by surprise.
  130. Let's remember the real victim here. by TheDullBlade · · Score: 2

    Somewhere, possibly in Russia, some poor, misled hacker now has to read MS source code.

    Poor bastard.

    --------

    --
    /.
  131. Re:stolen or not? by tegument · · Score: 1

    yeah that's what they stated this morning..but then ballmer chnged his story this afternoon and said that the source code had been copied out

  132. If you see and advertisement like this... by Michael+Jennings · · Score: 1


    If you see and ad like this:

    WinSki 2000, works just like Windows 2000, only 20 rubles.

    Be suspicious!

  133. Neal Stephenson sez... by anonymous+cowerd · · Score: 2

    ...By clambering over this structure and going into these bright shapes, Hiro could probably uncover some of the code that makes Rife's network operate. He could, perhaps, try to hack it up, as Juanita suggested.

    But there is no point to messing with something he doesn't understand. He might waste hours fooling around with some piece of code only to find out that it was the software to control the automatic toilet flushers at Rife Bible College...

    I wonder what they found, those probing hackers. If it were merely bare source, Neal above suggests, nothing. Now if it were marketing documents, that would be something; and if it were legal documents relating to all that Federal fuss, well, this would be one interesting crack!

    Why did Microsoft tell, and what didn't they tell?

    Yours WDK - WKiernan@concentric.net

  134. Osma Bin Ladin by tegument · · Score: 1

    Words out Osama and his boyz took it..lol..just kidding..we just like 2 blame him 4 shit :)~

  135. Happy Halloween? by flufffy · · Score: 1
    This was PRECISELY my first thought when I read these pieces: this is a staged event for some reason as yet to be revealed.

    Indeed. Let me offer two interpretations -- toally opposed, of course.

    (A) Perhaps they do want to go open source, a la "Halloween," but to do it without losing face to their investors (one of the objections to Halloween was that the investors would not buy it as a business plan).

    Or:

    (B) Or, as you say, they will use it as a way to beat down open source. This latter strategy is sometimes known as "the strategy of tension." Some interesting examples being the bombing of Bologna railway station in Italy by extreme right wing groups connected w/ the govt, passed off as a left-wing bombing, in order to precipitate a crackdown on left-wing groups; or the British govt. setting up security force controlled, fake terrorist gangs in Northern Ireland, in order to increase their security powers there.

  136. Hope the spin doesn't make you dizzy! by talks_to_birds · · Score: 1
    Well, as you might expect, this is getting spun like crazy:

    "Hackers that broke into Microsoft may have done little more than poke around a few computers, although they had several weeks to explore the software giant's network, sources said.

    Contrary to previous reports that indicated hackers had extensive access inside the company for as long as three months, the period was more likely shorter than four to five weeks, sources familiar with the matter said."

    Well, that's a lot different! It only took 'em five weeks to figure out they'd been cracked.

    The investigation is also focusing on how the attack was executed to determine whether an amateur hacker was at work or if this was an internatinal attempt to steal trade secrets or software source code from Microsoft.

    So your basic scr1pt k1dd13 cracked Microsoft? Any body been on IRC crowing about this 'sploit?

    The attack tentatively has been traced back to St. Petersburg, Russia, sources said, fueling speculation the break-in was an act of industrial espionage."

    Damn it, it was the Russians! Those bastards! Wouldn't you just know it! That'll piss-off all the right-wing Commie baiters in Washington DC.

    (But wait! Can you say "mail-drop"?

    Sure! I knew you could!)

    And finally, aha!

    "Congress has been wrestling with cybercrime legislation ever since the denial-of-service attacks on online retailers such as eBay and Amazon.com earlier this year, and such legislation now seems especially timely with the latest hacker attack, this time on software giant Microsoft."

    Or is the crack timely in relationship to the legislation?

    Has there been any independant corroboration that any of this happened?

    Just wondering, and sceptical, as always...

    t_t_b
    --
    I think not; therefore I ain't®

    --
    I'm on PJ's "enemies" list! Are you?
    1. Re:Hope the spin doesn't make you dizzy! by jdwilso2 · · Score: 1

      I've gotta say man, that last point about the legislation really *REALLY* scares me... Getting the gov't to pass laws that were especially harsh against hackers and crackers would be especially desireable to microsoft, as my guess would be that their software is the absolute most messed will on the net... Granted, that's also because they have the largest userbase, but that's a whole other discussion...

      The point is, could microsoft have done this to themselves in order to get better protection both nationally and internationally (via the russian email address)?

      And if anything along those lines is going on, I really really wanna catch the next ride to mars so I can colonize it... not that I have all the answers, or anything ;-)

      JDW

  137. Re:s/NT/stupidly trojan-enabled software/ by jafac · · Score: 2

    y'all better try again. Here is the registry hack to DISABLE this oh so useful (to virus spreaders) feature:

    delete the key HKEY_CLASSES_ROOT\ShellScrap\NeverShowExt

    --

    These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  138. Re:Why open source is better... by jbarnett · · Score: 1


    You'll never see an article about RedHat like this... "Yeah, they broke in and stole the source to our prize gem OS..."

    AHEM the source code of Linux HAS already been stole, along with the full source of OpenBSD, FreeBSD, NetBSD, Minix and a couple others. Alot of warez sites like ftp.cdrom.com and ftp.tux.org have the code avaiable for download. The source code speard like wild fire and we don't have enough law enforcement to track down these hackers/warez. cheapbytes.com even sells CD-R of the source code for under $5 a peice.

    Please know what you are talking about before posting this disinformation to slashdot.


    --

    "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
  139. Re:The heart of the problem... by vheissu · · Score: 1

    Not to mention the C|Net article that, well you better just read it: But a stolen copy of the source code is a far cry from a legal license to use it, Levy pointed out. While the latter would allow a company to market a competitor to Windows, the former would not. Instead, it could provide aid to projects that are trying to reverse-engineer aspects of Windows. One example is a group called Wine working on technology that lets Windows programs run on Intel-based Linux systems. Those pesky open sourcers stole it! I knew it! When will this anarchy end?

    --
    /* This post not warrantied for mission critical applications. */
  140. Re:No Security on a Windows Network by kettch · · Score: 1

    While I would prefer Linux, I work at a Hospital that uses a sophisticated firewall. However, we also run software on the exchange server that scans all incoming emails. It manages to detect regular viruses and macros. It then deletes them and sends the recipient an email notifying them that the action was taken. Someone will only get hit every 2-3 months, and then only because administration is too cheap to upgrade the mail server, and it sometimes lags a few seconds (and yes, that is long enough, for those people who sit at their desks all day hovering in front of outlook, to open up the attachment) This might be a good thing to look into, there are several companies that offer this sort of thing, and it does work.

    --
    Opportunities multiply as they are seized. --Sun-Tzu
  141. Re:What people are worried about by Austenite · · Score: 1

    1. ...the crackers could have modified Microsoft source code? No. Look, does anyone believe MS don't use version control and offsite backups?

    Well, they don't appear to use any Anti-Virus measures. Norton Antivirus installed on the workstations or even just on the server would have detected this almost instantly!

    For bonus points, discuss the reasons virii exist on the Win32 platform....

    --
    "In person, WAP'ed up and making your life a misery!" BOFH, 2003
  142. well, i have to say it... by jdwilso2 · · Score: 1

    but where can i get my copy!

    yeah, i know, hundreds of other people are probably looking for it too, but wouldn't it be in some way useful it somehow it accidentally got leaked to the general public? I mean, beyond the fact that microsoft would be in a bad spot, wouldn't it be more useful to humanity as a whole if the "cat were out of the bag" so to speak?

    And here is another intersting thought: could microsoft put the cat back in the bag ? I think they could! That's a whole lotta source there, and even if it got posted on the net and all kinds of slashdotters got ahold of it, I think that microsoft would have the money, the desire, and the wherewithall to come down hard on as many people as they could. And I think that might just scare enough shit out of enough people to where no good use would come of the source of the beast.

    But... I still want a copy!!

    JDW

  143. Re:The heart of the problem... by greenrd · · Score: 1
    Oh yes it does. Just think of all the lives you could save!!

  144. Re:This is obvious but... by mightbeadog · · Score: 1
    Hackers huh? Hopefully they'll fix some bugs before they give it back

    From the CNN article:

    In afternoon Nasdaq trading Friday, shares of Microsoft were up $3.88 at $68.31.

  145. Re:GNU/Linux in Windows? by hammock · · Score: 1

    The bugs and quirks in Microsoft software and API's has never been so well documented as in Samba and WINE, not even at Microsoft themselves.

    No doubt there is alot of code and know-how stolen from open source software in Microsoft software. Too bad they will never get sued for license violation since the source code was obtained by illegal means.

  146. Re:Maybe this is what sunk the Kursk by Mike+Buddha · · Score: 2

    I've always considered the majority of Slashdot readers to be brats, but this goes to show that whatever Microsoft may do to fight the open-source movement, they'll probably win.

    1) How do you know that the majority of Slashdot READERS are brats if they are in fact reading and not posting? If you'd said the majority of /. posters were brats.. then I'd tend to agree with you.

    Why? Because for the most part, it's people like you who make up and support that movement, people lacking any amount of maturity and decency, and for movements to succeed, they must at least be honorable in the face of their enemy.

    2) How do you know that people like the tastless, lame poster make up and support the open source movement?

    I think you're basing your opinions of a fairly large and diverse group of people on the actions of a few morons, who may or may not in fact be in support of Open source. I don't recall anything in that first offensive post that said anything about open-source software. I do recall some insensitive (and, quite frankly, LAME) humor about Microsoft's stability impaired operating system being responsible for the Kursk tragedy.

    You make these vast over-generalizations and your own prejudices shine through, overshadowing the original message: the original poster is a jerk.

    Please consider the targets of your message before you go off flaming good, undeserving people.

    --
    by Mike Buddha -- Someday the mountain might get him, but the law never will.
  147. BBC has a nice perspective by keete · · Score: 1

    From the analysis accompanying the BBC article:

    snip..

    How can the code be misused?

    Potentially, the source code could be used to produce bootleg copies of Microsoft software, perhaps boasting "improvements", or modifications to make it work with hitherto incompatible systems.

    ..snip

    ...sounds like misuse to me. :)

    --

    --
    keete
  148. I dont get you? by Thiarna · · Score: 1

    OK, so whats wrong with the statement that a virus or bug could have been included in versions of Windows shipping now? And why the [sic], have I been spelling bug wrong all these years? It is quite possible they planted a bug, virus, or more likely a backdoor in some Microsoft software, though since the scare Microsoft say they've ruled this out. Myself... I dont think they could know enough yet to rule anything out.

  149. Re:A plea to the perpetrator(s) by rumba · · Score: 1

    Angel 31337: I just uploaded the Microsoft source. It took long enough, but I think we got it all. Just looking at it briefly, Gabriel and I had a pretty good laugh. The comments, where present, are usually jokes about Bill. The one about the sock down the pants...

    God: Good, now what were we going to do with it, install it on all the boxes around here? You guys never tell me anything...

    31337: God, no, we're using it in our suit against Satan. We just found the registry keys to prove that he has a secret backdoor. He wants to use it to immanetize the eschaton.

    God: ImmaWhat?

    31337: End the world. He thinks everyone will run BSD after that.

    God: Hmm. Well, I there's this's guy petitioning me now on Slashdot to release the code. Do you think that will help?

    31337: Why would they want that? They all think it's garbage anyways.

    God: Hmm. Good point, well, gotta run, got a date with one of those BSD girls. Call it industrial espionage...

  150. do *not* ask for the source by criticalrealist · · Score: 2
    Do not post to this thread. Asking for that source is like asking for stolen goods. Under American law, that is a crime. You might not be prosecuted, but why take the chance? This is probably going to end up being the highest profile security crack for many years. The FBI is probably already swarming through slashdot and other hacker hangouts. I repeat. Do *not* ask for the source code. Also, do *not* encourage copycat hacks. That could also be a crime under American law.

    Just for the record, although I hate Microsoft Corporation and I support open source, a crime like this is still wrong. Crime does not pay.

    --
    I am not a lawyer.
  151. Re:/. edit box (Was: See what happens when you...) by gatekeeper-eu · · Score: 1

    My text editing with Mozilla is incompatible with /. or CR/LF gets lost somewhere in cyberspace :-((

  152. Re:Childish attacks unnecessary by Rakarra · · Score: 1
    It was Professor Plum in the library with the laptop and the packet sniffer.

  153. Bills reply by Adler · · Score: 1

    is here

    doesnt it look like hes saying "I'LL GET YOU HACKERS!!! IF ITS THE LAST THING I DO!!!!"

    --

    Everybody denies I am a genius--but nobody ever called me one!

  154. Re:security through obscurity by mattdm · · Score: 2
    Exactly. This is the reasoning behind the adage "security through obscurity is no security at all". It gives a false sense that no one could ever find the weaknesses, when in truth, it just means that only the bad guys know.

    --

  155. Re:Reichstag Fire by 2RockStars · · Score: 1

    It's not a fake - QAZ is a real trojan, and can worm from one Win32 box to another. Look at some of the anti-virus vendors' websites. It got onto my Win95 box sometime in September, and I didn't notice it until two weeks ago. Note that I don't use a mail reader on the 95 box, I just browse with Netscape. Seems to me that the QAZ payload is deliverable in more ways than simply double-clicking an attachment in Outlook. It sends your IP address as a raw SMTP message to an address in China, over port 7192 or something. I'll bet that the receiving box sifts through the incoming addresses until an interesting one is found. Like, say, Microsoft's.

    To check whether or not you've been caught, look at the Notepad executable. It shouldn't be over 100 Kb. If it is, delete it, and move note.com in the same directory back to notepad.exe. There is also a registry entry you must remove - somewhere down in HKCU/Software/Microsoft/Windows/CurrentVersion/Run .

  156. this is gonna kill my "Karma rating" by 20000hitpoints · · Score: 1

    I write software all day for a living. Pay me, give me time, and I'll do exactly what you say in your post. Or, give me a two week deadline, and I won't. And you, like the last person, are missing the point.

    I tell you what, let's see you post your code on this site, "Anonymous Coward", and let's watch slashdot rip you to shreds. You made a mistake here, you could have done this differently/better, whatever -- watch the fun as you hastily justify your decisions.

    My wife makes fun of my by talking in a nasally voice and saying "well, actually, blah blah blah." Don't forget you and I are just smart-ass computer nerds who are competitive and arrogant and think we're smarter than everyone else. The funniest, and worst, thing about slashdot is all the irritating know-it-alls that try to one-up each other. Shut up fucko.

    Guess what I'm doing when I get home from work today? You guessed it -- I'm NOT going to be sitting in front of a computer.

    Bye fucko!

    --
    Don't post on slashdot. Get back to work.
  157. Human error issues.... by ryusen · · Score: 1

    It has already been pointed out that human error could very likely be the cause of the hack... as even the most secure "Gates" are comprimised if someone forgets to close them on the way out(or in)
    the thing that makes me wonder on this is... if ms people are that careless with security... how careless are they with software design?

    --

    I believe sex is highly over rated... unless it involves me
  158. But they beat version control by Thiarna · · Score: 1

    Thats why this crack was different, they were there for months and had use of normal accounts, they could have made any source changes that the victim users could have.

  159. Re:Not A Good Thing by Reziac · · Score: 1

    You mention the, um, interesting times that could be ahead should GNU/GPL/Gwhatever'd source be found in M$'s code... I find it fascinating that a major upgrade was made to M$'s server remote admin tools so very shortly after the BO2K source was made public. :)

    --
    ~REZ~ #43301. Who'd fake being me anyway?
  160. Re:/. edit box (Was: See what happens when you...) by Fist+Prost · · Score: 1

    Assuming you're new here-There is a "slashdot reader" that someone put out on Freshmeat. I haven't had any problems with the defaults here so I haven't bothered to try it out yet but you wish to, and feel free to modify it to your liking. Also bear in mind that slashdot is an open source project. You can always submit a patch and if they like it who knows...

    Fist Prost

    "We're talking about a planet of helpdesks."

    --

    Fist Prost

    "We're talking about a planet of helpdesks."
    -Jaron Lanier
  161. Re:Bad Day for Bill by MarNuke · · Score: 1
    GET STUFFED!!!

    WITH SPAM!!!

    Good stuff at $1.79 for a 7oz can.

    Few foods are as versatile as SPAM Luncheon Meat.

    --
    MarNuke
  162. Re:Here's Windows source code by SteveTheRed · · Score: 1

    ...As Microsoft Corporation's legal representative, we demand that you remove the source code that you have posted on Slashdot.org immediately. You are direct violation of Microsoft's intellectual property rights...

    --

    I, for one, welcome our new robot overlords
  163. Re:Reichstag Fire by DGolden · · Score: 1

    Er.... I think you'll find that only a privelged user (i.e. root, or maybe a member of wheel) can make a suid root file. A trojan you get over the internet is NOT going to be able to save itself as suid root.

    --
    Choice of masters is not freedom.
  164. Changes in source code discovered!!! by YankeeDoodleJoshi · · Score: 1

    All backdoor passwords were changed to "Microsoft engineers are weenies!"


    --
    HTTP header ad space for rent! Advertise to thousands of server log readers - only $50 a week per header! 1-800-SURFALOT
  165. Re:The heart of the problem... by Anne+Marie · · Score: 1

    A mother raising children is not considered "a worker." She is treated as if she has no input or productivity to contribute to the "real economy".

    In Sweden, being a homemaker is assigned a value for the purpose of calculating GDP.

    --
    -- Anne Marie
  166. Yeah, ok by MarNuke · · Score: 1

    Say I'm hacking my own network. Say I find a expolit in a package on a UNIX machine. I write a patch. I apply the patch. I recompile the package. I deploy the package. I have a more secure UNIX based network. Do you really think I can do that with NT? I can't.

    If I find a expolit in NT, I have to submit to mickysoft, disable the service, wait for them to put in the service pack, and then enable the service while I'm left in the sun baking. Sure, it's the same "degree", but one I can do in a night, the other I have to wait a few months.

    --
    MarNuke
  167. Month? Nah, probably a little faster... by Mr.+Flibble · · Score: 1

    Take a PC, install a default copy of RH 6.2, hook it up to a static IP DSL modem. Come back in a month or two, and you'll find that you have
    at least 1 or 2 "volunteer" sysadmins!

    Month or two? Try a few hours. I have tried this a few times, and it is usually compromised within a week. Twice I have seen the machine compromised within 5 hours.

    --
    Try to hack my 31337 firewall!
  168. this is gonna kill my "Karma rating" even more by 20000hitpoints · · Score: 1

    I'm tired of this goddamn site anyway, and it's sure not the fault of the people who set it up. What a great "community" -- a community of assholes, myself probably included. Oh, wait a minute -- sorry: very intelligent assholes.

    --
    Don't post on slashdot. Get back to work.
  169. Very true by shion · · Score: 1
    Ah, so then before running 'make all', the paranoid user can su to some nobody user, and they'll be safe, right? Oh, but not if the make actually does something like compile and execute a suite of known local root exploits.

    This reminds me of the one case a whole ton of years ago when someone added a set of instructions to some cc which would automatically add a backdoor into any generated code.

    There are all sorts of hidden things that any OS or program can do... the problem is to minimize risk; you can't eliminate it.

  170. LIGHTEN THE HELL UP!!! by MarNuke · · Score: 1

    I hate people that says some should be shot for expressing thier views.

    Listen, jack, I have freedom of speech. If I think the guys post is funny, I'm going to luagh. Who the hell are youto say I should be shot. One thing buddy, eat shit. I have rights. I have freedom. If you don't like it who the hell cares. We all have freedom.

    He who gives up freedom for security doesn't deserve freedom nor security.

    And most closed-source zealots have pucked up asses, wet thier bed, and deny other people thier god given rights to be "brats".

    --
    MarNuke
  171. why do I get upset about this? by 20000hitpoints · · Score: 1

    I can't stop people from being idiots. If there's anybody on this site who isn't a fucking asshole, be a pal and respond to this post in a way that shows you aren't. I don't know why I'm asking this.

    Oh well, it's the internet, just a void that you shout into, no answer. Nobody there. Just a bunch of storefronts, but nobody behind the counter. A library with no librarian.

    --
    Don't post on slashdot. Get back to work.
  172. ummm ... bullshit by kipling · · Score: 1
    plenty of mac virii - the first PC (as in personal computers, not ibm-compatible-intel-based-PC) viruses I encountered were mac only. The code-in-resource-fork model of a traditional mac application made it easy to write virii (nVir et al) that could infect arbitrary executables without screwing too much with the application otherwise. There was also a nasty "autostart" worm a couple of years ago that did unpleasant things to your HD.

    Nowadays most of the virii that a mac virus detector sniffs are word macros that fail to work properly on a mac, due to filesystem differences.

    --
    -- open source? sounds like the real book --
  173. Easy: Don't have to. by TheLink · · Score: 1

    Trojan connects outbound and gets instructions on what to do next. Lots of companies allow almost any outbound connection (we don't but I've seen many that do, and many HOWTOs that foolishly suggest it). I can think of lots of ways how the instructions can be obtained, you go think up your own ;).

    There are ways of making it harder for the trojan to be successful - e.g. need to authenticate to surf, everything not expressly allowed outbound is denied. However because of Microsoft's idiocies like storing and autocompleting user passwords, it is even easier for trojans to bypass such controls (any bets on access to digital certs?). And of course they use IE and Microsoft "LookOut" ;).

    Because of these stupid features/flaws, you may have to resort to greater inconveniences like OTP authentication just for web browsing.

    And because software is becoming more and more bloated, people aren't going to notice if your trojan is rather big for what it claims to do, so you can add lots more features...

    Most antivirus solutions can't detect stuff, if you are the first and only target. Some antivirus software have decent heuristic scans and deep scans (AVP), but of course the attacker can always check things out first, then when everything passes, they launch the attack.

    Cheerio,
    Link.

    --
  174. Document-executable distinction. by Raffaello · · Score: 1

    "Torjans are executables, not documents Well, how then do you classify VB scripts then? They are pretty much like a document, being plaintext and all. They are even more like a document when they come embedded in a Word or Excel document. "

    Part of the problem with executable email attachements (a la Outlook) is that they effectively destroy the distinction between passive data, and active executables. Once data becomes executable the possibilities for compromising a system are greatly multiplied, because there is a whole range of files which the user doesn't expect to _do_ anything, just sit there on disk, but which can actually do pretty much anything the user has permissions for on that system. On most Windows machines, unfortunately by default, that means pretty much anything.

  175. Re:Sounds like a great idea! by Mr.DarkStar · · Score: 1

    Bond: "Do you expect me to talk Mr Gates?"
    Gates: "No, Mr. Bond, I expect you to die!"

    Err ok, I'll get my coat.

  176. 1000th Post! by istartedi · · Score: 1

    suckuz

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  177. 967th Post! by istartedi · · Score: 1

    I bet nobody reads this. I want to shake my karma down to below 50 though, so I can be a ho again.

    --
    For all intensive purposes, "whom" is no longer a word. That begs the question, "who cares"?
  178. Re:umm. wait. by SgtAaron · · Score: 1
    try a whois on microsoft.com. they've been cracked in more ways than one.

    That doesn't have anything to do with Microsoft. What you are seeing is the result of flawed pattern matching by the WHOIS server, which terrorists.net has taken advantage of (to prove a point or for joke benefit I guess).

  179. Russian attempt to crack US Navy Security? by Raffaello · · Score: 1

    Considering that the US Navy recently announced that they would be using a _future_ MS OS to control the next generation of aircraft carriers
    <http://www.fcw.com/fcw/articles/2000/0807/news- navy-08-07-00.asp>
    the possibility exists that these were Russian crackers looking for access to US military networks.

  180. Re:Pulleth The Other One, it hath Bells On by Chops · · Score: 2
    Doom-saying is all fun and games, but please do try and stay within the bounds of reality...
    I agree with you an I hope that you're right, but remember that reality has very little to do with what happens inside a courtroom that has a technology case on its hands.
  181. Re:Should I release the code? by maximus+hans · · Score: 1

    use http://www.geocities.com hehe....all the best to you in your corporate take-down-those-dirty-bastards-from-the-inside endevors

  182. Don't get Cocky by Forge · · Score: 2

    Don't get too cocky now. Remember that Microsoft's isn't the 1st "flagship" site to be cracked. In fact. I think Sun Microsystems and posibly IBM are the only ones that havn't.

    Slashdot, was owned. Apache was defaced, Credit cards were stolen from some Ecomers places.

    Just be thankfull the source code for Windows didn't leak out. It wold be so horible if it fragmented into varius incompatible versions.

    Huh... What's that ? It's hapening already ?

    well at least we don't have to sufer throgh the pain of reading that code.

    --
    --= Isn't it surprising how badly I spell ?
  183. Re:Should I release the code? by H*rus · · Score: 1

    1. Go to China
    2. Step into a internetcafe
    3. Post a article on /. explaining what you'll be doing.
    3. After 2 ours (give commanderTaco some time):Hack the MS site
    4. Place the source-code on the MS-site
    5. run
    "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former."

    --

    - if you love something, set it free; if it doesn't come back, hunt it down and kill it
  184. Lots of sites get compromised... by jetson123 · · Score: 2
    Lots of sites get compromised. Most people just don't put important information on visible computers and they don't blame hackers when it happens--they fix it.

    Microsoft, on the other hand, inflates the importance of what happened. I mean, after all, who gives a damn about their source code? And then they are crying out of the FBI to help them track down the evil criminals, costing tax payers lots of money, rather than admitting that they did something stupid, fix their processes, and move on.

  185. The heart of the problem... by guynorton · · Score: 5

    This quote taken from the Yahoo coverage..

    "The code could also be purchased by an unscrupulous company looking to make its applications work more smoothly with Microsoft's dominant operating systems"

    Who is 'unscrupolous'?, the company trying to improve their software for the greater good of everyone? I think it is the company that won't reveal the source code...the company that has systematically crippled/sabotaged other companies by keeping their 'intellectual' secrets under wraps in an attempt to leverage themselves into any software based market they see fit to at the expense of others.

    I think this quote basically sums up the whole open source/closed source debate.....

    Guy

    1. Re:The heart of the problem... by Stonehand · · Score: 1

      Because it's theft. One wrong does not necessarily excuse another.

      It may be unethical to for an aging millionare who hates his family to suddenly start wasting his entire fortune and gambling like mad to make sure no possible heir gets a cent -- but that doesn't make it ethical to rob him to stop the waste.

      --
      Only the dead have seen the end of war.
  186. "If It can happen to Microsoft" by Felinoid · · Score: 2

    I work nights so I woke up to the radio news about this and an expert saying "If this can happen to Microsoft it can happen to anyone"

    I step back and think.. isn't this sort of the way Microsoft responds to everything?
    If it's a problem on Linux or Unix its unique to Unix or Linux.
    But if it's a problem on Windows it can happen to anyone.

    E-mail viruses.. ANYONE can have e-mail viruses (Note in the 1980s Unix experts were saying Unix was immune to viruses.. This is far from a unique clame.. Mac users made the mistake of razzing Dos for viruses... forgetting that everything that made dos viruses posable was present in MacOs.. however absent from anything else)

    Back doors are supposidly unqiue to open source yet back doors usually happen as a result of an employee not the result of an unknown coder submitting code.

    Anyway... look for the spin.. any time Bill Gates gets hit with a pie in the face we are told we are all hit with a pie in the face..
    When Linus locks his keys in his car it's unqiue to Linus...

    Side Note: Anyone notice Bill Gates didn't throw a fit but USA, California, SanFransisco Mayor Willy Brown did...

    On the other had we do have a point to make...
    If Microsoft can't secure it's own network should you trust them with yours?

    --
    I don't actually exist.
  187. Code not compromised by riggwelter · · Score: 1

    According to Linux Today, Microsoft say that the code is safe after the attack (presumably as safe as it was before, ahem...)
    Info here ;


    --

    --
    Listening for the sound of the coming rain...
  188. You MUST BE WRONG by jetson123 · · Score: 2

    Microsoft explicitly stated that E-mail attachments are not dangerous because, after all, you don't have to open them. In fact, of course, it's common practice to delete all E-mail from people you don't know sight unseen. So, you must be wrong: Microsoft said so when the Melissa virus came around.

  189. Why? Because Microsoft said so. by jetson123 · · Score: 2
    It's not that there is some evil conspiracy to smear Microsoft. Microsoft does themselves in. After all, they claim near perfect security yet don't meet their own standards. They run off to the FBI to waste tax dollars on tracking down some teenager in Russia, and they are the ones that state that someone looking at Windows source code is the end of the world (as if anybody really cared).

    The attitude more commonly found among UNIX sysadmins seems healthier. Yes, we know it's buggy. Yes, we aren't perfect. And if it's broken, it's our fault, and we'll try to fix it. And let's try to keep important stuff somewhere nice and isolated.

  190. Can the Russian crackers tell us... by mwillis · · Score: 2

    What NSAKEY is all about anyway? Did MS lie, and leave a big fat backdoor for spooks? This is the only thing in the w2k source that even vaguely interests me.

  191. Re:s/NT/stupidly trojan-enabled software/ by DavidTC · · Score: 1

    Actually, it's .shs it hides, no matter what you do.

    -David T. C.

    --
    If corporations are people, aren't stockholders guilty of slavery?
  192. THe BSOD Bitch is back. by linuxgod · · Score: 1

    Look, the little asshole who has to repeat himself to make it look like he is talking to someone is back.


    Ignore the Anonymous Pissant trolls !!!

    1. Re:THe BSOD Bitch is back. by linuxgod · · Score: 1

      Look its the anonymous troll !!!!


      Ignore the Anonymous Pissant trolls !!!

    2. Re:THe BSOD Bitch is back. by linuxgod · · Score: 1

      SOrry, im not in HS like you little babys.


      Ignore the Anonymous Pissant trolls !!!

    3. Re:THe BSOD Bitch is back. by linuxgod · · Score: 1

      I have a job. I work on peoples machines all day. NT? ya, i noticed thats the only OS that needs to be fixed daily. Sorry, i lost mine 5 years ago.
      Im gonna be single. I got enough $ i wouln't need to pay anyone anything. You must be poor and hungry. Do you need some food?


      Ignore the Anonymous Pissant trolls !!!

  193. Re:The end of email-attachments? by divec · · Score: 1
    Why would it be difficult to get an MS employee to download anything moronic?

    Why would they bother? All the moronic stuff is already preinstalled ... :-)
    --

    perl -e 'fork||print for split//,"hahahaha"'

  194. at what price? by ColdTap · · Score: 1

    Knowing how much malicious glee this news brings to this site... at what price? This will only feed the 'Stop Hackers at Any Price' sentiment. I can't help wondering if MS didn't permit it to happen... It makes them look vulnerable, (not a trait associated with super-power monopolies) and gives Bill some ammunition to use against the 'open-source-file-swapping-naked-box-hacker-menace '. A much better ROI than the crappy product he peddles.

  195. Re:Read the (full) Wall Street Journal Article by SETY · · Score: 1

    Same as MSNBC link on story is it not?

  196. Integrity by Brett+Viren · · Score: 3
    From the MSNBC/WSJ article: ``We are confident that the integrity of Microsoft source code remains secure'', a Microsoft spokesman.

    Remains? Since when has there been any integrity to MS code?

    1. Re:Integrity by horza · · Score: 1

      Something that made me laugh is on the BBC they had a security consultant who pointed out that with the source code someone could distribute a version of Windows that "gives out your personal information or destroys your data". My first reaction was: this is different... how?

      Phillip.

    2. Re:Integrity by athmanb · · Score: 1

      You don't seriously believe that anyone (except perhaps a programmer which has been with Microsoft for 10 years and knows all the code changes since Windows 1.0 by heart) could change even one little line of the Windows code and the thing would still compile afterwards, do you?

      --------------------------------------

  197. DNS entry also cracked by beebware · · Score: 2
    According to this article on The Register, Microsoft, Apple and AOL's DNS entry has also been cracked.
    It's DNS entry currently reads:
    MICROSOFT.COM.IS.SECRETLY.RUN.BY.ILLUMINATI.TERROR ISTS.NET
    MICROSOFT.COM.IS.RULED.BY.HACKERJACK.COM
    MICROSOFT.COM.INSPIRES.COPYCAT.WANNABE.SUBVERSIVES .NET
    MICROSOFT.COM.HAS.NO.LINUXCLUE.COM
    MICROSOFT.COM
    Apple's says:
    APPLE.COM.IS.THE.CHOICE.OF.ALL.SELF.RESPECTING.TER RORISTS.NET
    APPLE.COM
    and AOL's says:
    AOL.COM.KCAUTOWEB.COM
    AOL.COM.IS.REGULARLY.HAX0RED.BY.INSIDE-AOL.COM
    AOL.COM.EATMYSHIT.ORG
    AOL.COM.AMSLIQUIDATORS.COM
    AOL.COM
    Somebody has been busy...
    Richy C.
    --
    1. Re:DNS entry also cracked by Ranger+Rick · · Score: 1

      Dammit! I get righteous and you agree? How is that supposed to make me feel? =)

      --

      WWJD? JWRTFM!!!

    2. Re:DNS entry also cracked by Polaris · · Score: 1

      Try Netscape.com:

      NETSCAPE.COM.SHOULD.SHAKE.OFF.ITS.CHAINS.AND.FUC KAOL.ORG

      NETSCAPE.COM

      I am adding in this extra lc text to beat the lameness filter.

    3. Re:DNS entry also cracked by Ranger+Rick · · Score: 3
      Jesus christ already, that's not cracking, I'm sick of seeing this "story"!

      All those are is host entries under, say, terrorists.net or hackerjack.com.

      If you have a DNS that is acting on behalf of registered domains, it's IP address is registered to the registrar so their root servers can point to it.

      So if you say you have a DNS server called "microsoft.com.is.secretly.run.by.illuminati.terro rists.net" it will show up there.

      So can we agree that there's no "cracking" going on? Sure, it's a neat hack, but I've seen this thing in e-mails, on 4 different web "portals", and now in comments as well. Please, for the love of god, make it stop! :)

      --

      WWJD? JWRTFM!!!

    4. Re:DNS entry also cracked by beebware · · Score: 1

      Oh - sorry, so it is. You're right. If anyone does a search with http://www.internic.net/cgi-bin/whois?whois_nic=DO MAIN you do infact get up ANY servers register in the DNS with the string 'DOMAIN'.
      You're perfectly right, it's not a crack or hack, but someone knowing that people would try a search like that and register a server with a name that would occur in the search string.
      It's still funny (and kinda topical to this story).
      Oh well, I'll go and revise my knowledge of the DNS system (grin)
      Richy C.
      --

    5. Re:DNS entry also cracked by mikej · · Score: 1

      Not true. Do whois on 'microsoft' and you get all of the microsoft (.net .org etc.) in addition to these listed. A query against the whois database returns all matching strings: Someone has a nameserver registered as MICROSOFT.COM.IS.SECRETLY.RUN.BY.ILLUMINATI.TERROR ISTS.NET, that's all. I could register MICROSOFT.COM.IS.POOPY.JURNEY.NET tomorrow if I wanted. Not a hack, just good clean fun.

      --
      Ideology breeds Hypocrisy. Just how much is up to you.
  198. blow me by linuxgod · · Score: 1

    You little pissant shit, are getting on my nerves.


    Ignore the Anonymous Pissant trolls !!!

  199. You can't even do that. by DavidTC · · Score: 1
    Actually, you can't even get your own password as an unpriviledged user. You'd have to set up some fake login prompt and wait for yourself to log in. Or course, that way you can get anyone's password, assuming they don't do Alt-SysReg-K first to reset the console, or Ctrl-Alt-Baskspace for xdm. It's probably easier to get other people's password then you're own this way, because you'll know you installed the fake login program, and will reset before login.

    Of course, all this is rather hypothetical, as stealing passwords from yourself is rather stupid. :)

    And, if you really wanted too, you could just email the admin asking him to change it to a different one. :)

    -David T. C.

    --
    If corporations are people, aren't stockholders guilty of slavery?
  200. Your father is a hamster by Gorimek · · Score: 1

    As you seem to say yourself, that was a long time ago. Today's virus hackers just don't use macs. The word viruses you mention come from the windows world.

    I remember sometime in 98 or 99 during Apples rise from the ashes how the discovery of the first new mac virus in years was hailed as yet another sign of the mac revival :-)

  201. Re:Childish attacks unnecessary by Charles+Dodgeson · · Score: 1
    And someone please explain to me why the SYSTEM ADMIN was checking his email with the ADMIN account on a SECURE MACHINE. Then running an unknown program as ADMIN user!

    This is the heart of the matter, and I think that some design aspects of NT are to blame. You really asked two questions here. First I'll speculate at why someone was running as admin.

    • It is remarkably hard to do anything if you are not admin.
    • Unlike *nix users, you can't easily have a "root" terminal window open while your X-console session is under an ordinary user. Being logged in as admin is an all or nothing thing.

      If you had to log out and log back in every time you need to do anything that requires access, you would run as admin all the time too. At least after the first week of doing that.

    Now why run an untrusted program? Again, there are things about the design of NT that encourage that.

    • content-type is very tightly linked to file names.
    • file name extensions are typically concealed
    Users on any system could make such a mistake, but those two things make it much more likely that an NT users will make the mistake of running an untrusted program.
    --
    Prime numbers are exactly what Alan Greenspan says they are -S. Minsky
  202. And speaking of Idiots by Rogain · · Score: 1

    Are you the sort of idiot that goes about logging into remote systems without the benefits of ssh???? My goodness indeed!

    Can anything on slashdot not be discussed without dorkwads calling each other idiots? One day, when I rule the universe, and don't try to kid yourself, that day IS comming (and soon I might add), such vulgar displays of crudness will be punishable by testicular-removal.

    --
    The current Slashdot moderation system is made by gay communists!
  203. Re:Redhat Cracked by Saint+Aardvark · · Score: 1

    ROFLMAO...

  204. Re:Open Sourcing Windows... by luckykaa · · Score: 1

    They may very well have the kind of leverage to get the US government to pressure whichever countries supply SeaLand's bandwidth to have SeaLand cut off

    The US would have to pressure a few North Sea countries (All reasonably wealthy with no real dependence on the US) essentially as a favour to a corporation currently being tried for monopolistic practices. Of course, MS could directly approach those countries.

  205. The spy in your Software by senfman · · Score: 1

    I think that there are many reasons for beeing scared of this news. Somebody who had access for over 3 Months, had enough possibilities to include i.e. BackOrifice in Windwos.
    Maybe this sample shown, that it's always better to use free software.

    1. Re:The spy in your Software by divec · · Score: 2
      you've checked every line of your linux kernel for back doors then, correct?

      Someone has. Well, not quite to the OpenBSD level, but each patch has been read by someone. And there is an unbroken patch link from linux 1.0 to current versions, so I guess the chances of those patches having been looked at are pretty high.
      --

      perl -e 'fork||print for split//,"hahahaha"'

    2. Re:The spy in your Software by Tony-A · · Score: 1

      I haven't checked any, but methinks there are some paranoid souls who have checked quite a few and would be yelling their heads off if they found any trace of a back door.

  206. Re:Open Sourcing Windows... by drsoran · · Score: 1

    But Sealand is a sovereign country. According to their FAQ a few months ago, the only thing they will not host is child pornography on Sealand itself. They planned on establishing POPs in various countries with various laws.. the laws of that country would determine what is legal or illegal. I would imagine if they established a POP in China the code would be distributed from there. ;-) All I want to know is.. WHERE ARE THE MIRRORS!? Get this thing out there! Get it on EVERYONE's servers. Bitchslap Microsoft once and for all. I have a feeling though there's not much use of having the MS source code without having all the development tools they use and the roadmaps and notes... there's probably more spaghetti code in Windows than in Mozilla and StarOffice combined (actually we're positive of that). The Mozilla guys just gave up and started from scratch... hehe. So, like Mozilla.. will the source they stole even compile or do you need their secret tools? I doubt they use GNU auto configure and make!

  207. fud fall out? by geoff+lane · · Score: 1
    It will be interesting who MS accuses over the next few weeks.

    Question one is, will MS go off on a tangent blustering about hackers and script kiddies; or will they actually LEARN a lession and take some notice of all the good security advice that is available in the net?

    Q2 is "Why hasn't this happened before?" MS can't be the only windows/nt site in the world that is not attacked by script kiddies. What normally protects them; why can't we buy it?

  208. What a coincidence by Tubster · · Score: 1

    That just a few days ago they somehow managed to get Office2000 running onder WINE MOOHAHAHA

  209. Re:Open Sourcing Windows... by luckykaa · · Score: 1

    You may have a point. I think a good lawyer would be able to make a case for Sealand being British territory. Probably by arguing that it was never an independent country. Considering the amount of money that various extremey rich people have invested in it, the legal battle would probably go on for so long that Microsoft's copyright would have expired.

    The earlier comment suggested that the UK Gov. should just use pig headed arrogance, assume it's their property and demolish it. Sealand could sue for damages, but it wuldn't be worth it.

  210. Re:s/NT/stupidly trojan-enabled software/ by k3rn3lH4X0r · · Score: 1

    Not to be too pedantic, but as administrate is not even a word, it's adminster.

  211. Why MS Windows is a special case by Sloppy · · Score: 2

    Seriously, though... one of the more serious reasons that viruses/trojans spread more easily on Win32/Mac is "user imbecility/gullibility".

    That gullibility is manifested not just by the users' poor choices while using the applications, but in their poor choice of the applications themselves.

    how long before something like this happens on a Linux box?

    A long time.

    It's not so much due to any specific virtue of Linux, as it is due to selection pressure. On any non-MS platform, there is competition among applications. That means if some incredibly irresponsible app developer releases applications that treat data as code, they will be subject to market forces and backlash and their apps will not become popular among the users of that platform. Go ahead, write an email reader for Linux that executes scripts that are embedded in the emails that it displays, and see if anyone still bothers to use your program once this "feature" has become known.

    Whereas among MS Windows users, it's pretty much a given that you'll use Outlook, IE, Word, Excel, etc. regardless of whatever virtues or faults those apps happen to have. The flaws in the overall design philosophy (not just bugs) have been known for years, and yet people still use these apps.

    Every single application market other than MS Windows has selection pressure in the direction of increased security, and MS Windows does not. Until the market changes (i.e. Microsoft is hurt), Windows will have significant security disadvantages compared to every other platform.


    ---
    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
  212. Re:What people are worried about by CharlieG · · Score: 2

    5) Or people hack on the source code, put in a nasty virus or trojan, and then distrubute it as part of a shareware/freeware program, or hack the Microsoft site, and put it in as part of "Windows Update"

    A few weeks later, 50% of the worlds PCs are wide open

    --
    -- 73 de KG2V For the Children - RKBA! "You are what you do when it counts" - the Masso
  213. Re:hope source code gets out by gb · · Score: 1

    On the other hand we then get the very worst combination of open and closed source... its open for crackers to figure out how to break in and closed for hackers to plug the holes. Given that MS is highly unlikey to go open source, I for one am hoping the source doesn't leak this time.

  214. Marvel at the possibilities!! by surferfro · · Score: 1
    Is it really a suprise that a network made completly of NT/2000 was hacked?

    I am curious as to the motive of the hackers, Piracy, Blackmail, or just "because it was there". Imagine if the source code was dumped onto source forge or some other open source collaborative site (preferably out of the legal reaches of M$ in a former eastern Bloc country)One article spcefically named WINE as an application . Maybe the patches would be released in a timly manner and actually work.

    Then again fixing Windows is a pretty daunting task for a million open-source developers

    --
    A computer lets you make more mistakes faster than any invention in human history - with the possible exception of handg
    1. Re:Marvel at the possibilities!! by phillymjs · · Score: 1

      According to the MSNBC article, the infiltration was made possible by a Microsoft employee who received a Trojan horse in e-mail and activated it.

      Didn't Microsoft take all of us "stupid users" to task for opening those "ILOVEYOU" messages in our mail some months ago?

      I think it's great that their own employees are now officially just as dumb as they consider the great unwashed masses to whom they peddle their crapware, though I'm sure they'll publicly put a different spin on it.

      I hope that those evil hackers made off with the Crown Jewels of Redmond, and that in a couple weeks people will be able to buy CDs of Windows and Office source code on the street in China for $5, or download it from Hotline.

      It doesn't even matter if anyone does anything with it, just that millions upon millions of people will be able to possess it will keep Bill awake at night. So much the better if anti-competitive tricks are discovered to have been coded into it, whether that's admissible in court or not.

      In the words of Prostetnic Vogon Jeltz, "I've no sympathy at all..."

      ~Philly

  215. Re:Could it be a source of problems for Wine & Co. by smillie · · Score: 1
    What I mean: in six months or so, could Microsoft point the finger to Wine, or WVWare (was MsWordView) or OpenOffice, etc., and say they used their stolen intellectual property to improve compatiblity with Windows/Office, and thus the projects are to be suspended until clarity is made by a judging court?

    Unless they offer some proof then they would just be opening themselves up to a slander suit.

    --

    Dyslexics Untie!

  216. Could it be a source of problems for Wine & Co.? by ianezz · · Score: 1
    What I mean: in six months or so, could Microsoft point the finger to Wine, or WVWare (was MsWordView) or OpenOffice, etc., and say they used their stolen intellectual property to improve compatiblity with Windows/Office, and thus the projects are to be suspended until clarity is made by a judging court?

    I can't believe that Microsoft would ever admit it has been cracked and their sources were stolen unless there is some advantage in doing so. Do you?

  217. The NSA must be pissed by Anonymous Coward · · Score: 1

    ROFL!
    3 Months!

    Pretty soon script kiddies will be using the
    US-government-initiated M$ backdoors.
    It'll be chaos!

    Assuming, of course, this wasn't a Russian
    govt. espionage conspiracy.

  218. Immediate and long-term solutions. by Black+Parrot · · Score: 1

    > We're taking this very seriously and have both an immediate and long-term solution to protect our internal corporate network.

    Immediate: Unplug everything.

    Long-term: Upgrade to Unix or VMS.

    --
    Sheesh, evil *and* a jerk. -- Jade
  219. Re:Source shenannigans. by divec · · Score: 2
    Surely the source code couldn't be used for anything other than blackmail?

    And making samba work with the secret protocols used by PDCs, and doing the same for Wine, and ...
    --

    perl -e 'fork||print for split//,"hahahaha"'

  220. Re:Funny? Learn to moderate! by fredrik70 · · Score: 1

    WEll, if you know what you targeting, you bloody make sure that you try to get a trojan in that's binary compatible. That trojan didn't get there by chance.. Of course it was aplanned attack.
    If they knew MS ran *nix, then they would have used/build an *nix trojan....

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  221. Here's Windows source code by Molina+the+Bofh · · Score: 3

    Indeed, Windows source code leaked. Here's a fragment.

    voidmain()
    {
    while(!CRASHED)
    {
    display_windows_logo();
    display_copyright_message();
    display_bill_rules_message();
    do_nothing_loop();
    look_for_new_hardware();
    sleep(10);
    look_again_for_new_hardware();
    scandisk();
    if(detect_cache())
    disable_cache(); if(first_time_installation)
    {
    make_50_megabyte_swapfile();
    do_nothing_loop();
    totally_screw_up_HPFS_file_system();
    search_and_destroy_the_rest_of_OS/2();
    hang_system();
    }
    write_something(anything);
    display_copyright_message();
    do_nothing_loop();
    do_some_stuff();
    if(still_not_crashed)
    {
    display_copyright_message();
    do_nothing_loop();
    basically_run_windows_3.1();
    do_nothing_loop();
    do_nothing_loop();
    }
    }
    if(detect_cache())
    disable_cache_again();/*just to be sure*/

    if(fast_cpu())
    {
    set_wait_states(lots);
    set_mouse(speed,very_slow);
    set_mouse(action,jumpy);
    set_mouse(reaction,sometimes);
    }

    /*printf("WelcometoWindows3.11");&nb sp;*/
    /*printf("WelcometoWindows95");&nbsp ;*/
    printf("WelcometoWindows98");
    if(system_ok())
    crash(to_dos_prompt);
    else
    system_memory=open("a:\swp0001.swp",O_CR EATE);
    while(something)
    {
    sleep(5);
    get_user_input();
    sleep(5);
    act_on_user_input();
    sleep(5);
    }
    create_general_protection_fault();
    }

    --

    -
    Roses are #FF0000, Violets are #0000FF, find / -name '*base*' |xargs chown -R us && mv zig greatjustice
    1. Re:Here's Windows source code by Anders · · Score: 2

      Indeed, Windows source code leaked. Here's a fragment.

      Come on, that is getting to be a very old joke. It is about time that the syntax got correct.

      search_and_destroy_the_rest_of_OS/2();

      That would be search_and_destroy_the_rest_of_OS_2(); since a slash is clearly not allowed as part of a function name.

      basically_run_windows_3.1();

      Same deal, this time with a dot instead of a slash.

      system_memory = open("a:\swp0001.swp", O_CREATE);

      I do believe that the backslash would have to be escaped, making it "..a:\\swp...".

      There might be a few more syntax errors that I did not notice this time around. void main() is illegal C, but I believe Microsoft compilers accept it, so no need to correct that one.

      Making fun of Microsoft is great and all, but being binary only, Microsoft will have to make sure that Windows does at least compile. I think Linux is one of the only kernels that has a record of shipping with syntax errors ;-).
      --

    2. Re:Here's Windows source code by Anders · · Score: 1
      I'll open up N869 later and see if I'm wrong, but IIRC it's just not recommended because of the implementation specific behavior- which for most intents and purposes means you shouldn't use it ;)

      Well, a program that formats the hard disk would be a correct translation of the source void main() {}. So you are right, I would not recommend it :-).
      --

    3. Re:Here's Windows source code by bugg · · Score: 1
      Reading N869 here..

      5.1.2.2.1 (Program startup) says that main shall be defined with a return type of int.

      It doesn't bring up the issue again until 5.1.2.2.3 (Program termination) where it says if the return type of main is not compatible with int, the behavior is unspecified.

      Unspecified means one time it could format your harddrive, another time it could write you a check, and the behavior needs not be documented ;)

      --
      -bugg
    4. Re:Here's Windows source code by NetFu · · Score: 1

      You must be fun at parties. It's a JOKE. Correct syntax is an after-thought at best...

    5. Re:Here's Windows source code by Anders · · Score: 1

      You must be fun at parties. It's a JOKE. Correct syntax is an after-thought at best...

      Jokes have a tendency to get better if they are plausible. This one has had at least five years to evolve. I tend to bring new and/or good jokes to my parties, thank you. ;-)

      I did enjoy it the first time but am getting a bit bored by now. It seems like someone must post it every time Microsoft and source code is mentioned in the same sentence.
      --

  222. One more mark against proprietary software. by Brett+Viren · · Score: 2
    This developement is a bad thing considering how much mission critical stuff, for good or ill, depends on MS software. Just think of all those stock market, insurance company, bank, and government computers running MS software. Now think of all that data under the control of an outside untrusted agent. It's enough to cause a bank run!

    However, as bad as this is, it is good for free software as highlights the benefit of having access to the source and the drawback of proprietary software. It should be strongly stressed that this break in and possible insertion of back doors in literally millions of computers via MS software just underlines things we all already know: When the source is not open, the consumer has *no* way to prove its level of security.

    In the past MS and others have used the ``argument'' that having the source available to black hat hackers makes free / open source less secure. This (false) argument rested on the assumption that Uncle Bill kept MS source under lock and key. Today this argument is now double false.

    1. Re:One more mark against proprietary software. by gwizah · · Score: 1

      Yeah, but does VMS run GLquake?

      --

      There is no spork.
  223. Re:Open Sourcing Windows... by fredrik70 · · Score: 1

    Why would it kill of MS???? it was just the ME source and the Office (ok, that's quit big)?
    Ain't gonna hurt them more that all those pirate copied CDs, except for the humiliation...

    No more than a couple of geeks are willing of going through the process of compiling it b4 using it and they can't really release it big style as a official distro... hence, it wont do more harm than rouge CDs...
    And soon MS will be out with new (probably incompatible) versions...

    Trust me, I'm not a big MS fan but I don't see any need for stuff like this or the DOJ (little bit uncertain about that one) in order to beat them, they will go down anyway...because there will be better alternatives around than MS.. Mind you I don't think they disapear either, probably gonna be the major desktopOS for home users for quite a while... so what? not my problem, as long as I don't have to use it....

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  224. Re:The end of email-attachments? by image · · Score: 2

    This is obviously bait, but I'll bite.

    Do you have first-hand personal knowledge that Microsoft employees would do something "moronic" like downloading a trojan?

    As I've mentioned before, I used to be a program manager at Microsoft. As a whole, I found my co-workers there to be some of the most computer-literate, intelligent, and most capable people I've ever worked with (rivalled perhaps by my new company, Avacet). I can not think of a single one who was not educated about the dangers associated with blindly running executables that come in email.

    Also, Microsoft's network security was rather strong, especially considering that they have something like 25,000 employees worldwide and hundreds of thousands of machines to deal with.

    Seriously, feel free to critique MS technologies -- I do it myself all the time. But an uniformed criticism of everybody who works there is just inappropriate.

  225. Re:No Security on a Windows Network by cygnusx · · Score: 4
    There is no security on ANY network (though Windows is slightly more susceptible to cracks, that's all :-)). If cracking fails, there's always social engineering. You want security, go get a standalone computer. (and don't forget the Tempest shielding -- and the intrusion early-warning system and the leadlined safe.)

    Seriously, though... one of the more serious reasons that viruses/trojans spread more easily on Win32/Mac is "user imbecility/gullibility". And one reason (among many others!) why Linux/BSD was considered secure is that (1) users were much more sophisticated, and (2) the OS often compromised on security over 'ease-of-use'.

    Today, with Linux (not BSD though (thankfully!)) reaching more and more into the newbie space (I'm just waiting for the first "for-newbies" distro (oh, wait, Corel comes to mind)), how long before something like this happens on a Linux box? Remember, there are a lot of newbies out there running Linux (and also Win2k/NT, for that matter) on their PCs with exactly one user account -- "root"! (or "administrator".)

  226. Re:This is obvious but... by clyons · · Score: 2
    But actual hackers? No self-respecting hacker would ant or need to crib from Microsoft's notes. That would be like copying off the paper of the class idiot.

    Most class idiots aren't pulling down A's. Microsoft software is almost standard (as in, it's there and used)in business environment.

    As some people have pointed out, if someone makes the source to Microsoft software avaiable, a whole pandora's box could open:

    • 3rd party programmers may be able to increase the stability and speed of their software under Windows.
    • By examining the source to say, Windows ME, Windows 2000, etc, we may have proof that Microsoft does or doesn't code their OS's to break specific peices of software.
    • As others have pointed out, this berak in proves just how insecure NT is. However, if the source is published, it may be possible to make NT more secure.
    Of course, this makes it impossible for Microsoft to ignore obviouse problems with Outlook running vbs scripts from an e-mail.
    --

    --
    Intelligence is definitely a recessive trait.

  227. hilarious by [verse]Eskil · · Score: 1

    "But industry experts said that [a E-mail Trojan] is a relatively unsophisticated hacker's tool, which isn't likely to have duped Microsoft's systems on its own." duh. I find it hilarious. Eskil

  228. DNS entry *NOT* cracked by willie150 · · Score: 1
    This is a non issue. The DNS entries have NOT been cracked.

    First, you'll notice that it's just internic that has the problem.

    Next you'll notice that 'microsoft.com' is at the START of the host name... This is 'flaw' in the internic code. The way it searches entries is by searching the start of all hosts first, then hosts those that end with the search criteria.

    You could do the same and make any host appear like this.... just make a host that STARTS with microsoft.com and it's fine.

    So microsoft.com.suck.because.internic.is.fucked.myho st.com *would* work

    A real crack would be i.hate.microsoft.com becuase it's appening to the start of the host name.

    --
    Better to stay silent, and let people think you're an idiot than to open your mouth and remove all doubt
  229. Re:Open Sourcing Windows... by ksmeltzer · · Score: 1

    This may very well be true, but given the ferocity in which people hate Microsoft it is my opinion that the code would spread like wild fire. People would be willing to stand up for this fight due to the fact that this would surly destroys MS.


    I have a sneaky suspicion that these guys are going to release the code. They know that this one act could very well put them in the history books if they do.


    Disclaimer: I am not condoning their acts. Hacking is wrong and may cause cancer, but I sure would like to see if those secret hooks that Netscape et al. keep complaining about are real.



    Any one want to buy a T-shirt -Bill a month after the release of the Windows source code.

    --
    Crack |
  230. What people are worried about by marnanel · · Score: 2

    It seems from reading the news articles that the writers don't agree on what's worrying about this. Is it worrying because...

    1. ...the crackers could have modified Microsoft source code? No. Look, does anyone believe MS don't use version control and offsite backups?
    2. ...the code could be used in other people's products without permission? Perhaps, but not much-- that's what Easter eggs are there to get in the way of.
    3. ...everyone will read the code and discover defects? That's a good thing-- after an initial phase of instability, Microsoft will have to bring out patches. It's the opensource idea of the collective benefit of having millions of eyeballs read your source (what ESR calls "Linus's law".
    4. ...people might discover that the source is flaky in places, badly designed and so on? That might be more of an embarrassment to MS, but there's little opensource software which doesn't have flaky parts, is there? And better that people know about it than not.
    --
    GROGGS: alive and well and living in
    1. Re:What people are worried about by naasking · · Score: 1

      A few weeks later, 50% of the worlds PCs are wide open

      And they all upgrade to linux or BSD. :-)

      Hey, it could happen...

      -----
      "People who bite the hand that feeds them usually lick the boot that kicks them"

  231. Re:Open Sourcing Windows... by Cap'n+enigma · · Score: 1

    Microsoft would just buy SeaLand. Remember, BillG is the man who would be king, so that would fit nicely into his plans. Need Christmas shopping ideas Melinda dear?

  232. Re:I can tell you who stole it! by Shadowlion · · Score: 1

    Don't you know? He's still dangerous because he's learned how to manipulate his telpathic powers to hack into computer systems remotely. While he's off at a conference in St. Petersburg, he's using his ESP to compose email for Microsoft employees...

    Or, at least, that's the impression the parole board has of his computer abilities. Considering for a long time they wouldn't even let him give lectures about computers, they must believe he's figured out some new non-computer-based way of cracking.
    --

  233. Re:The "Truth" about who Microsoft really is by mystik · · Score: 1

    Those of you with just slashdot:

    [mystik@roast /home/mystik]$ whois microsoft.com
    [whois.crsnic.net]

    Whois Server Version 1.3

    Domain names in the .com, .net, and .org domains can now be registered
    with many different competing registrars. Go to http://www.internic.net
    for detailed information.

    MICROSOFT.COM.IS.SECRETLY.RUN.BY.ILLUMINATI.TERR ORISTS.NET
    MICROSOFT.COM.IS.RULED.BY.HACKERJACK.COM
    MICROSOFT.COM.INSPIRES.COPYCAT.WANNABE.SUBVERSIV ES.NET
    MICROSOFT.COM.HAS.NO.LINUXCLUE.COM
    MICROSOFT.COM

    To single out one record, look it up with "xxx", where xxx is one of the
    of the records displayed above. If the records are the same, look them up
    with "=xxx" to receive a full display for each record.

    >>> Last update of whois database: Thu, 26 Oct 2000 06:47:54 EDT <<<

    The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
    Registrars.

    [mystik@roast /home/mystik]$ whois aol.com
    [whois.crsnic.net]

    Whois Server Version 1.3

    Domain names in the .com, .net, and .org domains can now be registered
    with many different competing registrars. Go to http://www.internic.net
    for detailed information.

    AOL.COM.KCAUTOWEB.COM
    AOL.COM.IS.REGULARLY.HAX0RED.BY.INSIDE-AOL.COM
    AOL.COM.EATMYSHIT.ORG
    AOL.COM.AMSLIQUIDATORS.COM
    AOL.COM

    To single out one record, look it up with "xxx", where xxx is one of the
    of the records displayed above. If the records are the same, look them up
    with "=xxx" to receive a full display for each record.

    >>> Last update of whois database: Thu, 26 Oct 2000 06:47:54 EDT <<<

    The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and
    Registrars.

    --
    Why aren't you encrypting your e-mail?
  234. In other news: MS Switches Internal Servers to W2k by franksbiyatch · · Score: 1
    mod me down (-1 troll) I don't care. But you have to admit, M$ and apple take a lot of stick for not using their own products for all of their web serving needs.

    Bwahahaha

  235. Re:The end of email-attachments? by GodSpiral · · Score: 1

    More than likely, it was an excel or word macro virus. Most viruses are implemented in these tools.

  236. I can tell you who stole it! by drsoran · · Score: 1

    Which of our favorite uber-hackers has been released from prison within the last year that might want to rebel against the establishment by pulling off something so dasterdly? Could it be.. hmm.. oh I don't know.. maybe.. hmm.. THIS GUY? He DID steal source code in his previous days. ;-)

    1. Re:I can tell you who stole it! by Diskore · · Score: 1

      I seriously doubt it since he's not allowed to use a computer.

  237. Source and GPL by compwizrd · · Score: 1

    If the source for windows/office is really out there now, guess that'd prove once and for all if there's GPL/equiv code in there somewhere, if someone takes the time to look

  238. www.windows2000test.com finally hacked? ;-) by Jacco+de+Leeuw · · Score: 2
    So, was www.windows2000test.com (website now offline, mirror here) finally hacked? ;-)

    The award for the "hackme" LinuxPPC contest was that you could get the hardware, but I didn't know that with the www.windows2000test.com you would get the whole Windows source code! ;-)

    Jacco
    ---
    # cd /var/log

    --
    -------
    Warning: Slashdot may contain traces of nuts.
  239. picture at CNN?? by skilletlicker · · Score: 1

    What's the picture in the CNN story?
    Mice crawling over a keyboard?

    1. Re:picture at CNN?? by naasking · · Score: 1

      Looks like broken keys on the keyboard... They're popping out... I think...
      -----
      "People who bite the hand that feeds them usually lick the boot that kicks them"

  240. Re:Well, Ho Ho Ho by divec · · Score: 4
    This would have happened if they were using Linux, BSD or anything else.

    Well, y'd have to be running some program as stupid as Outlook, which runs arbitrary executable attachments, inside your supposedly "clean environment". I can't imagine a competent UNIX sysadmin would set things up this way.
    --

    perl -e 'fork||print for split//,"hahahaha"'

  241. That "H" Word is all too typical of the media... by Qwaniton · · Score: 1

    Haven't they learned yet? They keep using the word "hacker" and it makes me sick. At least /. has the brains to use the correct word. What would happen when OSI, ESR, or RMS does something extraordinary? Lemme guess...computer "genius". It seems more like "hacker" is the right word, because when you hack around with something, you play around with it, you tinker around with it, and you develop either new uses or new fixes for something broken. However, "cracking" makes me think of "cracking the code", which in turn makes me think of breaking code, breaking security, or solving a code you weren't supposed to know. Oh well.

    Definitions:
    XML: Leading the way to make the web a ebiz thing

  242. Office for Linux by dan14807 · · Score: 1

    So, does this mean that we are finally getting MS Office for Linux?

  243. Re:Sounds like a great idea! by omay · · Score: 1

    I will release the blueprints unless you pay me one milllllllllllion dollars...

    --
    Arm yourself with knowledge.
  244. Re:This isn't good. by PigleT · · Score: 2

    > I'm a Linux user in all, but if MS fall I want
    > them to fall the right way and no other

    Precisely, couldn't agree more. Let them hang themselves, rather than someone coming along assassinating them.
    (Mind you, if it can be shown to have been an M$ product that was cracked, I'd feel justified in saying they had hung themselves :)

    > It's Illegal all I have to say about it...

    Well, there might be that.
    I think it's more to the point that you'd be breaking the license agreement by so doing, myself; laws come and go and we've got a shed-load of stupid ones doing the rounds just to prove the point, but settle for "right" and "wrong" instead. If you're doing what the license at the top of the source file says you shouldn't, you're doing the Wrong Thing(TM).
    ~Tim
    --
    .|` Clouds cross the black moonlight,

    --
    ~Tim
    --
    .|` Clouds cross the black moonlight,
    Rushing on down to the circle of the turn
  245. MS doesn't want 3d party software to be compatible by Rolu · · Score: 1
    In the MSNBC story:

    "Other possible motives include economic espionage, though experts said only a rogue company might knowingly buy stolen software, using it either to improve its own products or make those products more compatible with Microsoft's best-selling operating systems."

    So, they admit you can make your software more compatible if you have the source code of Windows? What are they hiding in it?

  246. Re:Isn't it ironic? by Shadowlion · · Score: 1

    only a rogue company might knowingly buy stolen software, using it either to improve its own products .....

    If that's the case, maybe we need to forward a copy back to Microsoft. :)


    --

  247. Re:This could be the greatest thing to happen sinc by fredrik70 · · Score: 1

    doubt that many Open source people would be too interested in Windows source... Too big and nothing new in there anyway.. Look how hard it was for the mozilla people to get programmers to work in the mozilla code...

    COmapnies can't use it either, even if they found it. Might get caught and that would be too serious to be true...

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  248. Windows users should be scared by ash5g · · Score: 1

    Nevermind them releasing the source code, what if they modified it? If Microsoft can't detect a break in security for 3 months(or more), how is it going to detect changes in the source code? I wonder if they will go over the ME code? Or the SP1 for W2K?

    1. Re:Windows users should be scared by edgarde · · Score: 1
      One wouldn't have to alter code code on M$'s end to cause trouble. Windows isn't intended to be open source, and probably relies on security through obscurity. Just downloading and viewing the code probably means someone can write malicious hacks, or publish it elsewhere and let others do the work.

      For this reason alone I don't believe Microsoft faked the break in.
      __________

  249. Re:Initial breakin was via email trojan by jon_adair · · Score: 1

    Here's my question: If a user got bit by an attachment and it opened a port on his machine, how did the cracker connect to that machine? Shouldn't they be behind a firewall? Or did someone start a new email attachment trojan that does an outbound connection instead?

  250. some assumptions made here by twitter · · Score: 2
    1) People who know criminals are criminals. Sorry, wrong, we all know criminals and most of us want them in jail.

    2)The people who broke into MS are criminals. I'm not sure about this either. OK, they did break in and they did copy information, but we don't know much more than that.

    3)Judges are stupid. Nope, not always true. I doubt the fact that MS code was "stolen" will make all other programing illegal.

    4)MS code is worth copying. I don't need it, or Wine for that matter, do you?

    So, does this make MS open source?

    --

    Friends don't help friends install M$ junk.

  251. Good and Bad for Linux Community by mach-5 · · Score: 1

    OK, we all know this is bad for MS...but how does it effect the Linux community. I think it has both good and bad implications. Good in that maybe individuals and business will seek a more secure solution, thereby exploring Linux as a possibility. Bad in that it could give Linux bad press...any developments toward a more "windows like" OS could be blamed on using "stolen" code. That is, if they do indeed find that code was stolen. I'm sure their NT logs will be good enough to determine which files were acessed by who, and when.

  252. Standard Procedures by Thiarna · · Score: 1

    Nothings as simple as just find the changes. Whoever broke in had access to valid, active accounts, they would have no problems making changes to source code through the normal methods. Some poor sods are going to have to look through every source change for the last three months to find something 'suspicious'.

  253. Re:Going to affect everyone by MartinG · · Score: 1

    > open source can't compete on this level unless it incorporates itself under law

    What on earth does that mean? Can you (or anyone) please elaborate.

    --
    -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
  254. Taking this a little serious? by Cap'n+enigma · · Score: 1

    Don't recognize humor when you see it, do you?

  255. An orchestration to reinforce Anti-Hack Treaty? by ksan · · Score: 2

    The break seems too weak to believe. Doesn't it seem like orchestration with the government to reinforce the Anti-Hack Treaty ? Showing such case to europeans and other signaturers may be a good reason. You cannot forget that government of USA entered in the World War II alleging that a ship was sunken by german sub and it was not true.

  256. Re:Should I release the code? by fredrik70 · · Score: 2

    sourceforge purrhaps???

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  257. Not Suprising... Yet It Is by dywebmaster · · Score: 1

    I think Microsoft security should be praised. I mean, how long has Microsoft been high-ranking on the scales of hacker's hate list? It seems to me that they ran a tight ship that has finally been damaged. We'll see if it sinks or not... :-)

  258. I just think its rather ironic by paqez · · Score: 1
    Microsoft had to call in the FBI on some little VB programmers in Russia. I think this is some kind of wet dream or something. The other thing is that no one will ever let Microsoft live this down. As the article said, "This is a major embarassment for Microsoft." I agree very much so. For many large companies, there is a dark time and this is it for Microsoft. Being split up then releasing new software only to be hacked. Amazing.

    ~paqez

  259. Please don't recommend M$NBC links!!!! by xjimhb · · Score: 1

    A lot of M$NBC pages simply do not work on *ix boxes, including this one. I am on an AIX machine at work, I have had trouble with M$NBC pages at home on Linux too. You get down to the arrow that says "complete story" and a couple of box ads below that, then NOTHING!!!! View page source shows the HTML is there, it just won't display. There is some kind of link to some weird site that hangs it up.

    But then, what do we expect, it's **M$**NBC. (Not surprising that M$ would want to hide the story on THIS one.)

  260. Re:Banks don't use Microsoft by Salsaman · · Score: 3

    Actually quite a few banks use unix for their core systems. I worked at places which use RS/6000's running AIX.

  261. Re:Good thing Linux couldn't have this happen! by fredrik70 · · Score: 1

    check out bugtraq, dammit. Linux got quite a few holes as well.... you better be aware than be taken by suprise....
    install the fixes!

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  262. Re:Could it be a source of problems for Wine & Co. by divec · · Score: 2
    I can't believe that Microsoft would ever admit it has been cracked and their sources were stolen unless there is some advantage in doing so. Do you?

    If their shareholders found out they'd been keeping it secret, then the directors could go to jail.
    --

    perl -e 'fork||print for split//,"hahahaha"'

  263. hmm by dypstick · · Score: 1

    Maybe it's just a hoax, so MS has someone (other than themselves) to blame for all the bugs in their software. i can hear it now "no, your honor, we didn't knowingly hinder the performance of non-MS software, it must have been those hackers". You never know

  264. Oh, the WINE people must be pissed. by dmorin · · Score: 1

    What was up with the CNET article insinuating that projects like WINE would benefit from getting access to the stolen source code? That's all we need -- "Oh, well, the source was in the wild, therefore we can assume that you saw it, therefore WINE is illegal." Charming. Mind you, that whole "innocent until proven guilty" thing doesn't work when it's a big company just trying to cause grief for the little guy who has no money.

  265. Re:What would you do with the source? by GodSpiral · · Score: 1

    This has to be the biggest hack in history ??

    The most obvious application of the source, is using it as a cheat sheet in purported 'clean room' reverse engeneering efforts.

    Wine and starOffice submissions could coincidently increase.

    Serious legal heat would come down on any outright financial demands or commercial applications. Open source contributors could endure Federal investigations too.

  266. I hope they have the source code. by fjordboy · · Score: 1

    I hope that whoever did this does have the whole source code. This can only improve Windows...if the source gets out, there is no way it will dissappear again. (decss for example) everyone will release their own windows and it will make microsoft products a million times better. I bet it was an actual M$ employee who was told to do this and to make it look like it was someone else. This is the only way that M$ could release their source without having too much egg on their face.

    1. Re:I hope they have the source code. by biohazard99 · · Score: 1

      The forbidden fruit or Homer Simpson's soul donut ar5e also perfectly acceptable anologies

  267. Re:s/NT/stupidly trojan-enabled software/ by phil+reed · · Score: 1

    But if the operating system had a proper security structure, then a rampaging binary would not be able to cause any damage. Thus NT is at least partially to blame.


    ...phil

    --

    ...phil
    "For a list of the ways which technology has failed to improve our quality of life, press 3."
  268. Hopefully this is the end of "secret" API calls by Dr.+Spork · · Score: 1

    WIth the source code people will be able to see just how much of the eratic behavior of Windows is due to incompetence and how much is malice. Do they really have secret API calls that only Microsoft apps use? And isn't it amazing WINE announced this week it can suddenly run MS Office?

  269. Computer Security in Today's World by herwin · · Score: 1

    Automated computer security is vulnerable to bugs and social engineering. I wonder which was responsible here. Basically, you need a man in the loop to notice the funny patterns. What would be interesting would be a thorough search through the code for back doors, but I suspect that has been done by MS, at least for the ones not deliberately inserted. What would be scary is the perps doing a thorough search through the code for buffer overflow opportunities.

  270. Gates said "Blame Linux developers!" by billcopc · · Score: 3

    "the company couldn't say one way or the other whether source code had been stolen."

    In other news, a new build of Wine was released today boasting 100% emulation of the Windows environment at native speeds. When asked to comment, the dev team replied "We could tell you how we did it, but then we'd have to kill you".

    (note to morons : go check on freshmeat just in case!)

    --
    -Billco, Fnarg.com
  271. News Flash from Russia! by DrQu+xum · · Score: 4

    St. Petersburg (!AP) -- St. Petersburg police have found the bodies of three young computer experts. The three were found in one of the their apartments, lying on the floor in front of their 486 running SuSE Linux.
    "Our police experts stated that they were those who broke into Microsoft's servers and stole large amounts of code", says a police agent via translator. "Experts were able to tell from lengthy headers, pointless libraries, and pointers to nowhere-in-particular that this must be actual code for Windows 2000' successor."
    After a preliminary exam, forensic pathologists state that their deaths were all caused by ruptured lungs.
    "If I didn't know better, I would think that they would have died laughing", said the pathologist.
    One of the police experts who determined that the code was in fact Microsoft's also began laughing uncontrollably, and was rushed to a nearby hospital. He remains in serious condition and on heavy sedatives.

    --
    DrQu+xum: Proof that the lameness filter doesn't work.
    1. Re:News Flash from Russia! by DrQu+xum · · Score: 2

      Was ist das nurnstuck git und slotermeyer?

      "It was a fantastic success, over 500 Microsoft employees were released, and one that Bill Gates could not match."

      "Paul Allen has no nose"
      "How does he smell?"
      "Awful"

      --
      DrQu+xum: Proof that the lameness filter doesn't work.
  272. Banks don't use Microsoft by pantherace · · Score: 1

    Actually banks don't use Microsoft, or Unix. They use VMS, which according to what I have heard, kicks the crud out of everything else. VMS (from DEC) is posibly the best operating system, as it has everything Linux/Unix does, windows does, and I have never heard of a VMS box crashing or locking up.

    1. Re: Banks don't use Microsoft by Brett+Viren · · Score: 1
      You are possibly correct about banks using VMS, but walking into a bank I see a lot of Windows machines.

      As for VMS itself, have you ever used it? I used it the first year of grad school and I am very happy that my mind has purged everything it could about this OS. Uhg, what a pain in ass to use. When VMS can do simple things simply (like, cd, and rmdir) on VMS, then let's talk about it ``kicking the crud out of everything else''.

      VMS was the target of some of the first crackers. But now, since it is extreamly rare to see VMS used anymore it enjoys some security through obscurity: with out the scripts, there can be no script kiddies.

    2. Re:Banks don't use Microsoft by QuantumG · · Score: 1

      Every bank in .au runs on NT. I offered to port the EFTPOS software to unix (a very small part of the banking system that reads data from a slow ass modem, pumps it into a proprietory encryption device and dumps it back down the modem). It would have been a simple job and the distributor was willing. He went to get approval from the banks and was turned down. Why? They didn't trust unix security. They had bought the NT is secure line from Microsoft and weren't going back.

      --
      How we know is more important than what we know.
    3. Re:Banks don't use Microsoft by hughk · · Score: 1
      Most Banks are using stuff like Solaris, AIX and various IBM mainframe O/S. VMS gets used for some specialised stuff but isn't so popular anymore, despite its reliability.

      Sorry VMS does crash, but usually not very often. However, I have taken many machines down whilst testing stuff. Try debugging a piggy-back kernal AST for one thing!

      --
      See my journal, I write things there
    4. Re:Banks don't use Microsoft by gotw · · Score: 1

      No, that's just wrong! Infact NATWEST (National Westminster Bank for all you 'mericans) decided to port its entire system over NT so everything was ruinning the same system. What inspired this operation I don't know. But suffice to say - I have seen natwest ATM machines with a bluescreen (less amusing when I needed that money to get the train home). Would you control a machine with over £20000 cash in it with NT? I know I wouldn't! Why on earth would you need a huge sprawling multipurpose OS like windows (Or UNIX for that matter) to control a cash machine? Or an OS that is so well explored (and has so many) for vulnerabilities. A silly decision - but it's not my bank, so I won't end up paying for anything that might happen.

  273. Win2K Held for Ransom by MrValve · · Score: 1

    The CNBC report I saw mentioned "data ransom." Hmmm. "Give us a billion dollars or we fix the bugs in Windows 2000!"

  274. "...we invented Software Theft?" Hear me out... by American+AC+in+Paris · · Score: 4
    Y'know, it may not be in the Open Source community's best interests if the source code for MS' OSes gets stolen and released into the wild. Regardless of how sweet the irony looks from here, what kind of influence would it have on the Open Source movement if the first thing people associated with "Open Source" was "Oh, like those gyus who broke into Microsoft and stole their code, right?"

    Al Gore has the quote "I invented the Internet" fused to his name. It's been used time and again to demonstrate Gore's penchant for hyperbole, his untrustworthiness as a leader. Many of you probably already know, though, that Gore never actually said that he created the Internet, but rather that he was the key political figure in the early days of funding the Internet (still an inflated claim, but nowhere near as sensational as the other.) Does the fact that he never actually said what countless media outless attribute to him, often as a direct quote, make any difference whatsoever to his image and reputation? Nope. The media and his opponents decided to nail him to the wall with a hyperbole of their own, and with a bit of hard work and luck, it has become Truth. Truth, in that wonderful Orwellian fashion of 'if all official sources report the lie as the Truth, then the lie becomes the Truth, and the truth a lie.'

    It wouldn't matter how much you or I knew the truth, much like it doesn't matter that Al Gore never actually said that he invented the Internet. The Sheep and PHBs everywhere will swallow whetever pill they're given, and you can bet dollars to donuts that the story line wouldn't play out in favor of Open Source. If you think it's hard to convince your superiors to utilize an Open Source model now, try and imagine the brick wall you'd hit with your boss' brain automatically substituting "what happened to that stolen MS code" for "Open Source".

    For the moderators out there, I'm not saying that I think Open Source is theft, just so that's sufficiently clear. I'm just saying that it's worth considering the damage that the mass media PR monster could do to the Open Source movement, especially in light of the fact that most major media outlets are heavily invested in (and guided by) large, mean corporations. Think about it.

    --

    Obliteracy: Words with explosions

  275. Quote from MS: by scott1853 · · Score: 1

    "We are confident that the integrity of Microsoft source code remains secure." Dammit, I hope this isn't true.

  276. Re:Reichstag Fire by jgarry · · Score: 1
    If Richard Stallman were alive today, he'd be rolling around in his grave laughing his ass off.

    What?

    --
    Oracle and unix guy.
  277. Re:Well, Ho Ho Ho by twingo_gtx · · Score: 1

    "Well, y'd have to be running some program as stupid as Outlook, which runs arbitrary executable attachments, inside your supposedly "clean environment". I can't imagine a competent UNIX sysadmin would set things up this way.

    It doesn't matter what OS you're running or what Email proggy you use if the person is dumb enough to run random executables.

    It may take a little extra work to run it in *nix but if the guy really wants to look at that p0rn.exe they will find a way to run it.

    What they need to do is just find the employee that ran said stupid trojan and fire his ass, or do something worse like make him work on securing their network.

  278. Re:Should I release the code? by bruceg · · Score: 1

    MOD this up as funny :-)

  279. lame media by Cally · · Score: 3
    As always on the occasions when some tech story is big enough to make it into the mainstream media, we get to cringe at their awful attempts to explain things to the general public which they don't understand themselves. I woke up this morning to hear a BBC radio interviewer asking "so what are these source codes? are they like blueprints?"... discussion then proceeded to the topic of could the 'hackers' have planted "a virus or bug"[sic] in Windows? "Yes", said their expert, "and that could be included in every copy of Windows shipped from today!" ARRRRGGGHHHH.

    Perhaps this is a UK-only phenomena. Eventually the BBC etc might stop assuming that their audience thinks of computers as huge semi-sentient boxes with spinning tape drives and flashing lights that talk to their operators. Or that Microsoft are the best and only software source in the world. ("How could this happen to Microsoft of all companies?" asked the same interviewer.)

    And the use of "hacker"...
    /me goes up in a puff of unsmoke.

    --
    "None are more hopelessly enslaved than those who falsely believe they are free." -- Goethe
  280. yooo - hooo! by twitter · · Score: 2
    You and your peers may be very bright, but can you vouch for everyone? Don't you know anyone dumb enough to have a downloaded screen saver, pointer cartoon program, or any of these other stupid things people pass around and execute without worry? Come on.

    I work with bright people too who don't know any better. On an MS box that screen saver runs as root, but most don't know what that means. Someone who does not program and has never been exposed to *nix would not. They have been assured that their data is safe and trust that it is. That's the way it goes.

    MS employees might better know their software than people who listen to the MS sales department but, again, can you vouch for everyone? From Bill down to secretaries and janitors on the night shift? I don't think so.

    --

    Friends don't help friends install M$ junk.

  281. Whois using only a browser by marnanel · · Score: 1

    If all you want is to do whois:

    • the Internic have a fill-in form you can use; all the examples given above can be read this way. However, this only works with gTLDs.
    • If you want to look up (almost) any domain regardless of its TLD, try using BW Whois, which is clever and asks the correct NIC automatically. It fails on some odd cases like names in .ac.uk, though.
    --
    GROGGS: alive and well and living in
  282. Re:The end of email-attachments? by Pfhreakaz0id · · Score: 2

    WOW! Have you been on slashdot very long? It's very appropriate here.
    ---

  283. MS Latest Project ... by belbo · · Score: 1
    MS Open Networks ;-) tom

    --

    --

    --
    "Just believe everything I tell you, and it will all be very, very simple."

  284. Maybe this is what sunk the Kursk by gelfling · · Score: 1

    "Investigators today discovered that the Kursk was sunk by a failure in an experimental launch system that was using stolen MS source code." Records recovered from the sub included this fragment:

    "ok boot the launch system"
    "roger"
    "prime the payload"
    "roger"
    "uh we have a problem with the launch system"
    "shutdown payload initiate"
    "failure to shutdown payload, launch system will not start <garbled> blue screen <garbled>"
    "payload is arming"
    "Shut it down shut the <garbled> down"
    "Can't - it won't start or stop, it's frozen. The <garbled> shows blue screen"
    "Abort abort"
    "payload is armed with proximity fusing"
    "holy mother of God, shut the <garbled> down"
    "complete lockout, no response, launch system failure, reboot reboot reb"

    Loud blast noise followed by sounds of bulkhead failure. Air escape, bubbles, rumbling. Silence.
    "

    1. Re:Maybe this is what sunk the Kursk by Hrunting · · Score: 4

      I've seen some pretty dumb things on Slashdot and I've seen some pretty offensive things on Slashdot, but never a post like this.

      This ranks up there with the jokes that came out after the Challenger accident and after Oklahoma City. The Kursk was a tragedy. It may not seem that way to an American, but it shattered the emotions of the Russian people. To further imply that Microsoft had any part in that tragedy is simply childish.

      I've always considered the majority of Slashdot readers to be brats, but this goes to show that whatever Microsoft may do to fight the open-source movement, they'll probably win. Why? Because for the most part, it's people like you who make up and support that movement, people lacking any amount of maturity and decency, and for movements to succeed, they must at least be honorable in the face of their enemy.

      Just sickening. Whoever moderated this up for being funny should be shot. Mark me down for flamebait or what have you, but the fact remains, many open-source zealots and programmers are simply brats.

    2. Re:Maybe this is what sunk the Kursk by hoofie · · Score: 1

      Very sick and unfunny. At least 20 or so people died a slow and horrible death on that sub.

    3. Re:Maybe this is what sunk the Kursk by hughk · · Score: 1
      Sick yes, but very, very sad - but the current theory going around miltary circles is that the cruiser "Peter the Great" fired a missle either at the wrong time or it malfunctioned. The submarine was hit (there was inward buckling of the hull) and one or more torpedoes exploded.

      They wouldn't have been running Win2K. However someone in St. Petersburg, Russia knows a lot about this incident.

      --
      See my journal, I write things there
    4. Re:Maybe this is what sunk the Kursk by radja · · Score: 2

      people will ALWAYS find humour in what hits close to home. There are jokes about racism, terrorism, death, war, destruction, ships sinking, murders.. anything. humour is a normal mechanism for human beings to cope with anything serious. you don't have to like it, you don't have to do it. I admit to making racist jokes, lesbian jokes, homosexual jokes.. just about anything. that doesn't necessarily mean that I am a racist, womanhating homophobe though...I have friends in all those classes..

      //rdj

      --

      No one can understand the truth until he drinks of coffee's frothy goodness.
      --Sheikh Abd-Al-Kadir, 1587
  285. That's absolutely crazy thinking. by drsoran · · Score: 2

    Now that you mention it though.. it is kind of odd that only a couple of days ago we read that Wine can now run Microsoft Word 2000 and Excel 2000. Coincidence? :-)

    1. Re:That's absolutely crazy thinking. by logicTrAp · · Score: 2

      Wine's running Diablo II perfectly as well, without any Windows DLLs for me whatsoever. I tend to think that looking at the history of Wine it would be hard for Microsoft to be able to claim any sort of collusion. It's really a tribute to the Wine team that they've been plugging at it for 5 years and it's now bearing some real fruit.

  286. Re:This is obvious but... by twingo_gtx · · Score: 1

    "Hackers huh? Hopefully they'll fix some bugs before they give it back. "

    Hopefully they'll start with the bug in Outlook that allows these stupid trojans to get easily into their network.

  287. Re:The "Truth" about who Microsoft really is by stu_coates · · Score: 1

    whois netscape.com is also quite interesting! ;-)

  288. Re:This could be VERY bad by Our+Man+In+Redmond · · Score: 2

    I'm certain a group of 31337 h4x0r2 in St. Petersburg will be deterred by an American law against breaking into computers.

    I know, I know, you can't expect to make sense of laws related to computers or efforts by the clue-challenged to pass them.
    --

    --
    Someone you trust is one of us.
  289. Re:The "Truth" about who Microsoft really is by mrfiddlehead · · Score: 1
    Or if you're stuck with Windoze snarf a copy of Sam Spade and you'll be able to do nslookup, whois, traceroute, ping, dig, finger, ...

    No more excuses.

    --
    :wq
  290. Look at who wants government involvment now! by Duchamp · · Score: 1

    What a hoot.

  291. Proof that MS doesn't learn. by Bad_CRC · · Score: 1
    Microsoft's email network was taken down by the "I love you" virus.

    It's amazing that they hadn't put in security measures to keep this type of attack from happening again.

    Or is it just not possible to lock down windows, due to it's lack of security? If the manufacturer can't do it in their own buildings... what chance has a normal person got?

    ________

    1. Re:Proof that MS doesn't learn. by Stonehand · · Score: 1

      Well, you can't lock down users or upgrade their firmware.

      And they can't really prevent users from saving attachments to disk and running them manually without the equivalents of noexec and read-only, *and* discouraging people from logging in as Adminstrator or giving their regular UID Administrator privs. And if they did THAT, I suspect there would be mucho unhappiness, as folks aren't used to that.

      And they don't really provide a chrooted sandbox in which to test executables.

      I'm not sure what they CAN do here without causing a hue and cry.

      --
      Only the dead have seen the end of war.
  292. Well Regarded Security? by juliao · · Score: 1
    Computer security at Microsoft's campus generally was well-regarded until this latest incident.
    "Well regarded" just because no one had broken in yet? If Microsoft had been inclined to impose decent security standards on their own private network, they would have to either:
    1. Change most of their software products to make them more secure
    2. Hire as many security engineers as they have programmers so that they could endlessly "securify" the machines
    3. Forbid the use of insecure software in their internal network (and starting running Solaris on servers and Macs on desktops, probably... or Linux on both)

    Windows is just too weak. Bad design principles. Too much code. Too bloated. Too obscure.
    Well, maybe the guys that took the source code will change this last part...

  293. Re: And listen to this... (NYT) by lucidvein · · Score: 1
    This from the New York Times

    "Other possible motives include economic espionage, though experts said only a rogue company might knowingly buy stolen software, using it either to improve its own products or make those products more compatible with Microsoft's best-selling operating systems."


    Only rogue companies would use stolen software?
    While it's likely that companies with integrity would turn in any offers of the stolen software, I wouldn't limit the possibility that many not-as-financially-successful businesses would seriously consider it. Now that Communist Red China is no longer a rogue state, is the media trying to insinuate that the real threat here is third world capitalism?

    *the Communist Red China crack came from a Republican ad run this weekend stating that Gore sold out American security for campaign contributions.
    --

    "I have a cunning plan..."

  294. Re:This explains the Kursk disaster by k3rn3lH4X0r · · Score: 1

    Ok, now THIS Kursk story is *funny*

  295. Workaround... by tdsanchez · · Score: 1

    I tried this running Netscape 4.7 on a Solaris box, and intially, I couldn't see the 'complete story' either. By chance, I went back a page (using the back button) and then forwarded (using the forward button) and could then see the rest of the story.

    I'd venture a guess that this is a *nix Netscape rendering bug if indeed you are using Netscape.

    -t

  296. Re:Childish attacks unnecessary by johnnyb · · Score: 3

    You really need to think before posting. Most of the security compromises you list for Linux are _local_ compromises. That means, you must already have a shell to do them. If you have a shell on Windows, getting root is even easier, unless you have all of the security updates. When NT4 was first released, almost every kernel call did not do proper checking, and you could comprimise security with _any_ kernel call. As far as _network_ security goes, securing Linux is just like securing any other OS - you check the network programs. The way you secure the console is by simply removing unwanted SUID programs. With Windows, you can assume that if someone is at the console or telnetted in (which you _can_ do with the proper software), you should assume they have administrator priviledges. As far as security advisories, most Linux security advisories come from the people developing the code, not from being cracked. This means you get to secure your machine _before_ script kiddies get their hands on things. With NT, the advisories are normally based on someone actually being cracked. Please think before posting, and make sure you understand the topic at hand.

    I'm not even trying to say "Linux is better than Windows" with this post. I'm just pointing out that your arguments are comparing apples to oranges (network security to local machine security, and published exploits to theoretical problems).

  297. Re:Open Sourcing Windows... by StarFace · · Score: 2

    Not even close. We figured it out, if you take all 60 million lines of code and shrink it small enough to print onto (let's be generous) 15 feet of cloth, the font size would be about 13 atoms tall. Given the nature of cloth, hardly any of the "paint" would actually end up on the threads. Most would fall through the holes. You would in fact get a tshirt that was kinda stiff, and solid white.

    --
    V
  298. Re:Open source.. assisted? (well, gpl perhaps..) by hrieke · · Score: 1

    In the court of law (in the US), even illegally obtained evidence can be produced and considered as long as the parties prove that they didn't obtain themselfs.
    For example, if a criminal breaks into a house and steals a book which details the crimes of the victim, the police can (and do) act on it.

    --
    III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...
  299. Re:Open Sourcing Windows... by Zan+Thrax · · Score: 1

    OK, how bout one of those nifty stadium tricks with giant index cards for everyone? Surely there's enough space on a setup like that?

    Or, find particularly amusingly badly written functions or calls or objects or whatever (I'm no C++ guru, I can barely kludge together a complicated struct) and use those for the shirts...

    --

    Intolerant people should be shot.
  300. Re:Security by Obscurity by JM_the_Great · · Score: 1

    Well, yes, technically, the source code in Outlook, but I meant more the whole way they designed it, I'll pick on Windows for bad programming and source code, in Outlook they _meant_ to put this "feature" in, so I can't really call it a mistake in the source code, but a mistake in the design.


    Grades, Social Life, Sleep....Pick Two.

    --

    --Justin Mitchell
    "2nd Place is a fancy word for losing" --Bender (Futurama)
  301. Isn't it ironic? by Manes · · Score: 1

    According to the journal, it looks like they got
    cracked with the same methods ILOVEYOU used.

    Is it just me, or isn't this a tad ironic?
    :-)

    1. Re:Isn't it ironic? by s390 · · Score: 1

      Russia has _mostly_ rogue software coders. Their "companies" are mostly small, often controlled by criminals (freelance, mafia, or well connected). That whole region has been a barely-functioning kleptocracy for a while. Hopeful signs are the election of Putin in Russia (he's a standup guy) and rejection of Milosovec in Serbia (a mini Stalin, war crimes instigator, _very_ bad news).

      However, one can hope that rehabilitation of the Russian political / legal / socioeconomic systems won't happen fast enough to prevent the starving programmers from beating Microsoft with Whistler! Few things could be sweeter than seeing Microsoft code stolen due to their own security lapses, and then improved, nearly given away on a mass scale.

      Expect to see a Russian version of Whistler that is more-stable / works-better than Microsoft's. It should go over big in the third-world (China, Southeast Asia, Middle East, Africa), especially if source is available (China is very paranoid, but it also tells the West to go suck eggs about legal niceties involving intellectual property, only except for a few cosmetic raids sometimes).

      Short story: The owner/coder for a nice piece of software I use once shared some code with _one_ Russian programmer who was supposed to do work on it; he stole the code, then boldly proceeded to sell it under another title. The author still hasn't been able to shut it down (Russian legal process, you must be kidding!) and still has to endure the continued website postings announcing the usurper's updates to _his_ code, sold by pirate Russians!

      I can't wait to download my low-cost copies of Russian versions of Word/Excel/Powerpoint 2001. They'll probably work better than Microsoft's official point-releases, at one-tenth the cost. With luck, they'll include source, maybe they'll have Linux compatible binaries: bye, bye, Microsoft. (But then, we get a serious stock market correction - Microsoft has defrauded its investors and employees for so long that fixing its lower value will be genuinely painful here - www.billparish.com for details).

      What might be _really_ ironic would be Russia's lack of justice beating the US courts to justice. Don't break up Microsoft, just steal their code! (Then improve it, port Linux/Mac, a lovely road.)

    2. Re:Isn't it ironic? by radja · · Score: 1


      ----------- 8 ------------ 8 ------------------
      Other possible motives include economic espionage, though experts said only a rogue company might knowingly buy stolen software, using it either to improve its own products .....
      ----------- 8 ---snip----- 8 ------------------

      and what about that one? ;)

      //rdj

      --

      No one can understand the truth until he drinks of coffee's frothy goodness.
      --Sheikh Abd-Al-Kadir, 1587
    3. Re:Isn't it ironic? by agentZ · · Score: 1

      You may accuse me of wearing a tin-foil hat on this one, but China rejected purchasing Windoze a while back because they were afraid the American government had planted bugs in the source...

  302. If I were Ballmer I'd... by hey! · · Score: 3

    order the biggest freakin' code review in history.

    If I were a hostile cracker, I wouldn't go the "data hostage" route -- to risky. The police will follow the money.

    Instead, posing as an engineer, I'd slip a few buffer overrun vulnerabilities, just where I could use it. Knowing the cruftiness of MS operating systems I'd have my own private back door into any system shipped with Windows for years to come.

    Give a man a fish, and he'll eat for a day. Hand a fisherman a crate of hand grenades and he'll catch all the fish in the river.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    1. Re:If I were Ballmer I'd... by QuantumG · · Score: 1

      bah.. like you'd need to install your own backdoors.. just browse the source for five minutes and look for the comments that say /*** THIS COULD BE A SECURITY BUG, FIX THIS!!! ***/

      --
      How we know is more important than what we know.
  303. Childish attacks unnecessary by Carnage4Life · · Score: 4

    I'd expected more mature responses to MSFT being hacked than childish attacks either blaming NT like the above post or claiming that MSFT being hacked is good for Open Source like others I've seen. Frankly *nix and Windows are roughly equivalent in default security (except for OpenBSD) and only through the machinations of a good sys admin is either OS properly secured.

    For those that believe *nix is somehow more inherrently secure than Windows here are a few sources that may refute that claim The major security issues in Windows are Outlook (disable preview pane, be careful with attachments) and Internet Explorer (disable Javascript). Doing that and using a firewall like ZoneAlarm is most of the securing that a typical Windows box needs. On the other hand due to the use of insecure C libraries (str* functions, *scanf functions, etc) most of the services that are enabled by default in a typical Linux install are insecure (especially RedHat the primary consumer Linux OS in the U.S.). Take a quick look at security sites like Attrition.org, CERT, SANS, rootshell, SecurityFocus, etc and check the results. Defacements of Linux sites has been rising at a steady rate and now there are more defacements of Linux sites than NT sites. CERT regularly has more Linux and Unix security advisories than for Windows. The SANS (System Administration, Networking, and Security) Institute top ten list of security holes has more entries for *nix than Windows. A quick search of the terms "linux" and "windows" on Rootshell's seearch engine come up with 84 downloadable exploits for Linux versus 39 for Windows.

    The above post is not intended to be flamebait (I run Win2K but plan to reinstall Linux on my second machine so I am a Linux user) but as a counterpoint to the above post which was rated +5 when I replied to it.



    Second Law of Blissful Ignorance

    1. Re:Childish attacks unnecessary by jbarnett · · Score: 4


      The point is this.

      1) Microsoft has complete unrestricted access to there own source

      2) Microsoft is a billion dollar company and ALOT (atleast in their eyes) is at stake

      3) They have enough money to higher decent security officers

      4) These well-paid security officers should of secured the system and network

      5) With people hired for the sole purpose of securing the network, the network should be somewhat more secure, no matter what OS they are running.

      6) Why are there developemnt/ source code computer even avaiable on the Internet? Anyone every hear of firewall or internal network? Anyone think about just upluging the T1 from the internal network? Anyone think about requiring the security admins to read "Intro to network security"??

      I am sorry to say, but this crack looks "so seventh grade or something"

      7) Should Microsoft employees know how to use what software they are required to for there job (ie. outlook). Shouldn't of Microsoft employees be educated about basic security?

      8) Where is any monitoring? "Hey Network Admin Bob, some ip in russian has been downloading megs of stuff from one of our internal machines? Is that normal?"

      Microsoft views the security of there source code as "high value", the see the closedness of their source as their cash cow, yet they let someone 0wnZ them so easy.

      I am not saying NT or W2k is more secure than Unix, etc, that is a broad and misleading statement. I am not saying Unix is more secure than NT, that is also to broad and misleading.

      What I am saying is that any decent OS (this includes NT, W2K) should of not even had the chance to be owned like this. If there network was setup right, you could have had the most insecure OS running with default uid/pass for admin access and should not be spolitable like this (atleast from the internet).

      It boggles the mind.

      It not even like a 31337 crack, it is "hey I downloaded all this programs off the internet, you want to 0wnZ M$?"

      The problem isn't with what OS it is running, the problem is that 1) the network admins no nothing about security 2) the system admins no nothing about security 3) the users no nothing about secuirty.

      Even if they where running a "Ultra Secure" *cough*OpenBSD*cough* OS, if they hook their "important machines with highly classified information" up the the internet, they are just ASKING for trouble...

      And someone please explain to me why the SYSTEM ADMIN was checking his email with the ADMIN account on a SECURE MACHINE. Then running an unknown program as ADMIN user!

      That is like a unix admin, going to a secure unix box, logging in as root, checking his email with root, then running an unknown program as root, this mind boggles.

      Do they people in redmond even know how to use there own dam OS? Maybe they should require all employees to get MSCE or something...


      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    2. Re:Childish attacks unnecessary by Carnage4Life · · Score: 2

      You really need to think before posting. Most of the security compromises you list for Linux are _local_ compromises. That means, you must already have a shell to do them.

      And your point? The Microsoft crack was most likely a Trojan (i.e. local compromise) as a opposed to deliberate network hack into the system. Secondly you are incorrect in stating that I listed mainly local compromises, there a liberal smattering of both types of compromises in my links (defaced web page count, SANS top ten list, rootshell exploits, etc).

      Frankly resorting to personal attacks when it is clear that you didn't bother checking the links in my post, shows who indeed is the person who doesn't think before posting.

      Second Law of Blissful Ignorance

    3. Re:Childish attacks unnecessary by jbarnett · · Score: 1


      WTF? God dam grammer whore.

      "read a book once in a while, then post. "

      *AHEM*

      It is "Read a book...". If your posts aren't prefect, why do you flame me on mine? Fuck you.


      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    4. Re:Childish attacks unnecessary by jbarnett · · Score: 1


      i bet it was a secretary

      Why isn't the programmers development network complete seprate from the secretary's? Would the secretary be considered in the same "security class" as the lead developers of Windows ME?


      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    5. Re:Childish attacks unnecessary by Linux_ho · · Score: 1

      Keep in mind that it's a lot easier to write an exploit when you have the source code available. Up until now, that was the only security advantage Windows had over Linux.

      Looking at this story, its possible Windows can't claim that advantage anymore.

      --
      include $sig;
      1;
    6. Re:Childish attacks unnecessary by Znork · · Score: 2

      As unreliable as the defacement statistics are, you should actually look at the page. NT has a good solid upward trend again, and linux sinking.

      Factor in the number of sites running either and it's not very pretty statistic for NT.

    7. Re:Childish attacks unnecessary by Hard_Code · · Score: 1

      They have enough money to higher decent security officers

      Maybe if they would stop getting their security officers high this sort of thing wouldn't happen.

      --

      It's 10 PM. Do you know if you're un-American?
  304. Jobs did it! by sensate_mass · · Score: 1
    Heh. Yeah, Steve wanted to get his hands on some of those cool Windows features he's been dying to put into MacOS.

    --
    --- Submission is feudal.
  305. Bad Day for Bill by Chitlenz · · Score: 4

    AVAILABLE - Slightly frazzled security Admin seeks Immediate Position after undertaking imposssible task at unnamed Redmond, WA. employer. Canned due to circumstances beyond control. Will take any offer not relating to windows. Added Plus - Able to interpret arcane source code for popular and possible unintentially Open Source Operating System (you hear that Larry E.?). Used to long hours and sleepless nights, anything's a change for the better. Looking for stock options (in a company that's still gonna be worth something in a month).

    --
    Imagination is the silver lining of Intelligence.
  306. corporate suicide? by dirtmerchant · · Score: 1

    From the CNN link: "it would be tantamount to suicide" for competitors to exploit illegally obtained information about Microsoft code for their commercial benefit.
    Now is this a legal threat or just the fact that even Microsofties realize their company has no economic future?

    -----BEGIN GEEK CODE BLOCK-----
    v.3.12
    GCS d-(--) s+: a-- C+++$>++++$$ UL++$>++++$$ P+>++++$ L++>++++$ E--- W++$>++

  307. "Why they stayed for 3 months?" explained by Boomer3000 · · Score: 2

    Apparently the hackers were looking for some good or brilliant source code, and they weren't able to find it. This explain also why Microsoft persons are sure that source code wasn't compromised: "It's impossible to make it worse than that" one spokeperson said.

  308. Re:Open Sourcing Windows... by Basje · · Score: 1

    This entirely unlike DeCSS. DeCSS isn't illegal. It's still in court of the circumvetion of CSS is illegal. The sourcecode to windows is stolen property (intellectual property by law, whether you acknowledge such a thing or not). So hosting the source code is fencing stolen property. And fencing _is_ illegal in most countries.

    ----------------------------------------------

    --
    the pun is mightier than the sword
  309. Russians by Soruk · · Score: 1
    Makes you wonder what the Russians want with the Whistler source code...

    ..perhaps to upgrade the ships' computers on their nuclear submarine fleet?

    --
    -- Soruk
  310. Re:Post removed with second article by fredrik70 · · Score: 1

    it's not???
    *world falling apart*

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  311. GNU/Linux in Windows? by SpringRevolt · · Score: 1

    If the source code ever becomes available... we would at last be able to resolve the issue that we have been pondering for years... "How much GNU and Linux is there in Windows?".

  312. Security 101 (or rather, RFC 2196) by juliao · · Score: 2
    While there is no evidence that any changes have been made to the codes, and experts characterized such a risk as remote
    Makes you wonder.
    Weren't those same experts characterizing the risk that someone broke into their network as "remote", too?

    Evryone knows the standard procedure for security break-ins. Isolate all machines, compare all binaries to archived copies, etc, etc.

    RFC 2196, now does that ring a bell?

    But of course not, it's going to be "bad hackers versus oh-so-nice Microsoft" all over again. Microsoft's software and OS design lacks in security, but guess what, it's going to be someone else's fault...

  313. Security by Obscurity by EisPick · · Score: 1

    This sort of kiss MIRCOS~1's argument that Windows's security features are more robust than Unices'/Linux's because the source code is proprietary.

    1. Re:Security by Obscurity by JM_the_Great · · Score: 1

      Erm, it has nothing to do with source code, but the avreage intellegence of the users :) (oh, yeah, and some stupid design things in Outlook too...)

      Grades, Social Life, Sleep....Pick Two.

      --

      --Justin Mitchell
      "2nd Place is a fancy word for losing" --Bender (Futurama)
  314. Pulleth The Other One, it hath Bells On by henley · · Score: 3

    Any project started within the last 3 months may be potentially vulnerable to a legal Denial of Service attack, yes.

    I refuse, however, to believe that there's a Court of Law in the world that's bone-headed enough to believe that project X, running for Y years and fully documented in that time as an open project (cf WINE), has benefited from the unrelated, unadvertised and recent breaking out of MS source code.

    Come on.. Doom-saying is all fun and games, but please do try and stay within the bounds of reality...

    --

    --
    I'd rather have a bottle in front of me than a frontal lobotomy
  315. Sealand by acb · · Score: 2

    All MS would have to do is persuade the government that it is in the interests of the US New Economy and the perpetuation of the Long Boom to drop a few laser-guided fuel-air explosives on Sealand.

    1. Re:Sealand by mattdm · · Score: 1
      Right inside UK waters. Yes, I'm sure that would go over well.

      --

    2. Re:Sealand by Chalst · · Score: 2

      The British government has just the right combination of spinelessness
      and crawling to the US to let it pass.

  316. Reichstag Fire by Deskpoet · · Score: 5

    This was PRECISELY my first thought when I read these pieces: this is a staged event for some reason as yet to be revealed.

    Of course, as a reluctant user of NT, I *know* it's vulnerable, and the fact this occured doesn't surprise me at all. What IS surprising is we haven't heard more of this coming out of Redmond; it can't be the first time.

    I don't think the possibility that this is a way for Microsoft to reign in the Open Source movement is paranoid AT ALL. With M$ having its market share threatened by Open Source stuff, why not create an excuse that the people releasing it are ripping off internal code stolen from M$. Indeed, it makes perfect sense, and it wouldn't surprise me if the lawsuits start flying within 6 months.

    I worked at a place where we had REAL break-ins, and the last thing you want to tell your customers is that you've been hacked. The fact that M$ is being so forthright about this--in direct contradiction to the way they typically stonewall against any less-than-flattering news--points to an entirely different motivation than just being honest.

    Remember, the people that report these stories have extensive relationships with M$. There can be no doubt that they are spinning this is such a way as to ultimately benefit M$, or any initiative that M$ may find to its liking.

    By the wall, Randall is *NOT* a criminal. Yes, he was convicted, but that means about as much as the stain on Monica's dress. Judge for yourself; go here for more information.

    --
    "The more corrupt the state, the more numerous the laws."--Tacitus, The Histories
    1. Re:Reichstag Fire by sparty · · Score: 1

      Yes, but most likely, the same is the case on a WinNT network..I find it hard to believe that MS wouldn't have setup security on their servers (which is presumably where the source code would reside) so that anyone could read any files...only developers who needed source access would have such access. And the same would be true on a *nix system...if the person is working on the source, then presumably they'd have access to it and therefore it would be "personal" files ot the extent that a trojan under their UID could read it and email it to Russia or South Africa or Hackensack or wherever.

    2. Re:Reichstag Fire by netstorm2000 · · Score: 1
      Of course, as a reluctant user of NT, I *know* it's vulnerable, and the fact this occured doesn't surprise me at all. What IS surprising is we haven't heard more of this coming out of Redmond; it can't be the first time.

      Did you miss something? The article SPECIFICALLY said it was accomplisghed via a Trojan, making it NOT NT's fault, but the users'.

      --
      --matt Cowger
    3. Re:Reichstag Fire by mattdm · · Score: 2
      Users never learn. Operating systems/environments and apps (this goes for Linux too) need to take some responsibility for making sure this never happens.

      --

    4. Re:Reichstag Fire by medicthree · · Score: 1

      Just so you know, this type of crap is why no one takes you open source kids seriously. Yeah, sure, a huge multinational corporation with huge market capitalization would fake an infiltration and get the FBI involved in helping them solve the "crime." Get real, idiot.

    5. Re:Reichstag Fire by Hard_Code · · Score: 2

      Microsoft lives and dies by its stock value. I don't think there is any chance they'd jeopardize that on purpose.

      --

      It's 10 PM. Do you know if you're un-American?
    6. Re:Reichstag Fire by jbarnett · · Score: 1


      Um RMS isn't dead.

      Uh um and if he was alive, why would he be rolling around in his grave laughing his ass off?

      RMS is alive, I don't think he owns a grave. If he did, I don't see why he would roll around in it laughing.


      --

      "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
    7. Re:Reichstag Fire by Deskpoet · · Score: 1

      Yes, I read the article, and it did not refer to NT; you're correct.

      However, it definitely referred to Outlook, which generally runs on NT or WinXX, and therein lies the problem.

      Now, you can claim that users are at fault for events like these, but isn't part of software engineering and design to make software that is not only user friendly, but protects users from making errors that would comprimise their systems?

      Case in point: OpenBSD. It takes a MINIMALIST approach in its design philosophy so that it prevents a luser's accidental comprimising of the system/network. Yes, you can make it vulnerable, BUT NOT BY JUST USING THE SOFTWARE; it takes a conscious effort on the user's part to make it open.

      Outlook, and the system it rests on top of, does NOT have this design philosophy. Quite the contrary, as "market driven" products, issues such system security and program integrity take a backseat to "interface usability" and "feature set".

      The enduser should only be blamed on the failed integrity of their system to the degree that they actively seek to comprimise it. And since this "attack" wasn't a StickyNote Exploit, I think it's perfectly fare to dis the system that created the situation.

      --
      "The more corrupt the state, the more numerous the laws."--Tacitus, The Histories
    8. Re:Reichstag Fire by jafac · · Score: 2

      It is, and always has been in Microsoft's best interests (as far back as Bill Gates' Micro-soft open letter to the hobbyist community regarding "software piracy") to raise public hysteria against hacking and piracy to a fever pitch, in order to justify laws like UTICA and DMCA, which put all the cards in their hands, and out of our hands.

      We stand at the brink of the beginning of a dark, dark, age. I don't believe there is anything that can be done about it. Those of us who want to preserve our freedom are going to necessarily have to become outlaws, and perhaps fight a guerilla war, or possibly fight from inside. (the stories I've read about the whole Intel/Rambus fiasco, and internal rebellion have kind of made me feel less pessimistic).

      At least crypto is free. We have that small victory. But everything else seems to be going to hell.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  317. Just wondering... by noims · · Score: 1

    I wonder if they've sent in any bug fixes yet.

    --
    This is not the greatest sig in the world. This is just a tribute.
  318. A little advice... by Siqnal+11 · · Score: 1
    I just looked through your recent comments, and I have some advice. If you're going to post such nonsense, you need to develop thicker skin, like me. Just admit you're a troll & live with the consequences. It's not a bad lifestyle. You're almost there, anyway, because you post from your account, instead of as an AC.

    --

    --

    --
    You are a fucking moron.
    1. Re:A little advice... by linuxgod · · Score: 1

      As you can see, the anonymous troll talks to himself also. Its kinda funny.


      Ignore the Anonymous Pissant trolls !!!

    2. Re:A little advice... by linuxgod · · Score: 1

      um, no. And i pitty the phool who does....


      Ignore the Anonymous Pissant trolls !!!

  319. Selling... by cluening · · Score: 1

    I wonder how long now until we see the source to Windows selling on Ebay...

    "The source to a popular operating system - this is a real fixer-upper! Kind of worked last time I used it, buy as-is. Will pay shipping. No reserve!"

    --
    Posted from the wireless couch.
  320. Redhat Cracked by ahaile · · Score: 5
    Durham, Oct 27 -- The linux world is in a tumult today after a report claiming hackers broke into the corporate network of industry leader Redhat. The report, published on the internet by a pseudonymous "BG", purports that "lots and lots" of hackers outside the Durham-based organization have been "stealing intellectual property" from the company for "a whole lot longer than three months." Redhat officials appear to be stonewalling on the issue, responding to questions with a baffled look and the reply, "What the hell are you talking about?"

    According to the report, unknown hackers managed to procur a password to Redhat's network servers. They then used the password to download the blueprints to all of Redhat's products. Even worse, the password was circulated widely over the internet, allowing thousands, potentially over a million hackers to repeat the exploit.

    One person familiar with the case said it appeared the hackers initially gained access to Redhat's corporate computers by exploiting a hole in the company's "FTP" software. This software is used to transfer files between remote computers. The hackers discovered that the password "anonymous" allowed them access to all of Redhat's intellectual property.

    Most damning of the report's accusations is the claim that internal Redhat officers have known about the vulnerability for months, even years, but failed to alert customers or close the security hole.

    The breach may have allowed hackers to insert instructions into the blueprints for Redhat's products, including the recently released Redhat Linux 7. One anonymous insider called such practices "common." When asked if they were planning an extensive audit of their code, Redhat officials repeated their reply, "What the hell are you talking about?"

    1. Re:Redhat Cracked by QuantumG · · Score: 1

      You should send that to MSNBC, they would probably publish it.

      --
      How we know is more important than what we know.
  321. Re:Open Sourcing Windows... by joshuaos · · Score: 1

    They can't drag everyone to court, and the more people that host it, the more difficult it will be for them to bring lawsuits. How many people have been sued over DeCSS compared to the amount of people hosting it? Hosting the Windows Source would represent a protest.

    Joshua

    --

    When in danger or in doubt, run in circles, scream and shout!

  322. You're our new winner! by mosch · · Score: 1

    Congratulations, AC, You won today's edition of the tin foil hat awards! A black helicopter will be by later to give you your award.

    --
    "Don't trolls get tired?"

  323. LOL by metis · · Score: 1
    I liked the part about the hackers stealing source code, it reminded me of the O Henry story about kidnapping the chief ( dunno the exact name). Or maybe it is a smart attempt to convince the media that someone wants their source code.

    --
    -- look, cheese ahoy!
  324. Hack update by verbatim · · Score: 1

    Several people have reported over IRC that someone going by the nick "BigBG" hacked into ftp.kernel.org and STOLE the source code to LINUX. It turns out that the kernel.org servers were configured in such a way that "BigBG" could exploit the known Anonymous/Email user-account. It is unknown how long this BigBG has had access to the Linux source code, nor is it known what code this person could have introduced into the Linux kernel. Linux sys-admins are encouraged to check their systems for a mysterious kernal entry that may cause your computer to emit a so-called "Blue Screen of Death" upon a segmentation fault. Linus Torvalds was not bothered for comment.

    ;)

    Verbatim

    --
    Price, Quality, Time. Pick none. What, you thought you had a choice?
  325. Open Source by pcwhalen · · Score: 1

    on Office and Win 2000 whether or not MS wants it. Hmmm.......

    --
    Pay no attention to the man behind the curtain with all your metadata.
  326. A moment of enjoyable, paranoid speculation by Badgerman · · Score: 2

    Considering the antitrust case going on, can Microsoft leverage this to show that Windows "now isn't closed" and "the code is in the wild" and thus claim they shouldn't be treated as a monopoly?

    Could this have been "allowed" to happen? Note there seems to be a great deal of confidence no source code was changed, just code stolen.

    Not rational sepculations, of course, merely interesting ones to explore the depths of paranoia.

    --
    "The Sage treasures Unity and measures all things by it" - Lao Tzu
  327. If only... by Brian+Knotts · · Score: 2
    ...this could somehow persuade IT managers to *finally* begin diversifying their networks, it could turn a negative into a positive.

    Although I could see how some people might not see this event as a negative to begin with. :-)

    --

  328. This is a conspiracy . . . by acceleriter · · Score: 2

    . . . for Microsoft to be able to explain the back doors they have placed in software when the get found. Golly! There's a back door in Win2K?! Those nasty Russian Mafia people must've put that there. We'll comment that out, er, uh . . . remove that in the next service pack!

    --

    CEE5210S The signal SIGHUP was received.

  329. slashdot123 (OT) by nob · · Score: 1

    I was thinking, wouldn't it be nice if login: slashdot123, password: slashdot123 was registered at all these annoying websites that make you register to read articles, access content, ect (like nytimes.com for one)? If we all just registered this id/pass when we'd normally register our own, we could save a lot of hassle for all other /. users.

    --
    daed si luap
    1. Re:slashdot123 (OT) by ConceptJunkie · · Score: 1

      Try "cypherpunks"/"cypherpunks"... works lots of places.

      Rick

      --
      You are in a maze of twisty little passages, all alike.
  330. Desiring compatibility? How rogue!!! by siliconghetto · · Score: 1
    The article stated:

    "The motive behind the break-in isn't known...either to improve its own products or make those products more compatible with Microsoft's best-selling operating systems. "


    What??? Trying to make one's software compatible with Microsoft's OS? How rogue of them!!!!! How dare they!!!!

    --
    ========================== pipe(13) -- can you figure it out?
  331. MS source code by pcmills · · Score: 1

    I like this

    "We are confident that the integrity of our source
    code remains secure. There's no evidence that any
    source code has been modified or corrupted," Miller said.

    You mean they didn't fix it.

    --
    Ask Slashdot - google for stupid people.
  332. And they don't know if their source is clean... by Rdickinson · · Score: 1

    Wonder whats been added to the retail windowsME,free trojan with every copy? Guess M$ might be going open source...

    1. Re:And they don't know if their source is clean... by Delphis · · Score: 1

      oooh.. good point.. Jeez.. they must be going nuts over there in Redmond. 3 months is a long time to have a hole open.
      --

      --
      Delphis
  333. Re:Open Sourcing Windows... by JimPooley · · Score: 1
    They may very well have the kind of leverage to get the US government to pressure whichever countries supply SeaLand's bandwidth to have SeaLand cut off
    The US would have to pressure a few North Sea countries (All reasonably wealthy with no real dependence on the US) essentially as a favour to a corporation currently being tried for monopolistic practices. Of course, MS could directly approach those countries.
    The thing about Sealand is that when it was founded it was outside British territorial waters - the old three mile limit. We extended that to a ten mile limit several years ago. Sealand is now inside British Territorial Waters.
    I suspect the only reason we haven't already reposessed it is because nobody has paid any attention to it - nobody wanted the hassle. It's a bunch of metal and concrete in the north sea, so long as it's not being used for illegal purposes (drug running or terrorism), it's harmless and eccentric - and we love eccentrics.
    Picture this: Offended party complains to FBI. US Gov. asks UK Gov. to do something. UK Gov. closes down Sealand and probably demolishes it. After all, it is government property, and the only reason it hasn't been knocked down is because there's been no real need to.
    The idea that Sealand is going to be some kind of wonderful free data haven outside the reach of governments is a pipe-dream for inhabitants of cloud cuckoo land.


    Hacker: A criminal who breaks into computer systems
    --

    "Information wants to be paid"
  334. Open Sourcing Windows... by The+Dodger · · Score: 4

    If the hackers release the source into the "wild", we're likely to see a similar situation to DeCSS - anyone who hosts or links to the source code for Windows or any other Microsoft software will have the full force of Microsoft's legal vultures brought to bear upon them.

    Wonder if HavenCo would host it. That would mean a real, live-fire test of SeaLand's sovereignty - if Microsoft can't beat them, then noone has a chance! :-)

    D.

    1. Re:Open Sourcing Windows... by bilgebag · · Score: 5

      First one to submit a patch gets to pick a new default colour for the Screen Of Death...

    2. Re:Open Sourcing Windows... by rdl · · Score: 5

      It's not against our AUP.

      We as a company are not in favor of software
      piracy, so we certainly wouldn't help, but if
      a customer wanted to host stuff like this, we can't really say it's against our AUP.

      (I personally think MS source code would be a
      waste of space, a thousand monkeys and all that...)

    3. Re:Open Sourcing Windows... by Erasmus+Darwin · · Score: 2

      Which brings up an interesting circumvention technique. If you were to hypothetically assume that a pool of open source developers were all able to get their hands on the Windows source, could the sneak around the law by releasing some sort of diff (probably something other than 'diff -u', given that that tends to include original code)? Maybe an XOR scheme with some heavy versioning magic? It obviously wouldn't stop the entire source distribution or the resulting build from being illegal, but it might be just enough of a gray area to get a public collaborative effort going. windows.sourceforge.net, anyone?

    4. Re:Open Sourcing Windows... by joshuaos · · Score: 1

      I don't know about you all, but I would host it everywhere I could! At work, at home. Hell, I'm going to be running a slash site soon, and I'll bloody well put it there. I can't wait till it begins to circulate (as I suspect it most certainly will).

      Joshua

      --

      When in danger or in doubt, run in circles, scream and shout!

    5. Re:Open Sourcing Windows... by Sloppy · · Score: 1

      sneak around the law by releasing some sort of diff (probably something other than 'diff -u', given that that tends to include original code)?

      No, that would be something called a "derivative work," and even less of a gray area than spreading around an MP3 that has been compressed from a copyrighted work that was originally in audio CD form.

      Doing what you suggest would get sourgeforge.net into a very clear copyright infringement situation. That would be bad for everyone.


      ---
      --
      As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    6. Re:Open Sourcing Windows... by JArneaud · · Score: 1

      As far as I know you can change that already (with a registry value). Locating the instructions for this is left as an exercise for the reader.

    7. Re:Open Sourcing Windows... by mattdm · · Score: 1
      I don't remember the history exactly, but I know there *was* a UK court case which affirmed that Sealand doesn't fall under UK juristiction. So they haven't been completely ignored.

      --

    8. Re:Open Sourcing Windows... by el_nino · · Score: 1

      A country cannot take foreign territory by extending it's territorial water limits, no matter if it's Sealand or a big, powerful country.
      --
      Niklas Nordebo | nino at sonox.com | +46-708-405095

    9. Re:Open Sourcing Windows... by JayBonci · · Score: 2

      Except that they would lose. And i mean bad. Someone broke the law. It's totally different. It's not like someone reverse engineered the Windows Kernel. Someone stole the source. If you accepted it, you could go to jail. It's stolen property, regardless of what you think of Microsoft.

    10. Re:Open Sourcing Windows... by Mawbid · · Score: 1

      And regardless of whether it's legal or illegal, distributing the stolen Microsoft code is wrong.
      --

      --
      Fuck the system? Nah, you might catch something.
    11. Re:Open Sourcing Windows... by nick_davison · · Score: 5
      we're likely to see a similar situation to DeCSS

      How the hell am I going to get all that bloatware on the back of a t-shirt?!

    12. Re:Open Sourcing Windows... by schulzdogg · · Score: 1
      And regardless of whether it's legal or illegal, distributing the stolen Microsoft code is wrong. Amen. Despite your feelings about microsoft they do have the right to choose how their work is distributed. If it doesn't match your views that doesn't make it acceptable to steal it.

      Imagine how slashdot would go up in arms if microsoft took some GPL'd code and schlepped it into windows, ignoring the license. By advocating the release of microsofts source against their will you are doing the exact same thing.

  335. Re:I wonder why by WildBeast · · Score: 1

    actually MS uses UNIX to protect themselves from viruses

  336. This is obvious but... by K8Fan · · Score: 3

    ...what in the hell would hackers want with Microsoft's plans? Script kiddies, sure. Crackers, of course. But actual hackers? No self-respecting hacker would ant or need to crib from Microsoft's notes. That would be like copying off the paper of the class idiot.

    --
    "How perfectly Goddamn delightful it all is, to be sure" Charles Crumb
    1. Re:This is obvious but... by jrumney · · Score: 5

      Hackers huh? Hopefully they'll fix some bugs before they give it back.

    2. Re:This is obvious but... by LowneWulf · · Score: 1
      An 'actual' hacker as you put it probably would have no more use for M$ source than as a curiosity and a playtoy. And some damned fine bragging rights.

      It'd be funny if the hackers modified Outlook(express?) to not be vulnerable to the same hack that killed M$ in the first place, and email it back to them.... har!

    3. Re:This is obvious but... by cathryn · · Score: 1

      I doubt they'd bother fixing the bugs. But likely, they'll be looking for buffer overflows.

      The geniuses at Microsoft can rest safely, though, knowing that normal puny brains are too tiny to understand their brilliantly obfuscated code.

      --
      http://junglevision.com -- Shamus for Gameboy
    4. Re:This is obvious but... by joshuaos · · Score: 1

      ...what in the hell would hackers want with Microsoft's plans?

      Real hackers, who are advocates of OSS and not very big fans of M$ have every reason to open up that source. This could theoretically topple M$ to quite a degree. It will be very interesting to watch what happens in the near future.

      Joshua

      --

      When in danger or in doubt, run in circles, scream and shout!

    5. Re:This is obvious but... by Jeremi · · Score: 1
      ...what in the hell would hackers want with Microsoft's plans?

      It would be interesting if someone looked through the source code and found evidence of dirty tricks (e.g. code to deliberately disable a competitor's product, etc) and published it (with some sort of proof of existence, I'm not sure how that would work)

      --


      I don't care if it's 90,000 hectares. That lake was not my doing.
  337. Re:Going to affect everyone by biohazard99 · · Score: 1

    Anyone else have trouble using their pron^H^H^H^H, hotmail accounts last night, login worked, no inbox though 2-2:30AM East US time

  338. Save Face by jjr · · Score: 2

    I wonder what now Microsoft has to do to save face in light of these action being taken agianst them. As a Big player in the world of softawre this will hurt alot of thier products. For instance if the source code for IIS was stolen I feeel really bad for people who run NT servcers hey could find an exploits even quicker and I would think it would be harder for microsoft to fend these type off attacks.

  339. This isn't good. by StarbuckZero · · Score: 1


    I'm a Linux user in all, but if MS fall I want them to fall the right way and no other. Besides I wouldn't feel right putting something into my program and knowing that I got it the wrong way.

    It's Illegal all I have to say about it...

    =/

    --
    From Zero to Hero... Starbuck Zero
    1. Re:This isn't good. by radja · · Score: 3

      I don't care how M$ falls. They've made it clear that they'll stoop to any level to get more cash, but now the shoe is on the other foot. But I would not insert any windows code into a linux app. linux is not the OS of thieves. And that would make linux just as bad as M$.

      //rdj

      --

      No one can understand the truth until he drinks of coffee's frothy goodness.
      --Sheikh Abd-Al-Kadir, 1587
  340. Tell my boss about this by wiredog · · Score: 1

    As he really likes to use MS software on major systems that we sell to our customers. With Unix we can tweak the security setings at a finer grained level. And (with OSS) find out where the holes are, and fix them ourselves.

  341. Re:s/NT/stupidly trojan-enabled software/ by schon · · Score: 1

    it's easy to get the same functionallity if you KNOW how to administrate a WindowsNT

    OK, I'll bite..

    So you're saying that the company that wrote NT doesn't know how to administrate it?

    (and please don't blame 'untrained users' - on a properly configured *nix system, an untrained user couldn't do any harm...)

  342. Proliferation of new backdoors by BennsArrow · · Score: 1

    It is interesting to note that with the "open" sourcing of any of the
    stolen source code, there is the potential for the exposure of a
    multitude of new backdoors/vulnerabilities into MS apps and a
    proliferation of new exploits in the coming months. While I dread
    the initial flurry of activity, it will be a great benefit to get
    these backdoors/vulnerabilities closed and patched once and for all.

    Sean

    Sean Brown
    Linux Evangelist
    "I'll let you be in my dream if I can be in yours." - Bob D.

  343. hope source code gets out by aseen · · Score: 1

    Here's hoping whoever did this took a copy of the source code, and will release it somehow (this is a great chance to test the efficacy of Freenet). This could help conquer a whole host of reverse engineering tasks facing the linux community.

    1. Re:hope source code gets out by Delphis · · Score: 1

      Best get some RH6.2 CDs now then, eh?

      --

      --
      Delphis
  344. now is "open source" by overlord · · Score: 1

    Now microsoft is "open source" or it ever was ?

    Overlord

  345. Not everyone by twitter · · Score: 2
    Nothing, open source can't compete on this level unless it incorporates itself under law, and the pseudo-communistic rantings of gurus like Stallmann will prevent this from ever happening.

    Sorry, greedy little troll, RMS does live within the law and FSF software has noting to fear at all from this BS.

    --

    Friends don't help friends install M$ junk.

  346. Re:Don't do it! by linuxgod · · Score: 1

    hmmm, you dont' even hage a page.
    Ill post your picture later on tonight.


    Ignore the Anonymous Pissant trolls !!!

  347. Re:Sounds like a great idea! by Kisc · · Score: 1

    Hmmm. Maybe Mr. Bill is a saint, rather than the anti-christ. Maybe he designed his software that way on purpose to make the world a safer place!

    *loud exhale*

    Wow, that's some good s**t.

    Probably shouldn't post while I'm smoking it though...

    Failure is not an option.

    --

    Failure is not an option.
    It comes bundled with Windows.
  348. Re:This is obvious also... by canning · · Score: 1

    Fixing some bugs would make more sense than fixing 'em all. That could take even the most bright and dedicated programmer(s) a lifetime. Maybe they could release it under the name Windows Hee Hee Version 1.a

    --
    I love the smell of Karma in the morning
  349. Re:This could be the greatest thing to happen sinc by WindowsTroll · · Score: 1

    >> No seriously, imagine forced open source.

    I don't see any advantage to having the MS source "open" as a result of a hackers actions.

    The information was gained illegally, so the possession or use of this information becomes illegal. The US judicial system does frown upon corporate espionage, which is how this would be considered. I believe that this would be illegal in most EU countries in regards to copyright laws.

    If *nix is a superior OS to Windows, and you have the source code for *nix, then where is the desire to have the microsoft source? This would be a step backwards, which in the software world, is downright stupid.

    --
    "Microsoft has made computing accessible to a population who would otherwise not be able to use computers" - B. Kernigha
  350. The end of the world by leonbrooks · · Score: 1

    Your tagline said: I have seen the end of the world! I think it was an exit on the Jersey turnpike. Eerie how appropriate taglines sometimes are. The end of the world is Outlook. If one single piece of software has the ability to knacker the 'net, Outlook is it. Maybe now Microsoft will do something serious about fixing it? Yes, I know, it is wishful thinking, but stranger things have happened. On the subject of the potential theft of Office and Windows, Bill will just write a letter to the crackers complaining that he can't make any money if they steal his code, and then tell everyone else that it was a buggy release anyway and he's concerned that it'll give his company a bad image.

    --
    Got time? Spend some of it coding or testing
  351. DNS Damage by zTTTz · · Score: 1

    You can look at some of the damage that was done to the DNS @ Internic as of 8:30 this morning.

  352. More linkages (and details) by beebware · · Score: 3
    More details are available from:

    Richy C.
    --
  353. Happened at Digital - BIG Mess over Source Audit by hughk · · Score: 1
    This happened at Digital some years ago requiring a massive audit of OpenVMS to look for trapdoors. The source to Win2K is many times larger and there is a lot about MS that suggests that their version control isn't that hot. A thorough audit will take a *long* time and take a *lot* of warm bodies.

    It may be a good time to sell your Micro$oft shares!

    --
    See my journal, I write things there
  354. Just release the code by hrieke · · Score: 1

    is what should be done.

    --
    III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...
  355. Re:No Security on a Windows Network by fredrik70 · · Score: 1

    wasn't it a cool article on /. before regarding using the nameserver to tunnel out of firewalls?

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  356. M$ source code "integrity"?! by macdaddy · · Score: 1
    "We are confident that the integrity of Microsoft source coderemains secure."

    The funniest phrase in the whole WSJ article is the one above. "integrity" and "Microsoft source code" is something I never thought I'd see in the same sentence, unless of course there was a huge NOT stuck in the middle! Way to go Hemos!

  357. A plea to the perpetrator(s) by Diskore · · Score: 1

    Please release whatever source you got and let it spread like a virus. Please, oh god, please.

  358. What happened to Win2k file protection? by AlienFactor · · Score: 1

    I thought Windows 2000 file protection was supposed to protect against exactly this sort of thing. This was supposedly a trojan that overwrote Notepad.exe, and Notepad.exe is one of the files that supposedly can't be replaced unless the replacement is signed by MS's private key.

  359. I wonder why by Daath · · Score: 1

    ...they didn't install some anti-virus mail scanning thing for Exchange?
    Oh wait... Maybe they aren't using Exchange? ;-)

    Oh well

    --
    Any technology distinguishable from magic, is insufficiently advanced.
  360. Re:how do we even know.. by NecroPuppy · · Score: 1

    this is for real? ms has been known to bullshit a lot. with things looking so bad for them with the trial, maybe they're trying to get a bit of public sympathy?

    Well, federal law enforcement agencies are well known for lacking a sense of humor. If they found out that MS was BS'ing them, heads would roll.

    The FBI doesn't have much of a sense of humor; maybe more for this than, say, a kidnapping, but it still isn't worth the risk. (The Secret Service has no sense of humor.)

    --
    I like you, Stuart. You're not like everyone else, here, at Slashdot.
  361. Re:Well, Ho Ho Ho by Shotgun · · Score: 2

    It doesn't matter what OS you're running or what Email proggy you use if the person is dumb enough to run random executables.

    But what happens when an email program provides a preview feature that will open an email and show you the first few lines and an auto-execute feature that will run an arbitrary program when the email is opened?

    What happens when both features are enabled out of the box? Is a heart surgeon to be called stupid because he spends his days reading up on heart surgery instead of all the intricacies of computer security?

    --
    Aah, change is good. -- Rafiki
    Yeah, but it ain't easy. -- Simba
  362. Re:Should I release the code? by The+Mutant · · Score: 1

    Boy I sure as hell hope you haven't posted message this from your home or work computer.

  363. I am surprised .. I wonder why... by UltraWide · · Score: 1

    .. they have any network access at all from the development environment to the Internet .. it should be unplugged by default ...

    Well .. this shows that if you want a place to be secure you should not have physical access at all to the Internet from that place... Heck .. they should have two terminals one for the development systems and one for Internet access/mail etc..

    If they have different locations where they develop code you can actually lease a separate line and not use for example vpn over the Internet.

    --
    I really HAD another userid .. I promise!
  364. Re:Going to affect everyone by Salsaman · · Score: 2
    "Microsoft can sue anyone who looks like they have a copy of their code (Wine), and what are they going to do?"

    Erm, ask for proof ?

  365. What you on about? by meadowsp · · Score: 1

    Surely you're not judging an operating system on the symantics of it's move directory command?

    cd == set def
    rmdir == delete whatever.dir

    By your reckoning MS-DOS is as good as any Unix, because it's got the CD command. Yeah, right.

    1. Re:What you on about? by Brett+Viren · · Score: 1
      Granted, I never spent the same effort to learn VMS as I have for UNIX, but I never felt comfortable in the VMS shell. In the case of changing directory, one had to use a clumsy (opinion!) path statements with too many brackets and colons. For removing directories there was always some dificulty with permissions so that by default, I could not delete my own directories.

      I know there are many people who swear by VMS so I am sure it isn't a terrible OS, but i just can't see it ``kicking the crud'' out of UNIX.

      Anyways, I was certainly not asserting that having a CD command makes a OS better, but rather the level of comfort that a VMS shell gives me is minimal in comparison to UNIX shells (even plain sh). In my mind, DOS is only slightly more comfortable than VMS as an environment. (This is very likely due to just familiarity).

      One thing I do remember fondly about that year of VMS is the help system was quite usefull. In comparison, UNIX's man system suffers as it is focused more as a reference guide than a guiding reference.

  366. Happy Birthday Billy!!! by James+Foster · · Score: 1

    Wow... on the eve of Bill Gates birthday... his most precious software source code gets found to be stolen. Have a great one Billy!! ;]

  367. Not A Good Thing by pokrefke · · Score: 5

    No matter how much you think Bill Gates is the anti-christ or hate Windows, this is most assuredly NOT good news. The judges, the lawyers, and the law enforcement that will certainly become involved in this case will look at one point, and one point only: someone broke the law. Know what else? They don't understand you, and they don't care that you want Wine to work better or an Open Source Windows.

    In the interest of fairness, let's look at this from their point of view. "Hackers" (does anyone know what this word means anymore?) have been getting a lot of bad press lately. Hacking into Microsoft's site adds fuel to the fire. Stealing Microsoft's code is fanning the flames.

    Everyone is making jokes about how insecure MS products are, as if Apache or Slashdot have never been compromised.

    Even more worrisome is the opinion of the everyday, ordinary citizen. Some of which have made money off MS stock. Many of which use a computer, but aren't as "in" to them as we are. I bet you lunch that they see stuff like this and feel "insecure". And I guarantee you, when something like Carnivore comes along, the average person will suport it, because it makes, at least in their mind, the online world a safer place.

    So laugh now about Microsoft's problem. Joke about an OSS Windows, regardless if they want it or not.

    Ladies and Gentlemen, if you're old enough to understand, it's time to realize that this is most assuredly Not A Good Thing.

    Disclaimer: MY computer runs Linux/BeOS.

  368. Color me paranoid... by Cullpepper · · Score: 1

    ...but what is the probability of a group of russian-teen-uber-hackers breaking into Microsoft's inner scantum, vs. the probability of the DOJ enlisting the aid of Microsoft to stage an "event" that will influence public opinion and help law inforcement authorities "crack down" on these vicious computer crimes?

    If you think the gov't doesn't create news events for the sake of swaying public opinion, you haven't been paying attention.

  369. What's next: OS version Windows has forked?? by drnomad · · Score: 1

    Because the Russians seem surf the stability wave?

  370. The saddest quote on the MSNBC site... by Invicta{HOG} · · Score: 2

    Other possible motives include economic espionage, though experts said only a rogue company might knowingly buy stolen software, using it either to improve its own products or make those products more compatible with Microsoft's best-selling operating systems.

    I'm not sure how you can label a company as ROGUE whose purpose is to provide more compatible software...maybe now we'll get open source windows...

  371. This could be great for other suites by loftwyr · · Score: 1

    All abuse of MS aside, This could be positive for the market as a whole.

    Ignoring the Windows source and focusing on the office source, it could now be possible to use some of this source code to make things like StarOffice or AbiWord properly import Word/Powerpoint/Excel documents. Once you have the source, you could use it as a basis to write new import code for any other Suite.

    The hardest part about getting people to move to OSS was the fact you couldn't convert between MS Word and back. Now, maybe we can and Linux, BSD and BeOS can make serious inroads.

    Lets see what new submissions to the various OSS suites happen in a few months...

  372. Users can't sniff passwords, firewalling no help by leonbrooks · · Score: 1
    This child process sniffs out passwords, because hey, any user account can sniff packets, not just root.

    If you weren't a spineless AC, I'd give you an IP, a user login and a password for this (my home) box, which is running an obselete version of Mandrake Linux.

    I'll also bet you $Oz1000 that you can't use that account to sniff any passwords. I'll add a side bet of a further $Oz1000 that you can't ping or traceroute either.

    This box has not been security tweaked (if it had you wouldn't be able to blow your nose here without special permission) indeed I've undone some of the default security.

    Now, shall we discuss a system which is serious about security, like OpenBSD or OpenVMS? (-:
    Microsoft's biggest mistake was that it wasn't using a more secure firewall to protect it's local machines

    Horse puckey. They were trojanned, so no amount of firewalling would have helped. Microsoft's biggest mistake was limiting their use of Unix to software manufacture plus the odd curiostiy piece.
    --
    Got time? Spend some of it coding or testing
  373. Re:Where is FBI when my machine gets cracked? by extar-bags · · Score: 1
    Amen! This falls on deaf ears every time i say it, which is every time i get into an argument about the [im]morality of cracking: it is not ok to break in "just to look around."

    ----------

    --

    ----------
    "Rock over London... Rock on Chicago..." -Wesley Willis

  374. Re:Read the (full) Wall Street Journal Article by Anonymous Coward · · Score: 2

    If you make a public registration somewhere
    try/create standard cypherpunk/cypherpunk first. (or was is cypherpunk?)

    (Please mod up if you know what I'm talking about)

  375. RE: Red Hats source by Spit_Fire1 · · Score: 1

    But wait! Red Hat started the open source revolution.

    --

    "The secret of success is to know something nobody else knows." -Aristotle Onassis
  376. Re:s/NT/stupidly trojan-enabled software/ by TheCarp · · Score: 1

    While I agree with you - It is stupid to have full fledge scripting languages built into email clients - and setup in wayhs that are just RIPE for abuse - its not like thats the only problem.

    Its not like noone ever found a buffer overflow in pine that would expoit as soon as the victem read mail. (of course - ive only seen that once - maybe twice - and it got fixed quickly)

    Then again - that is the beauty of unix - every user can pick their email client - there is no push or need to make EVERYONE use pine or elm or mutt (though I do prefer the latter).

    -Steve

    --
    "I opened my eyes, and everything went dark again"
  377. Re:The end of email-attachments? by Threed · · Score: 1

    My slashdot ID (13487) is 70,000 lower than yours (82141), isn't it. :) I've been around long enough.

    You have nothing to brag about. Move along.

    The real Threed's /. ID is lower than the real Bruce Perens'.

    --Threed

  378. Re:it's *NOT* a very good point by jovlinger · · Score: 2

    yup. Since the original host (infection 0?) was infected via an email attachment, it would have been easy for the attackers to tunnel through the firewall (port 80, perhaps: outgoing information encoded in the URLs).

  379. Possibilities... by joshuaos · · Score: 1

    I see several main possibilities here. The first is that this is real, and will be a great boon to the open source movement. I think that when we get our hands on the code that we're going to see some pretty nasty stuff in there.

    Another possibility is that this is an untrue rumor, possibly started by Micro$oft in an attempt to push through the Draft Cybercrime Treaty, or for other, unknown reasons.

    Either way, the lawsuits will start flying like mad quite soon, and things will change.

    Joshua

    --

    When in danger or in doubt, run in circles, scream and shout!

  380. Do I smell a rat? by codewhite · · Score: 1

    We may be missing something here. Did they find a way to turn this to their benefit? Their stock is GOING UP!

    Or did they plan this all along?

  381. Re:s/NT/stupidly trojan-enabled software/ by jbarnett · · Score: 1


    Maybe the admin was logged in with as ADMINASTOR while checking his email?

    If the admin was logged in as user "bob", your right a rampaging binary should of not cause that much damage.


    --

    "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
  382. The "Truth" about who Microsoft really is by b1t+r0t · · Score: 5
    Any of you with Unix shell access should try:

    whois microsoft.com

    also whois aol.com ; whois apple.com ; whois whitehouse.gov

    How did they do it? Simple. Whenever you register a nameserver IP address, you have to include a domain name for the nameserver. I think the only thing checked is that the IP address pings and the domain name is part of a real domain.

    --

    --
    "Open source is good." - Steve Jobs
    "Open source is evil." - Microsoft
    1. Re:The "Truth" about who Microsoft really is by wmschris+ · · Score: 2

      SamSpade is pretty good. I also like WS_PingPro

      But SSH would eat their lunches.

    2. Re:The "Truth" about who Microsoft really is by Erasmus+Darwin · · Score: 2

      Also, a press release from one of the groups doing it.

    3. Re:The "Truth" about who Microsoft really is by Danny+Tai · · Score: 1

      Methinks the name servers are going to be slashdotted...

  383. Hopefully they are tried in the US... by krypteia · · Score: 1

    ..if they are caught. Then all the info that they stole will become part of the public record. =]

    --
    Spazdot-1 in 10 insightfull articles, and 1 in 10,000 insightfull comments ain't bad.
  384. On Topic? by Bilbo · · Score: 1
    Hummm... On topic? I suppose. Dumb? Definitely - though not dumb enough that I'd moderate it down given the opportunity.

    Do you really think Microsoft really needs such a lame excuse to "go after" the Open Source community and efforts such as Wine? They are perfectly capable of thinking up a lot more believable reasons than that why such reverse engineering "infringes" on their IP.

    Microsoft may be a huge bully, but I don't think they are a huge brainless bully.

    --

    --
    Your Servant, B. Baggins
  385. how do we even know.. by jspectre · · Score: 1

    this is for real? ms has been known to bullshit a lot. with things looking so bad for them with the trial, maybe they're trying to get a bit of public sympathy?

    how can they be an ultra-powerful monopoly if they are hacked by a bunch of script kiddies? hahahahahaha

    --

    abcdefghijklmnopqrstuvwxyz

  386. Re:This could be the greatest thing to happen sinc by iMMersE · · Score: 1

    The information was gained illegally, so the possession or use of this information becomes illegal. The US judicial system does frown upon corporate espionage, which is how this would be considered. I believe that this would be illegal in most EU countries in regards to copyright laws.

    Still, the fact the information was gained illegally doesn't mean anything - Compare with DeCSS, for example ...

    If *nix is a superior OS to Windows, and you have the source code for *nix, then where is the desire to have the microsoft source? This would be a step backwards, which in the software world, is downright stupid.

    How would having the Windows code be a step backwards. Having it would be very useful, having as much reference material as possible is good. It doesn't mean people are suddenly going to drop their current kernel code tree and start using the Windows one ... We can do that by installing Windows now.

    .iMMersE

    --
    codegolf.com - smaller *is* better.
  387. Re:Funny? Learn to moderate! by fredrik70 · · Score: 1

    True, not sure the email thingie would work against unix. However, all networks got cracks, there are flaws in unix thatr has ben used b4 to gain root access and there are probably a few around now as well, nothing is 100% secure...

    Mind you I believe unix is far more secure than win, but it' s *not* 100%

    --
    if (!signature) { throw std::runtime_error("No sig!"); }
  388. What's the Source doing connected to the Net? by rute_1 · · Score: 1

    If the source code is so private, then why is M$ storing it on a network that connects to the Internet in the first place? The company I work for develops software but we have a closed network that the software is developed on. It has no connection to the internet. When the software is tested for internet compatability it is compiled and copied over. It seems to me for something that M$ would want such high protection on, they wouldn't let it anywhere near an Internet connection.

    1. Re:What's the Source doing connected to the Net? by JASegler · · Score: 1

      You just answered it.

      If you have *any* machines that have access to the internal network AND to the internet then your screwed. A trojan sitting on that machine can act as a gateway. The way I read this was you went to a workstation connected to both and copied it from the server to the workstation.

      Now if it's completely seperate (seperate hubs and the files have to be moved physically via zip disk or something) your fairly safe. However most networks are designed for "user friendly" rather than security. Most people don't put the servers on the net.. But put the workstations on both the net and the internal network.

      Also telecommuting is pretty popular in our industry. You have to be able to get to these things via the net or some dialup access if your allowing your developers to telecommute.

      MS got screwed by their own "user friendly" SW. Myself, I'm going to be looking for the laugh track over the next few weeks (aka MS PR spin doctoring/damage control teams)

      -Jerry

  389. Not Microsoft! by Bill+Pela · · Score: 1

    And now, more to the point, NOT MICROSOFT!

    HA HA!

  390. Why open source is better... by dennism · · Score: 1

    You'll never see an article about RedHat like this... "Yeah, they broke in and stole the source to our prize gem OS..."

    --
    dennis
  391. it's *NOT* a very good point by schon · · Score: 3

    In fact, it's probably the biggest misconception he made.

    Relying solely on a firewall is the single biggest mistake a company can make.

    True, a proprely configured firewall can make a huge difference, but _real_ security involves securing every machine on the network. A firewall won't fix a problem with bad client (such as Outlook) executing code it's not supposed to. A firewall won't fix a problem with a web/mail/whatever server running behind it.

    The bottom line is that if a machine needs to talk to the internet, it _needs_ to be secured, because an improperly written app can make any firewall completely useless.

    1. Re:it's *NOT* a very good point by TheCarp · · Score: 1

      > Relying solely on a firewall is the single
      > biggest mistake a company can make.

      > True, a proprely configured firewall can make
      > a huge difference, but _real_ security involves
      > securing every machine on the network.

      I completely agree. I also find that firewalls tend to be more trrouble than they are worth. Give me a bunch of hard hosts over a few soft hosts and a firewall any day of the week.

      However - here is the kicker. Microsoft seems to be designing their OSs (like plain old windows) with the idea that "Client machines are behind the firewall" in fact - it seems alot of vendors design things with that in mind.

      If you CAN'T make the host secure - then definitly put it behind the firewall. Windows hosts shareing files? Oh yea - thats where they are designed to be!

      -Steve

      --
      "I opened my eyes, and everything went dark again"
  392. The end of email-attachments? by Otis_INF · · Score: 2
    Reading the WP's story how the crackers got initial access, I wondered if this action will end the possibility to sent executables with email messages using MS software (as in: they'll patch the tools to get rid of this feature, as they should have done ages ago). I mean: the way the crackers got access wouldn't have possible with the lack of a way to send a person an executable by email (as a trojan).

    OTOH, it's always possible to get a trojan to a person's PC, f.e. by let the person download some moronic 'gadget' for the desktop. But it would have been way more difficult that way.
    --

    --
    Never underestimate the relief of true separation of Religion and State.
    1. Re:The end of email-attachments? by image · · Score: 1

      My slashdot ID (13487) is 70,000 lower than yours (82141), isn't it. :) I've been around long enough.

      It was funny respoding to anti-MS posts when I was working there. On the one hand, I was the guy running the Linux boxes at work, and had to defend *that* to my colleagues. On the other, I was the guy posting on Slashdot saying that MS wasn't *all* that bad...

    2. Re:The end of email-attachments? by SurrealKnife · · Score: 1

      Why would it be difficult to get an MS employee to download anything moronic? I would have thought it to be the easiest thing in the world...

    3. Re:The end of email-attachments? by aidan+skinner · · Score: 1

      Reading the WP's story how the crackers got initial access, I wondered if this action will end the possibility to sent executables with email messages using MS software ¥as in: they'll patch the tools to get rid of this feature, as they should have done ages ago© I mean: the way the crackers got access wouldn't have possible with the lack of a way to send a person an executable by email ¥as a trojan©

      I think this is unlikely, sending executables in mail can be handy ¥it's not the "right" way to do it, but it's sometimes easier than sticking it up on an ftp machine

      From what I read, it wasn't auto-executed, but was deliberately run by the reciever, which means somebody's due for the kicking of their lives©©©

      - Aidan

    4. Re:The end of email-attachments? by Juggler · · Score: 1
      Email attachments, be they binaries or something else, are far to valuable and useful to be eliminated or banned.

      Windows programs may be more vulnerable, but that is largely due to how common they are - finding a single bug has an impact on a huge number of users. There have been, and probably still are just as serious problems with Pine, Mutt and other open source mailers. Exploiting them just isn't as much fun...

      So while it is true that email programs should be more careful about their default behaviors, the biggest problem still lies in the user's ignorance of what is dangerous and what is not. No matter how good the mailer is, social engineering can still make email a security risk.

      What has been IMHO lacking is a tool to help those of us who do know what we are doing protect the ignorant users from common mistakes and problems, without making their lives too difficult. This is more or less what all firewalls do - and email should be firewalled in the same way, for the same reasons. It's all about risk management - the risk cannot be eliminated.

      This is only marginally related to the Microsoft hack - but it is quite likely that if they had had such a policy, and had automatically enforced it wherever possible, then they wouldn't have been hacked so easily.

      There are tools to do this, which were inspired by the obvious dangers posed by active HTML content and malicious attachments. Follow the link in my signature - I wrote one. :-)
      --

  393. Re:This virus has been known since August! by schon · · Score: 1

    rated it a 5 out of 10 for harmfullness

    I wonder if they'll re-asses it now? :o)

  394. Let your conscience guide you by Diskore · · Score: 1

    But be careful as noted by the above reply

  395. Update by mav[LAG] · · Score: 5
    ST PETERSBURG, Russia: 2000-10-27: In a joint sting operation, Russian police and the FBI made a raid on a downtown apartment today, netting four teenagers they suspect of being behind the Microsoft breakin. Microsoft spokesman Rick Miller applauded the operation, saying that neighbours tipped off the police after noticing strange behaviour from them.

    "These were all very bright boys - cheerful, helpful and good at their day programming jobs" said apartment resident Canya Bolyevtis. "But last weekend that changed when they started walking around in a daze after an all-night session, as if they had been exposed to some terribly traumatic thing."

    Californian software analyst Rich McGee says the teens were foolish to allow themselves to be exposed to Microsoft source code.
    "Here you have some very bright young guys with some Unix experience suddenly coming into contact with the C source for kernel32.dll. I think they were unprepared for the shock."

    St. Petersburg police chief Konstantin Bolygubov thanked the public for the information that led to the arrests, saying it was the easiest raid he had done in a long time.
    "When we broke down the door, none of them moved," he said. "They were all just staring in horror at the screen of a PC in the corner of the living room."

    --
    --- Hot Shot City is particularly good.
  396. Open source.. assisted? (well, gpl perhaps..) by uncleFester · · Score: 3

    What about the claims by some that M$ uses portions of GPL'd code? If that was revealed in the any sources absconded with, could this not work in open source's favor? Granted, M$ will still take the position the material was illegally obtained (probably rightfully so) and try to supress it (fat fscking chance). This could give the free software movement some justifaction for its model and some teeth for any legal wrangling they felt they should do.

    just a thought...

    --
    -'fester
    1. Re:Open source.. assisted? (well, gpl perhaps..) by Fat+Lenny · · Score: 1
      oops, misread your comment (a week later)

      --

      --

      --
      fat lenny's gonna lick your brain today.

    2. Re:Open source.. assisted? (well, gpl perhaps..) by Fat+Lenny · · Score: 1
      If that's the case, how were Linda Tripp's illegal telephone recordings considered admissible?

      --

      --

      --
      fat lenny's gonna lick your brain today.

    3. Re:Open source.. assisted? (well, gpl perhaps..) by Schwarzchild · · Score: 1
      Of course, but Linda Tripp was also going to be prosecuted after the whole Lewinsky fiasco because she broke the law by taping Lewinsky in the first place without her consent.

      So yeah, while the evidence might be admissible to a court the person who collected it is certainly going to be in hot water.

      --

      "sweet dreams are made of this..."

    4. Re:Open source.. assisted? (well, gpl perhaps..) by hrieke · · Score: 1
      Off topic here:
      You answered your own question: Linda's tapes where considered admissible in Clinton's case.

      --
      III.IIVIVIXIIVIVIIIVVIIIIXVIIIXIIIIIIIIVIIIIVVIIIV IIVIIIIIIVIII...
  397. Post removed with second article by l33t+j03 · · Score: 1
    Obviously this cannot be possible. I'm suprised Slashdot would fall for such a contrived story! This place is really going downhill.

    MS couldn't possibly be hacked. Why not? They have no Unix based machines! They are an NT only shop and are thus secure against any type of attack. Only Unix boxes can be hacked because they were not designed on a decent security model (as evidenced by the Morris Worm). NT has been designed to provide Enterprise level security.

    Gotta cut the lecture short for today, I'm off to ddos some stuff to simulate the Slashdot effect. Don't believe And0ver pays me to ddos servers to simulate the Slashdot effect? See here!

  398. Re:s/NT/stupidly trojan-enabled software/ by mindstrm · · Score: 2

    NT *does* have a proper security structure, even moreso than Unix does.

  399. The REAL story behind the Microsoft break-ins by wallk_in_columbus · · Score: 1

    I just found this on the web at the site for the MicroSloth Gazette
    and thought I'd repost it here. It definitely sheds a different
    perspective on things. You can find the original article at:
    http://www.microslothgazette.ru/articles/business/ 20001027/ms_hack_2000.htm
    or
    http://222.173.190.239//mad_cow_disease/bad_burger s_infect_redmond.html

    Let us hope that the hackers / crackers, or whatever they
    desire to be called, do not decide to release the Microsoft
    code to the rest of the world thereby infecting the worlds'
    programmers. After reading this, I believe that to do so
    would set the software industry back 10 years and should
    thus constitute an act of terrorism.

    Apologies in advance if lines wrap weird; blame it on this
    being my first post here.

    Note: Some of the words or phrases are trademarks of somebody.
    All others are open to the highest bidder.

    -wallk_in_columbus

    P.S.- I'm posting this anonymously, because this is not my
    real name.
    ------------------------------------------------ -----------------------
    The Real Story Behind Ballmer's Comment
    "our source codes are intact"
    By: Lacey Sheets*

    ----
    * The author's real name. Heh, would YOU choose that name as a pseudonym?
    ----

    2000-Oct.-28--St. Petersburg, Russia-- We at the MicroSloth
    Gazette were cruising the web's leading news portals looking
    to borrow another paper's story when we spotted the title to
    a still unposted article at the Yahoo,Yippee,Hurray!!?! web
    site that described the possible espionage and theft of source
    code at Microsoft.

    What intrigued us about the soon to-be-published story (available at
    http://dailynews.yahooyippeehurray.com/h/nm/2000 1027/tc/microsoft_ballmer_dc_4.html)
    was the comment made by Miscrosoft CEO Steve Ballmer.
    Ballmer said, "I think I can fairly say that our source
    codes are intact."

    Until then, it had been the opinion of some at the MicroSloth
    Gazette that Ballmer was at least somewhat technically astute,
    but this comment left even his staunchest supporters here
    wondering if he really wasn't totally clueless.

    Either Ballmer didn't know that simply copying source code
    would leave it unchanged or he was trying to cover-up
    something. We smelled a story and so we assigned our ace
    undercover reporter, Lacey Sheets to the story in Redmond.

    The following is a full disclosure of Mr. Sheets findings.

    "I arrived at Redmond at 8:05AM Pacific time. By 9:00, I had
    contacted our Microsoft mole and planned to meet him for
    a late breakfast.", said Sheets.

    Steven, er, our mole, whose name we cannot reveal lest he get
    arrested and we stop getting these inside scoops, arrived
    incognito disguised as a Linux kernel hacker. Sheets says
    he would not have recognized him except that he still was
    wearing his Microsoft badge. For the remainder of this
    story, we'll refer to our mole as "MS Guy".

    Sheets: "Well, Steven whose last name I had better not reveal, what's
    the scoop at Microsoft?"

    MS Guy: (nervously looking over his shoulder, and then smelling under his
    armpit): "The inside rumor is that our CEO is not revealing the
    whole truth."

    Sheets: "What do you mean? Is he simply lying or is he just planning to
    run for office?"

    MS Guy: "Well, for instance, the official report released to the press
    says that there was some 'unusual behavior' in the security
    protocols that we use in terms of the network and that's
    when the security team started the whole investigative process.
    But I have some friends down in QA and they told me that's a
    bit misleading. The security people did not really did not see
    passwords going outside of the Redmond campus. What made them
    suspicious is that suddenly the Windows 2000 Kerberos actually
    started inter-operating correctly with Kerberos servers on some
    UNIX hosts that are used for incompatibility testing. Of
    course, a few weeks before that, the QA team had become
    suspicious since Windows ME was only crashing half as
    much as expected."

    Sheets: "I see; and that led you to proceed, how?"

    MS Guy: "Well the security team was called in and what they
    discovered is not pretty. Are you sure that I will
    remain anonymous, as an undisclosed source?"

    Sheets: "Well, yes, Mr. B... Er, sorry, I'll be sure to erase that
    from my tape. Not only that reference, but, we hope your
    source code as well."

    MS Guy: "Okay, I believe you. I'm just nervous that's all. Probably
    because you're taking notes using XEmacs on a laptop running
    OpenBSD. I start sweating when I get near one of those, you
    know. Okay [takes drink of water], where was I? Oh yeah...
    the security team started checking audit logs and sizes of
    the files compared to those on our last backup that we did
    two months ago. They found the present file sizes much smaller
    then the backups."

    Sheets: (pouncing with his 'killer' question) "What do you mean?"

    MS Guy: "You know... the sizes for the current files--both object
    and source files--were almost all smaller than they were
    before. And also, we found some of the files were
    completely missing. For example, instead of the seventeen
    different implementations of shell sort functions in six
    different DLLs, there was only one sort routine in a single
    DLL. Someone who had an old copy of Knuth's algorithms books
    identified it as something called a 'quick sort' routine. Also,
    it had a copyright by the 'Free Software Foundation'. Another
    person mentioned it looked like the Gnu Public License. This
    lead our security team to discover that this one function
    not only ran much faster then all of our finely tuned
    shell sort functions--including those handcrafted in
    assembler--but it also appeared to be the same function
    as the qsort function in the GNU libc library."

    Sheets: "I see. So your source code really ISN'T intact, is it?"

    MS Guy: "No, but we ran regression tests and had a 99.9% pass rate.
    The few things that failed were things like case-insensitive
    file names. The hackers seemed to have made FAT into a
    case-sensistive file system. We currently have a team of 40
    engineers repairing that, although we're hoping someone
    can locate those backups of the DOS 2.11 code on 5 1/4 inch
    floppies so we can simply retrieve the corrections from
    the backup."

    Sheets: "Interesting... anything else out of the ordinary turn up?"

    MS Guy: "Well, one unusual thing of all was that all our patch blocks
    had been removed from the source code. That reduced the source
    code size by a factor of 10, but oddly enough, we saw no
    corresponding reduction in the size of the object code. We're
    still looking into that."

    Sheets: "Patch blocks? What are patch blocks?"

    MS Guy: "Ugh, you know, when you write code something you insert in
    the source code to leave room for making later emergency
    patches to the object code." [Illustrates by writing the
    below on the back of his place mat.]

    /* Purpose: Create NOPs in binary code to allow room for
    * future emergency patches. Should be called
    * upon entry of each and every C and C++
    * function in this file. Furthermore, every
    * C or C++ source file should define this
    * function.
    * Version: 1.4
    */
    static void patchBlock(void)
    {
    // patchBlock(); /* Don't call - infinite recursion! */

    // Leave room for patches by inserting NOPs into code.
    // Only use as multiple of 4 ';'s for proper alignment.
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ;
    ; // etc.
    }

    Sheets: "Hmmm; I don't know much about programming, but that certainly
    doesn't look like it does much."

    MS Guy: "Oh yes, it has a very valuable purpose, given that we
    have so many bugs and so many millions of lines of code.
    We just replace these empty semicolons with patches so
    we don't have to recompile everything to fix it. Do
    you know how long it takes to compile 27 million lines
    of C code? A long time!"

    Sheets: "Er, well, I see, I guess... What else did your security team
    notice in their audits?"

    MS Guy: "Well, now that you mention it, in some portions of code that
    was left, but simply rewritten, it was no longer written using
    Hungarian notation."

    Sheets: "Hungarian notation?"

    MS Guy: "Yeah, you know... naming variables after their data type. We're
    required to do that for readability or for some reason like
    that. Actually no one remembers why we use it, but the code is
    full of it and... Here, I'll show you..." [This time writes on
    paper cocktail napkin.]

    /* Copyright - 2000 - Microsoft. All rights reserved. */
    /* Proprietary and not for disclosure. */
    #include "sy.h"

    struct SY *PsySz(sz)
    char sz[];
    {
    char *pch;
    ... [runs out of napkin]

    Sheets: "And that means, what?"

    MS Guy: "Well, you see if SY is a structure for a symbol table, then
    PsySz(sz) is a pointer to a function returning an SY that
    takes a pointer to the first character of a null terminated
    string. See how convenient that is? It's a lot easier to type
    than to say, trust me. And by the way, I'll have to have that
    napkin back."

    Sheets: "Well, if you say so. So with all these changes, I'll bet you
    found all kinds of problems and trojan
    rubbers^H^H^H^H^H^H^Hhorses left behind, right?"

    MS Guy: "Well, so far we haven't. We know the thieves have been in
    for at least two weeks, but they only had a chance to replace
    a few key modules. But incredibly, the QA team have had less
    problems with the system and applications crashing then we
    normally do. In fact, almost 50% less to date. In addition,
    the overall performance has increased by 15%, and for some
    modules, there has been a factor of 10 increase in speed.
    Someone, tried, on a lark I think, to boot this hacked Windows
    ME up on an old Pentium 90 that the cleaning ladies play
    Solitaire on using Windows 3.1, and it actually worked.
    Well, it did until we ran out of memory when we tried to
    run MS Office. It only had 8MB of RAM."

    Sheets: (incredulously) "What, Windows ME booted on a Pentium 90 with
    only 8MB of RAM? Impossible!"

    MS Guy: "That's what I said. I wouldn't have believed it if I hadn't
    seen it with my own eyes. But of course you see my, er, our
    predicament, don't you?"

    Sheets: "Well, not exactly. What don't you spell it out for me in
    layman's terms. Put it so that it's something that even
    programmers who have had their minds wiped clean by writing
    years of Visual Basic could understand."

    MS Guy: "Well, I'm not sure that ANYTHING could be explained that simply.
    But I'll give it my best shot, and with luck, maybe even upper
    management will be able to grasp it.
    It's like this. If Microsoft doesn't restore the original
    software, people will notice the quality improvements, the
    speed improvements, and the smaller memory footprint."

    Sheets: "So?" (My best question, by far!)

    MS Guy: "So? So??? You aren't the sharpest knife in the drawer are you?
    Are you mad? Have you been swimming in the shallow end of the
    gene pool too long?
    If people notice, they won't feel compelled to buy bigger and
    faster computers. And if that doesn't happen, how are we going
    to get people to by our next operating system release? I mean,
    at first glance, it appears that more than 5000 of our known
    60,000+ bugs were fixed by these hackers. It's a good thing we
    caught them in time or it would have been too late. After all,
    we've done focus group studies and we know that people only
    want "good enough" software. They aren't expecting perfection.
    If our stolen source code gets out, it could spell the end to
    Microsoft as we know us. We can't have people think that they
    can get good quality software for nothing though. Where would
    that leave us for Windows ME++? Without an upgrade path, that's
    where. And our stock would crash and I'd have to get a job as
    a rock star. And I don't think anyone wants that."

    Sheets: "Well, Mr. Bal... oops, almost spilled the beans. Not to worry
    though, Steve... a good reporter never reveals his sources."

  400. A little bitch by linuxgod · · Score: 1

    Im going to ignore you, and when i close my eyes, and the re-open them, your troll face will be gone.

    TRolL stamped a$ ignored. M$ users are really pathetic people.


    Ignore the Anonymous Pissant trolls !!!

  401. Re:s/NT/stupidly trojan-enabled software/ by F452 · · Score: 1

    Could be. I've found NT to be incredibly irritating to use as anything but Administrator.

  402. Re: convince media by hany · · Score: 1
    Well, I was quoted here t;/a> about IT crimes in Slovakia.

    I send them links to descriptions of both cracker and hacker but the response was:

    I made all the changes and deletions except 'hacker'. My editors and I don't think anyone would understand the term 'cracker'.

    Well, if they (media) do not use word 'cracker' because nobody understand it then it is obvious nobody understands this word (I do not know much people which when absorbing information from general media use dictionary).

    --
    hany
  403. secret OS source code by 20000hitpoints · · Score: 1

    Here's a concrete example of why secret OS source code makes it harder for developers. I'm so frustrated at this point I feel like trying to find these guys in St. Petersburg and ask them politely if they could answer a few questions.

    Right now I am trying to write an app in Visual C++ that downloads a web page. There's this object called a "CInternetSession". To download a web page, you create one of these "CInternetSession" objects, then you call a method on it to return a "CHttpSession". Okay, fine.

    The thing is, I have to repeatedly download the same web page over and over, at regular intervals. I need to optimize for performance because of other stuff that's going on in this program. It would be simpler and more modular if I created a new CInternetSession every time I download the page. Then I just put all the internet code in one function and be done with it. However, of course it would be faster to create the CInternetSession once and reuse it. Which is preferable depends on exactly how much of a performance hit using creation of a CInternetSession object will incur.

    If I was writing this on Linux, I would just check out the source code and find out exactly what each of these objects do. But since they are "black boxes", I have to either 1) rig up a framework to run some tests 2) muck around searching the web and the microsoft site to see if I can get more info about what these functions actually do or 3) just say "screw it" and pick one and forget about it.

    Guess which choice I'm going with? You got it, #3. Proof positive that applications written for an open source OS have the capability, at least, to be much better quality than apps written for a traditional OS. Whether or not the OS itself is "better."

    --
    Don't post on slashdot. Get back to work.
    1. Re:secret OS source code by jedwards · · Score: 1
      The code for CInternetSession is in

      C:\Program Files\Microsoft Visual Studio\VC98\MFC\SRC\INET.CPP

      with VC installed to the default directory.

      Have fun!

  404. Competition for largest open source project. by Cupis · · Score: 1

    Then again fixing Windows is a pretty daunting task for a million open-source developers

    In related news, Sun have recently released the source code to StarOffice/OpenOffice.

    "According to Sun, this release of 9 million lines of code under GPL is the beginning of the largest open source software project ever."

    Not any more.

  405. Familiarity by meadowsp · · Score: 1

    I'm sure that it is just familiarity, whilst, admittedly the directory specs (SET DEF $1$DUA4:[x.y.x]) can be a bit confusing, conversley stuff like SHOW SYSTEM == ps seems a lot less confusing than Unix to me.

    I know it's practically heresy round here, but I've always viewed UNIX commands as being cryptic for the sake of it.

  406. In Other News.... by VChris · · Score: 1

    An anonymous post from somewhere deep in Russia to comp.so.windows contained a 250MB "patch" to the Windows source code. Improvements include the ability to compile with gcc 2.96, 65K bug fixes, thousands of speedups, and a cute Pengiun silhouette in the corner of the Windows boot up screen. Sources close to Microsoft said that their technicians issued a 'patch -p1', a several hours later went gold with the resulting product. "This is exactly what service pack 2 for Windows ME was going to look like, these folks just saved us the trouble of writing it;" an anonymous marketer at Microsoft said. "Users can expect to see the upgrade in stores in the next month, for a nominal charge of $450."

    --


    The difference between reality and fantasy is a nice soundtrack.
  407. There's a program to do this... by SmileyByte · · Score: 1

    http://www.pla-netx.com/linebackn/news/bsod.html
    --

    --

    h@hh@hh@...@.&.... "You shall not pass!"
  408. Planet Open by rjamestaylor · · Score: 2
    The following is a stretch, but bear with me

    I wonder if this could be the beginning of Microsoft being forced to open its code to major customers (at least)--those that will demand the code for independent review (say, Fortune 500 companies and major governments).
    Along this line I am reminded me of controversial tactics used in the homosexual community to "out" prominent persons publically against their will.

    Is it time to start a Planet Open? A movement to force companies to "open" their wares against their will?

    Such a thing would be illegal--and participating would make one liable to Mitnick-type incarceration (or worse!).

    But, it this inevitable?

    Now hiring experienced client- & server-side developers

    --
    -- @rjamestaylor on Ello
  409. Ok, so I'm paranoid but... by Rocketboy · · Score: 1

    Has anyone considered the upside to Microsoft from this? MS can now (truthfully) say that antitrust action needs to be reconsidered, since -everyone knows- that once something is released to the internet, the whole world has it in minutes. They can claim, with some validity, that since Windows source is 'in the wild', they don't need to be broken up. Sooner or later some Chinese or Ukrainian company will release a Windows clone and all of a sudden they have competition. Kinda hard to argue for antirust relief if that happens.

    Which, of course, makes me wonder: which low-level drone at MS did Bill pick on to give out the first password, and what did s/he do to deserve such a fate? :)

    "Just because I'm paranoid doesn't mean they aren't out to get me."

    mjs

  410. Source shenannigans. by Dr_D00gie · · Score: 1

    Surely the source code couldn't be used for anything other than blackmail?

  411. Its that time again... by James+Foster · · Score: 1

    Hey Billy... Perhaps its time to write another one of those letters to the god damn homebrew community and ask them to stop stealing your software, eh?? Happy Birthday!!

  412. why in the $!@%@$!@ is this +5? by ebbv · · Score: 1


    this is idiotic. there is a little thing called evidence, and M$ would have none of it. nobody would believe such a ridiculous claim, and the fact that you'd make it is evidence of a disturbing amount of paranoia on your part.

    tell me, do you worry about M$ fluoridating the water?
    ...dave

    --

    Think different? I'd be happy if most people would just think...
  413. Re:Should I release the code? by pcwhalen · · Score: 2

    That knocking sound you hear is the FBI at your door. I hear Thursday's desert is stewed prunes at Levenworth. Don't worry, I'll donate to your commisary account.

    --
    Pay no attention to the man behind the curtain with all your metadata.
  414. Re:In other news: MS Switches Internal Servers to by Drestin · · Score: 1

    MS Does, it's pure W2K

  415. Re:s/NT/stupidly trojan-enabled software/ by TheCarp · · Score: 2

    > (and please don't blame 'untrained users' - on a
    > properly configured *nix system, an untrained
    > user couldn't do any harm...)

    That depends on your definition of "harm".

    They certainly can do things like use the same password for your system as they use over unencrypted connections elsewhere.

    Stuff like that can at least open the door to harm. Lets face it - no system is completely bug free - and once someone gets on by sniffing a password - its that much easier for them to use the latest root exploit
    (assuming they need root - last time one of our users had a password sniffed - the guy who broke in just setup an IRC bouncer - fucking looser too - I got the job of logging and monitoring his IRC sessions while we were gathering evidence for the Authorities. Just sat around in IRC all day talking about how "we can take over this channel" or "We want that channel" - get a fucking life!)

    -Steve

    --
    "I opened my eyes, and everything went dark again"
  416. nice by H*rus · · Score: 1

    one small step for a man,...
    "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former."

    --

    - if you love something, set it free; if it doesn't come back, hunt it down and kill it
  417. This explains the Kursk disaster by ch-chuck · · Score: 1

    Some new information has come to light over the Kursk disaster.

    For those with short attention spans, the Kursk was the submarine that blew up and sank in the Artic Ocean killing all 118 on board. The Russians tried to blame the incident on a collision with an unidentified object. However, sonar tapes which recorded the blasts (a small one at first, then a much larger one two minutes later) cast doubt on these claims. A whistle blower within the Russian military has leaked that the crew of the Kursk was testing a new type of torpedo when the accident occurred. It seemed very likely that the test didn't go quite as planned.

    While rescue efforts to save the survivors of the Kursk failed, salvage crews were able to recover a 'Black Box' from the submarine which contained detailed accounts of the events leading up to the explosion. As luck would have it, we got a copy of those tapes.

    It turns out that the submarine crew was trying to load Microsoft Windows on their fire control computer. Their intent was to replace the aging CP/M operating system with the flashier Windows OS. Apparently, the Russians didn't know about the legendary stability problems exhibited by Windows. The log tapes make this painfully obvious:

    Captain: Is the new fire control Windows OS installed yet?
    Seaman: Almost Sir. We just need to finish filling out the registration
    card.
    Captain: Excellent. Soon we will be able to point and click our enemies
    into oblivion.

    [evil laughter in background]

    Seaman: Captain! It is booting! Look, it says "Preparing to run Windows
    for the first time".

    [long pause]

    Seaman: Arrgh! Sir, it wants me to reboot again. That makes the 27th time.
    Captain: Hmmm. This is not encouraging. Go ahead and reboot again.
    Seaman: Aye Sir.

    [another long pause]

    Seaman: Captain, it is up again. It says it found new hardware ... A
    CD-ROM drive and that it needs drivers.
    Captain: Where are the drivers?
    Seaman: On the CD-ROM.
    Captain: You are joking, right?
    Seaman: No Sir.
    Captain: Reboot the damn thing again. I am starting not to like this
    Windows.

    [another long pause]

    Seaman: Sir! It is back! It says it found the Gorby2000 Torpedo and is
    looking for the device drivers. Do we have a driver disk?
    Captain: I do not think so.
    Seaman: I will tell it to use the default drivers.

    [another long pause]

    Seaman: Crap. It wants to reboot again.
    Captain: How many times are we going to reboot today? This is taking
    forever. Our hull is going to rust out before this works.

    [another long pause]

    Seaman: Sir! It is up and this time it is not asking for anything!
    Captain: Really? No device drivers? No registration cards? No user profiles?
    Seaman: No Sir. I think it is ready.
    Captain: Good work. Now click on the fire control icon and let us see how
    this works.
    Seaman: Clicking now, Sir.

    [another long pause]

    Captain: Why does the fire control screen have a dancing paper clip on it?
    Seaman: I have no idea Sir.
    Captain: Hmmm, well try clicking on the menu.
    Seaman: Aye Sir. Let us see;
    Open E-mail, Spam a friend, Mail a Virus, Fire a Torpedo.
    Captain: We will spam a friend later. Let us fire a torpedo.
    Seaman: Aye Sir.

    [another long pause]

    Seaman: It is asking us to load the torpedo and to click when ready.
    Captain: Torpedo room, load a torpedo in tube number 1!

    [intercom:] This is the Torpedo room. The torpedo is loaded Sir.

    Captain: Click on the continue button.
    Seaman: Aye Sir.

    [another long pause]

    Seaman: It is asking for a target Sir.
    Captain: Hmmm, target the Rainbow Warrior.
    Seaman: Aye Sir. Damn! It says the torpedo is low on ink.
    Captain: Click ignore. We will get some ink when we return to base.
    Seaman: Aye Sir. We are ready to fire.
    Captain: Very good. You may fire when ready.
    Seaman: Firing torpedo Sir.

    [another really long pause]

    Captain: Well?
    Seaman: I am trying Sir. Nothing is happening. Wait a minute....

    [a loud explosion is heard in the background followed by screaming on intercom]

    Captain: WTF was that?!?!?
    Seaman: Captain! A new screen has appeared! Outlook Express Fire Control
    has performed an illegal operation and will be shut down. Click 'OK' to
    continue.
    Seaman: Oh my God! The paper clip has died! What should I do?
    Captain: Shut it down! Shut it down!
    Seaman: It is not responding Sir!
    Captain: Try 'CTRL-ALT-DELETE'!
    Seaman: Aye Sir. We are in luck! The task manager is still operating. I am
    instructing the task manager to shut down Outlook Fire Control.

    [another long pause]

    Seaman: The task manager says that Outlook Fire Control is not responding.
    Captain: Well no shit. Tell it to 'end task'.
    Seaman: Nothing is happening Sir.
    Captain: Try 'CTRL-ALT-DELETE' again.
    Seaman: Aye Sir.

    [sounds of frantic pecking on keyboard.]

    Seaman: Oooh! What a pretty blue screen!
    Captain: Holy Shit! Not the blue screen of dea....

    [ KABLAM! A really big explosion. More screaming and the sound of rushing water.]

    The tape ends at this point. During the week long rescue effort, divers
    reported hearing tapping in the form of Morse code coming from survivors
    inside the damaged sub. The rescuers couldn't understand why a group of
    men would spend the last of their strength tapping out "Windows sucks" in
    Morse code. The tapes of the last moments of the Kursk may offer some insight
    into this.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  418. Read the (full) Wall Street Journal Article by beebware · · Score: 3

    It seems michael has forgotten to include the link to the original article on the Wall Street Journal - it's here - login 'slashdot123' passwd 'slashdot123'. Very long, comprehensive and insightful.
    Richy C.
    --

  419. No Security on a Windows Network by hagbard5235 · · Score: 5

    This reminds me very much of a point I have
    frequently made to a friend of mine about
    the security of his network.

    He had claimed that he didn't need to worry about
    security because his networking folks had
    provided a very secure firewall.

    "Really," I said, "Do you have any Windows
    boxes on your network."

    "Yes," he replied.

    "Do they run Outlook?" I inquired.

    "Yes," he replied.

    "Then why do you bother to run a firewall at all?"

    I went on to explain that anyone could infect
    Windows boxes behind his firewall via email
    (which almost every firewall in the world
    is configured to pass). Once infected this
    Windows box could subvert his whole network
    and tunnel anything it needed back out via
    SMTP (we do after all, have examples of
    tunnelling IP via SMTP).

    My friend thought I was nuts. Seems that something similar happened to Microsoft itself.

    Guess I'm not nuts. There is no network
    security on a network which has Windows
    present.

  420. Information from Hackernews by Prolog-X · · Score: 1
    Here (10-30-00 in the archives): contributed by abner and laney
    The weekend did not manage to quell the massive amounts of coverage the Microsoft infiltration continues to garner. Virtually every news organization has its own version of the Microsoft debacle, of which we've provided a sampling below. Meanwhile, we are left wondering why the crown jewels of Microsoft were left at the mercy of passwords. There are all sorts of other authentication technologies that we have no doubt Microsoft will be investigating. Perhaps utilizing the smart card support in Windows 2000 wouldn't be a bad idea. It's a shame it takes negative incidents like this to get people to consider security as a strategic business issue. Shame on you, Microsoft.
    Also Happy Microsoft Day:
    ou've heard it before and you'll hear it again. Threats are evolving. We've seen viruses retrieve and forward passwords before on a large scale, now they are becoming targeted and fast. Threat evolution is something that cannot be dealt with reactively; it must be part of infrastructure planning and design. Today, all attention is focused on Microsoft. The world's favorite target has fallen victim to a password-stealing virus that got a hold of passwords that can access the source code to upcoming versions of Windows and Office. It is unclear whether or not the perpetrators were able to use the passwords to actually access and manipulate the source code, however if the source code was accessed two questions remain. 1. Was the code manipulated in some way that could open the door for later attacks or other problems? Microsoft claims no, the code has maintained it's integrity. Other than to trust Microsoft's word we may never know the answer. 2. Does the ability for a criminal group to view the source code destroy the security by obscurity that is key to so many commercial software products? In the open source community, numerous hackers examine products and contribute solutions to flaws in the products. In the commercial world, many companies rely on their development team to produce secure code and then keep the source code secret to not only protect their intellectual property, but also to minimize potential attacks that could be launched against the product. In this case, the loss of security by obscurity could result in a criminal having intimate knowledge of the product development cycle to be able to develop targeted attacks on future Microsoft products. Regardless of the quality of Microsoft products, the mere fact that the company was able to recognize that this incident occurred is unfortunately unique. Many corporations might never know this had happened to them. In fact the ability to isolate the incident to specific networks or machine is quite difficult in many environments. The other interesting thing going on here is the Trojan horse attack. These attacks have been discussed for several years now and the current solution has been to use content filtering software to detect the attack. If you are one of the world's favorite targets, the Trojan horse writer will write the attack specifically at you. By the time the anti-virus companies know about the Trojan horse and are able to detect and stop it, it's too late. Unfortunately, it has taken a high profile incident like this for awareness to spread. One solution is to seperate general purpose computing such as internet surfing and email from sensitive computing such as accessing source code or controlling IT infrastructure. This is what the military does. They run 2 networks that are physically isolated from each other. A less expensive solution is to keep all executable content from reaching workstations such as executable programs, active HTML content, or documents that contain macros. This is difficult to acheive in reality so physical seperation is the the only way to be sure you are secure. The Wall Street Journal broke this story and pretty much everybody is currently running it. Look for more information and speculation to filter out through the rest of the day.
    Hope this helps.
  421. Its not a computer its an amplifier... by HiyaPower · · Score: 2

    Sigh. That thing on your desk is not a computer. It is an amplifier. If you are smart, it allows you to be very, very smart. If you are stupid, it allows you to be very, very stupid. Outlook allows folks to be very very stupid bigtime. When anyone who has any DP skills at all is in big demand, sooner or later, you will find someone who you have hired that is going to amplify their stupidity bigtime. You don't hand your car keys over to your 10 year old, but many places are doing the equivalent with Outlook, and other M$ products. I personally feel that the risk/reward against a tightly coupled rice-pudding OS/Application model such as M$ brings out. I shed no tears that they have been given a dose of their own medicine...

  422. Whois by lemonk · · Score: 1

    [whois.internic.net] Whois Server Version 1.3 Domain names in the .com, .net, and .org domains can now be registered with many different competing registrars. Go to http://www.internic.net for detailed information. MICROSOFT.COM.IS.SECRETLY.RUN.BY.ILLUMINATI.TERROR ISTS.NET MICROSOFT.COM.IS.RULED.BY.HACKERJACK.COM MICROSOFT.COM.INSPIRES.COPYCAT.WANNABE.SUBVERSIVES .NET MICROSOFT.COM.HAS.NO.LINUXCLUE.COM MICROSOFT.COM To single out one record, look it up with "xxx", where xxx is one of the of the records displayed above. If the records are the same, look them up with "=xxx" to receive a full display for each record. >>> Last update of whois database: Thu, 26 Oct 2000 06:47:54 EDT The Registry database contains ONLY .COM, .NET, .ORG, .EDU domains and Registrars.

    --
    You are only popular on the Internet.
  423. (The sequel) by Anonymous Coward · · Score: 1

    "Have you heard of XYZZY Smirnoff?"

  424. Microsoft adopts open source by fonky · · Score: 1

    Looks like Microsoft is finally becoming serious about open source.
    :)

  425. security through obscurity by mattdm · · Score: 2
    It might not kill them, but it would definitely hurt. They've relied on security through obscurity for years, and suddenly, it's all exposed. If the code becomes public (or, perhaps worse, widely available in serious black hat circles), watch for a *lot* of exploits.

    --

    1. Re:security through obscurity by fredrik70 · · Score: 1

      Ah, true,never thought about that. THough more the line that people thinks it's gonna kill of MS because now everybody can get the source and compile it rather than buying it...
      But yes, your reasoning definetly makes sense...

      --
      if (!signature) { throw std::runtime_error("No sig!"); }
    2. Re:security through obscurity by Znork · · Score: 1

      I doubt the source code hasnt been available in the right circles already. It wouldnt be that hard for a disgruntled employee to burn a few cd's at work and share with friends who spread it around. NDA's arent the same as 'encrypted and viewable only from a secure terminal with no output device'.

      However, it will be interesting to see how many backdoors they installed into the sourcecode of the various microsoft product during their three months of playing around.

      After all, having instant access at will to every machine running the next release of any Microsoft product would be useful for them, I suppose.

  426. Win-Win? Not so sure...(Kevin Mitnick) by Carnage4Life · · Score: 3

    If it's a outside job and the crackers beat MS' secuity, now the whole world+dog knows that MS software sucks in protecting data.

    From all the articles, it looks like this was a Trojan that may have been secreted during the execution of some email attachment. Knowing MSFT, they'll probably spin this as a virus similar to Melissa or ILOVEYOU and the general public will stop blaming them.

    After all, no one is calling for their heads after Melissa and ILOVEYOU even though the main reason they caused so much damage is the lack of security built into Outlook and the ease of using Virus Building Script. Instead we'll probably get a lot of hacker crackdowns with this breakin, perhaps another Kevin Mitnick type case where he got reamed for seeing Sun's Solaris source. It's very possible to see the culprits doing massive jail time for supposedly causing MSFT zillions of dollars in lost revenue by merely looking at the source like Sun did with Kevin Mitnick. This is especially possible in the current climate of UCITA and the DMCA. I wouldn't consider that a win, would you?

    Second Law of Blissful Ignorance

    1. Re:Win-Win? Not so sure...(Kevin Mitnick) by jafac · · Score: 2

      Oh, there's TONS of security built into Outlook, and VBS is not a threat to someone who knows how to set things up right. There's all kinds of deeply buried dialog boxes and registry hacks that can put a stop to this stuff.

      But for 99% of Outlook users out there who use the defaults, (and NONE of the features that the defaults enable) they're screwed.

      --

      These are my friends, See how they glisten. See this one shine, how he smiles in the light.
  427. Sniffing Passwords?? by John+Cats · · Score: 2

    Bah humbug!!

    When are people going to learn to use SSH???

    I use it on my own local network at home, even behind my "invinsable" linux masq gate.

  428. Wow. by mindstrm · · Score: 2

    All it says is they had access to stuff... and sniffed passwords. What evidence do they have that these 'blueprints' were stolen?
    And they continually talk about whether stuff was modified.

    And they think that this might be a 'data hostage' situation.

    Hardly. I think said hackers would simply distribute the source around a bit then post it to usenet. THAT would be cool.

  429. Re:/. edit box (Was: See what happens when you...) by tagish · · Score: 1

    You're allowed to use your editor of choice and cut and paste...

    --
    Andy Armstrong
  430. Re:/. edit box (Was: See what happens when you...) by Nightlight3 · · Score: 1
    Are you saying to reply, one should switch to desktop, launch an editor, keep switching back & forth as needed to reply in the context, then when all is done, issue 'select all' command in the editor, then do the cut, then switch to the browser, then paste from the clipboard into the browser, then switch back to the editor, then click close on the editor window, then reply to the editor dialog box that you are sure you don't wish to save anything. And then multiply everything many thousands times for all the posters here. Just so we could spare the poor web designer the trouble of having to try out her creations, so she can concentrate on 'stuff that really matters', say, her H1B forms.

    Now there is an elegant solution. Who would have ever thunk of that. Well, it is true, human is an adaptible animal, he can get used to anything if he applies himself.

  431. MS releasing anti-virus products? by WildBeast · · Score: 1

    I think I got it, it's all a marketing strategy. Okay I have no clear idea of what MS is trying to prove by making that announcement. But after all the interviews and tests to pass to work as an MS programmer, it'll be unlikely that a programmer was dumb enough to open an attachement especially if he doesn't have any anti-virus software installed. If that's true, such an employee should be fired and MS should re-think their hiring techniques. Or maybe MS is planning a good excuse to go Open Source?

  432. Re:Funny? Learn to moderate! by gle · · Score: 2

    Local root exploit are quite common, and tend to be fixed late compared to remote root exploits. Some admins think they should only mind about remote exploits because they trust their users.
    Statistics show how wrong they are. And even if you can trust your users, can you trust what they get in the mail?

    ____________________

    --
    Ni!
  433. Good Samaritans... by Yousef · · Score: 2

    What's with all the negative noise here!
    They were probably well intensioned Hackers trying to fix bugs in M$ code!
    They can't legally see the code, so they did the next best thing!

    --
    -- "To ask a question is to show ignorance; Not to ask a question means you'll remain ignorant."
  434. This seems to be happening a lot more lately... by Oztun · · Score: 1

    This is exactly the same thing that happened to AOL a few months back. A trojan opened up a connection from the inside of the company.

    Working for a blue chip company I can tell you that users are responsible for virus protection here (and very few use it). Are there any IDS systems that detect these trojans?

    If the trojan sent out an encrypted email it would make finding it very difficult. I'm sure they just establish a connection through port 80 or some other common port. When I was an exchange admin. we caught trojans incoming on the server before they got to users.

  435. Danger! by Max+von+H. · · Score: 2

    If the Windows and Office source code starts circulating around, coder may just start coding stable apps and improve it since they'll have access to *everything*.

    Bah, some dude in Scandinavia or Russia will release an open-source distro of Windows and we'll all end using and praising it... Imagine that, the Ultimate Revenge(tm)! MS forced to embrace OSS or else they die! Haha! Some are already creaming their pants, I know that for sure.

    Linux is in danger!

    /max

    --
    -- It's always darker before it goes pitch black.
  436. Source code changed? by zelyan · · Score: 1
    Miller said there was no evidence to suggest that any source code had been modified or corrupted in the attacks. But the company couldn't say one way or the other whether source code had been stolen

    In other news, the Windows Development group reports fewer bugs and longer uptimes than ever...

    Jeff

  437. Initial breakin was via email trojan by divec · · Score: 3

    From what the MSNBC article said, the crackers initially got access because some poor MS employee inadvertantly ran a trojan email attachment, then did some sort of password sniffing.


    It should now be completely clear that attachment-running programs such as Outlook are dangerous and should not be used by any business which has sensitive data, i.e. any business at all. Any business which jeapordises my personal privacy by using such software is acting negligently, just as if they left their locks unlocked and their safe open at night.


    I wish I could say that this marks the beginning of the end of such "back-door enabled" software. However I fear that this will not be the case.

    --

    perl -e 'fork||print for split//,"hahahaha"'

  438. Damage to MS already poor reputation by pjrc · · Score: 2
    We all suspect (know) that windows is full of nasty security holes. Whoever's got the code could do a lot of damage to MS by finding problems and/or writing exploits to windows and releasing them to script kiddies, one after another... timed to keep MS in the news for one major security problem after another.

    Of course, this seems to be more or less happening naturally without the source!

  439. The Linux security modem *IS* weak. by Nailer · · Score: 1

    The Linux security *model* is weak in comparison to NTs. It's just that NTs is more easily circumvented. If Microsoft plugged the holes a little more, NT security would theoretically be better than Linux.

    RWX permissions offer no fine grained control, and should have been abandoned years ago. There's absolutely no reason Linux should be using this security model besides legacy support. The hazards outweigh the advantages.

    Unix provided the basis and way of thinking for most modern operating systems. Some, [or even most] brilliant OS ideas came from Unix. But rwx permissions wasn't one of them [neither was the backspace/delete difference]. In fact, rwx permissions often mean things end up being less Unix like. POSIX even has provisions for ACLs.

    On of the Unix fundamentals is that many things should be represented as files. Another is that of code-reuse, and uniformity. But since rwx permissions provide such pathetic granularity in security, many applications, such as Squid and Samba are re-implementing their own security models because the current system is to basic. This is both a kludge and a security risk - more implementations mean more fronts to fight crackers on, and makes things hard to manage. Most serious level DOD certifications require the use of ACLs [among other security measures, like Domain Type Enforcement and Capabilities].

    Another example would be firewalling. Let's Unixify it - make it into a file. Set ACLs on /proc/ports/incoming/8080, and /proc/services/http [for stateful inspection]. The user gets the most restrictive permission applied to them. There's probably flaws in that system [it was thirty seconds of brain work], but the concept remains.

    rwxs is pathetic. Multiple security implementations on one platform is a kludge. People using an account which has full access to the system is a security risk - let's distribute administrative load to priviledged accounts. `root' sucks. Sudo is a kludge. Deal with it.

    Yes, implementing ACLs on Linux will break things, but so has a stack of other things [the change in binary format, various GlibC bits and pieces]. In those instances the benefit was worth it, and it will be again.

    Works already been started. Get involved. ACLs for Linux 3.0 If you can think, stew about it with compatriots on your mailing lists. If you can hack, then take the time to look at some of the work and discussion by hunting for Linux ACLs on Google. If you have a project, think about the security implementation, and design with the future in mind. If you work for any company that wants to see widespread corporate use of Linux [which is assisted by shiny things like DOD certifications], then fund the damned think. And thanks for listening - especially if your name is Alan, Richard, Theodore, or Linus.

    POSIX ACLs for Linux 3.0, let's do it.

  440. Re: hacked? cracked? by Kyaphas · · Score: 1

    Yep, just like every story published out there did.

    You and I and probably 99% of the readers of this site can differentiate between the two, but the media can't/won't. Why waste your time preaching to the choir? Try to convince the media. 'course you'd probably have more productive results converting lead into gold.....

    Personally I've given up on the VERY old argument of hacker vs. cracker. I have better things to spend (ok, ok, waste) my energy on.

    --
    ---- The price of freedom is eternal vigilance. -Thomas Jefferson
  441. Re:s/NT/stupidly trojan-enabled software/ by mindstrm · · Score: 2

    ? I don't get it.
    YOu can select 'run attachment' from just about any mail client. How is this bad? It's a USER CHOICE to execute something mailed to them.

    Whether or not it's a script is not the point.

    I agree, it was stupid to have scripts that executed off a single click (a-la those trojans a while back)... so you didn't have time to think...

  442. Re:You can do this in Windows too. by AFCArchvile · · Score: 1
    Just type in "nslookup" in the Run dialog or in a DOS box.

    You'll be issued a ">" prompt. Type in the domain name (e.g.: "authorize.quake3arena.com", "slashdot.org", etc.). The IP address of the domain name is returned in the very last line before the next prompt.

    --
    "Ancillary does not mean you get to rule the world." --U.S. Circuit Judge Harry Edwards, speaking to the FCC's lawyer
  443. Evil Disk Drives by SubtleNuance · · Score: 1

    but the real culprit is Outlook.

    How do you mean its outlook - any program which makes its way onto a Windows computer has the opportunity to do this. A diskdrive is as big a security hole as is Outlook. Period. You dont need Outlook to do this. Patching outlook to not receive attachments will not solve this problem.

    We could write a prog which used whatethehellever *.DLL offers the API to send email. If some goober executes any code on a Windows computer it can do anything it pleases. No one will argue differently - because the OS has NO INHERENT SECURITY

    Re-writing Windows is necessary to fix it.

  444. New business oportunities in St. Pete VC needed. by Anonymous Coward · · Score: 1
    St. Petersburg programmers are quire good, every year a team St. Pete students win the international programming competitions. Some then go on to other things. Like the attack on Citibank.

    Well if you want to invest in St. Petersburg check out the web site. They have a VC forum called "BRAIN" that was launched yesterday. Just look for any interesting new projects for a "Windows-like Operating System" or a "Fully capable Office equivalent" for Linux.

    The guys who have stolen the code are going to be in deep dodo. There are people in St. Pete that Redmond can place under contract who don't know that "Terminate and Stay Resident" is to do with computers. This kind of 'service' can be obtained for less than $1000.

    However once a trade secret is disclosed, life gets very difficult for the owner of the secret. No business advantage.

    Anyway, when I'm nect in St. Pete I'll ask them if they have and Windows Source CDs at the black market. The binaries sell there for $2 per disk.

  445. Re:s/NT/stupidly trojan-enabled software/ by Nos. · · Score: 1
    True, but any decent admin will tell you that unless you absolutely have to be logged in as administrator or root, you don't. On any box I've setup (mostly linux) all mail to root will go to another user account.

    On the servers at work (NT), admin NEVER checks email, and is almost never logged in. The superuser account would never run any unchecked binaries period. If I get a questionable attachment (happens pretty regularaly), I forward it to a dummy user account that has no rights. I also keep my virus scanner up to date. If you're going to run one that's 3 months (or older), then don't even bother!

  446. All of a sudden by overshoot · · Score: 4
    --
    Lacking <sarcasm> tags, /. substitutes moderation as "Troll."
  447. Change is good by Mumble01 · · Score: 1
    During the three months in which the hackers had access to the code, there is a remote chance the software could have been altered, Microsoft told the Wall Street Journal...
    Cool! Maybe they fixed some bugs...

    Then again, nah. Microsoft probably used source control to remove the patches...
  448. Did you even read the article? by Roofus · · Score: 1

    If you read any of the above articles before posting, you would know that there are several uses for it.


    1) Use the source to find out what new features are being added into windows, this can be used by competitors to either get their products compatible before others, or add features into their product before MS adds it directly into Windows.


    2) Try to sell it back to them


    3) Compile a "Warez" version of Windows (haha yeah right).


    Anyway, there have got to be more uses for it than this. One post above mentioned putting it on Havenco and letting the world read it :)

    1. Re:Did you even read the article? by Nicolas+MONNET · · Score: 2

      But who are the competitors?


      --

  449. Re: hacked? cracked? by hany · · Score: 1

    "... getting hacked just as we face more and more legislation against hacking."

    ... while again someone used word "hack" instead of "crack".

    --
    hany
  450. Re:This could be the greatest thing to happen sinc by Hawks · · Score: 1

    as of last check, 11:02EST, MSFT was up over 2points. This just proves, to me anyway, that wallstreet is as delusional as Bill G.
    Hawks
    "Developers are the redheaded bastard step children of the computer world",

    --
    in anima Apparatus
  451. Send the code to the guys doing WINE! by jqs · · Score: 1

    Yeah, then their emulator will be great.

  452. This virus has been known since August! by pcwhalen · · Score: 2

    And MS didn't pick this up? On August 14, 2000, PC Mag ran a story on this trojan and only rated it a 5 out of 10 for harmfullness. WTF?

    --
    Pay no attention to the man behind the curtain with all your metadata.
  453. It's Not too serious ... by PhilHibbs · · Score: 3

    It's not as if they stole anything valuable, is it?

  454. Perhaps... by jqs · · Score: 1

    They will document all of the 'secret' API calls and publish them so that the non-M$ world has a chance for developing WinApps...

  455. Microsoft stock is rising by Ektanoor · · Score: 2

    Has anyone take a look at MSFT stock chart? It's rising!

    Well Windowzers nothing to worry about. It were Microsoft partners who sneaked the code.

    Microsoft partners:
    "AAAAAAAHHHhhhhhh. AT LAST!!! Now we can get a look at that dumbiness of kernel exception that has been segfaulting our code for 10 monthes and get a fix for it...

    Hello? Mr. Investors? We finally get a solution to our problems. This time code will be stable and fast. Soon a new set of fresh killer-apps will be on the market. So Windows will still live for some time...

    Investors:
    Ok Dealers NOW you can buy some of that M$ stock."

  456. Poetic Justice by Nick+Driver · · Score: 1

    Now MS gets to know and understand, firsthand experience, just how negligent and slipshod their products are designed which allow too easily the insertion of backdoors via automatically executing email attachments. I have no pity.

  457. Email trojan by DeathBunny · · Score: 1

    I'm surprised I haven't seen an messages in here about the REALLY funny and ironic part of that story.... It was an *email trojan* that allowed the crackers to get access. The exact weakness that everyone has been bitching at Microsoft for months about (ever since ILOVEYOU and MELISSA).

    This *should* (but probably won't) make it clear to everyone why email trojans are really dangerous! (particularly for MS-OS's!!

  458. This could cause MS to turn to Open Source... by KlausBreuer · · Score: 1

    ...especially as all the work is already outsourced >:)
    ---
    "What, I need a *reason* for everything?" -- Calvin

    --
    Free PC version of ChipWits at http://www.breueronline.de/klaus/chipwits/
  459. How long by hagbard5235 · · Score: 1

    How does Microsoft KNOWN that the hackers
    have only had access for three months?

    I have yet to hear how they are establishing
    this claim (which is largely how they are
    defending themselves from suspicion of their
    code base being corrupt).

  460. Re:Now that is some funny shit. by CoderDevo · · Score: 1

    Yeah, except this joke is older than Microsoft and used to circulate at IBM for their OS's.

    Old, old, old and tired joke.

  461. Waaaaaaaaaaasssssssssup? by billybob2001 · · Score: 1
    I just logged in as slashdot123/slashdot123.

    No problems. Why all the bitching?

  462. So what by crazyfrenchmen · · Score: 1

    Linux source code have been available for a long time and nobody is worried . Is microsoft worried that people will realise how crappy their code is if they see it?

    --
    "Failure is not an option, it come bundled with the software"
  463. Sounds like a great idea! by Chelloveck · · Score: 5

    Ah, yes, evil hackers from Russia stealing the "software blueprints". Smells like the plot of a James Bond movie.

    "And now, Mr. Bond, by altering the blueprints I will be able to take control of every desktop computer on the planet! I'll have an entire cybernetic zombie legion at my disposal!"

    "We're one step ahead of you, Smirnoff. Office is a very fragile piece of code. Change even one line and the whole thing will come crashing down like a house of cards. The worst you'll be able to do is crash every computer. And who would be able to tell the difference between that and the way Office normally runs, eh?"

    "Curse you, James! Now I'll have to kill you by an incredibly intricate device which you'll no doubt escape. The only way out of your cell is to cross this tile floor. Land mines are hidden under nearly half the tiles. Fancy a game of full-contact Minesweeper, Mr. Bond?"

    --
    Chelloveck
    I give up on debugging. From now on, SIGSEGV is a feature.
  464. The best link (irony) by billybob2001 · · Score: 2
    is at http://www.msnbc.com/news/481927.asp

    We are confident that the integrity of Microsoft source code remains secure.

  465. One thing to look forward to... by Tommy+At+Work · · Score: 1

    The next stable release of Wine should run the entire Microsoft Office suite pretty nicely...But don't use Outlook, you wouldn't want a nasty email attachement getting through...

  466. Remeber the Microsoft Ad? by kruczkowski · · Score: 1

    Remeber the Mircosoft ad that was posted on /. a few days ago.

    --
    hmm... for fun I enjoy launching DDoS attacks against 127.87.42.5
  467. CNET header by Nate+Fox · · Score: 2
    Seems funny to me that CNET would file this story under

    CNET : News : Entertainment & Media : Story

    -----
    If Bill Gates had a nickel for every time Windows crashed...

  468. I would like to address somthing... by linuxgod · · Score: 1

    I would like to say that if M$ can't protect their own data, what makes the end-ms-user think he can do it better? All those people out there running M$ products are probably crying their heads off, becuase they know they can't protect their own data.

    I had to ask this question, and im sure many of you are probably asking the same thing. 2000 is a poorly built OS, I hope whoever stole it will take it and build it better.


    Ignore the Anonymous Pissant trolls !!!

  469. MS shares by MartinG · · Score: 2

    Okay then..

    With this news in mind, can someone explain why MS shares have gone up nearly 5% so far today?

    --
    -- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz .@adgimnoprstu
  470. Endemic by chuckw · · Score: 1

    This is endemic to Microsoft. Take this quote for example:

    "Thursday, people familiar with the case said the company was meticulously examining every computer file on the compromised network that was modified for any reason during the preceding three months."

    And exactly how would one know which files had been changed within the last three months? If a system is compromised, one must assume that ALL files have been maliciously modified unless they have some sort of secure checksum app like Tripwire. Backup tapes should not be trusted either. Who knows if you were backing up altered data...
    --
    *Condense fact from the vapor of nuance*
    25: ten.knilrevlis@wkcuhc

    --
    *Condense fact from the vapor of nuance*
  471. brrr... code outside by xdc · · Score: 1

    If the code for Microsoft's products -- especially OSes such as Whistler -- gets out, then you could expect to see bogus alternate versions making the rounds. Unsuspecting warez kiddies could be installing copies of Windows that contain trojans galore. Some of this bogus software would surely find its way onto a few company networks, which would then be vulnerable to any number of creative exploits. That is, even more than the usual ones that IE so generously affords.

  472. code by jbarnett · · Score: 1


    So do this mean we will start seeing t-shirts with MS source code on it, like DESCSS (whatever it is) code?

    That would be cool.

    I want a full body suit printed up with Windows ME code.

    Uh um, I take that back, some Linux zealot might hit me with their car..

    I am a Linux zealot FTR. I don't hit people with my car (on purpose) any more.


    --

    "`Ford, you're turning into a penguin. Stop it.'" -THHGTTG
  473. (-1, Gross Stereotyping) by festers · · Score: 1

    You know, your post would have been +5 in my book if only you had left out the generalization of all Slashdotters. This is one comment out of 400+ so far. One. Go ahead and flame that loser back to hell, but don't you dare lump me (and all the other sensible people here) in with that kind of crap. Appealing to some false majority won't get you anywhere...


    --------

    --


    -------
    "Every artist is a cannibal, every poet is a thief."
  474. Going to affect everyone by Jon+Erikson · · Score: 1

    As someone in the IT consultancy business I can tell you now that this is going to send a lot of shockwaves through the ranks of middle-managers and CTOs who consider themselves tech-savvy because they know what IIS and how to add a new printer to their machine.

    Microsoft has always made a big point of claiming that they run their own products to ensure rock-solid reliability, which is why they recently moved Hotmail over from BSD to Windows. But now, people are going to worry, and it's going to affect the whole industry, not just Microsoft. Confidence will be eroded, and the only winners will be people like me who advise on setting up mission-critical platforms in exchange for large amounts of $$$.

    But what of the missing source code? This gives Microsoft a huge weapon with which to engage in legislative and legal warfare with evil hackers who were involved in this backdoor penetration. There's already a fear of cybercrime in the air thanks to people like Eric Corley who consider it to be 1337 to give away people's secrets and break the law, and this is going to fuel that fire.

    Microsoft can sue anyone who looks like they have a copy of their code (Wine), and what are they going to do? Nothing, open source can't compete on this level unless it incorporates itself under law, and the pseudo-communistic rantings of gurus like Stallmann will prevent this from ever happening.

    Well guys, see you in court.

    --

    Jon Erikson, IT guru

  475. Re:No Security on a Windows Network by bockman · · Score: 2
    I'm just waiting for the first "for-newbies" distro (oh, wait, Corel comes to mind )

    Actually, when I tried out the network edition of Colel 1.0 ( the one you find on magazines and on the 'Net), I was astonished to find out that the installer did not ask for root password ( I guess it was considered too complex a concept for newbies to grasp). As a result my box was perfectly installed - and anybody could became root with no password.

    Not a big thing, for a unix/linux user - but I would not be surprising if Corel users are still surfing the Net without protection for their root accounts.

    --
    Ciao

    ----

    FB

  476. That pesky NTFS fs by Skruffy · · Score: 1

    Maybe we'll finally get some NTFS drivers that don't trash your filesystem. I hope these guys do post it.

    --
    --- If something doesn't feel right, you're probably not feeling the right thing.
  477. oh oh I think I got it by WildBeast · · Score: 1

    yep I got it. MS will soon be releasing their own Linux distribution. Many of MS employees have been pushing for it. And after all the studies, MS finally realized they may be able to make money with Linux.
    Whistler : Looks good, newbie friendly, great features
    Windows Server : Rich with features, easy to maintain, easy to use, great for small businesses and some big ones
    MS Linux : an OS for security conscious people, great as a webserver, firewall, router, etc.

  478. Microsoft Code on T-Shirts by BuyMeASportsCar.com · · Score: 1
    Maybe the hackers will sell T-shirts with the acquired code on it. With Microsoft's bloatware, I guess the shirts would come in only one size.
    XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXL

    Michael
    http://www.buymeasportscar.com

    --
    http://www.buymeasportscar.com
    No, really! I'm serious!
  479. Windows = Secure? :)) by Ulky · · Score: 1

    Nice to see Bill finally being shown how unsecure Windows really is.

    If nothing else i hope this incident will get microsoft thinking more about system security in the future.

  480. s/NT/stupidly trojan-enabled software/ by divec · · Score: 4
    Um it was not about NT you fool.

    No. It's just about the software which comes with NT and Microsoft sells for NT and everybody uses on NT. An equally stupidly-designed UNIX mail reader would be equally bad. But most UNIX systems don't use such software.
    --

    perl -e 'fork||print for split//,"hahahaha"'

    1. Re:s/NT/stupidly trojan-enabled software/ by fwr · · Score: 1

      The problem is that Windows has no easy way to do the equivalent of su. Sure, there are some utilities in the resource kit to create a "dos box" that has Administrator rights, but it's kuldgy and a hack. Horrible to work with and nothing similar to the elegance of logging into a Unix box as a normal user and using su to temporarily change to root to instal software or do necessary system administration. That's why a lot of Windows admins run as Administrator. Not because they want to, but because the base tools provided kind of force you to (remember, the resource kit was not a "free" download last time I checked). Now, it may just be ignorance, but an OS that obsfucates and makes it difficult to find out how to administer a box securely doesn't seem to have security high on the list of priorities, does it?

  481. Re:/. edit box (Was: See what happens when you...) by F452 · · Score: 1
    Personally I don't think the default box is so awful. And also IMO, switching to another editor isn't so horrible as you describe. Anything can sound plodding if you describe it in your terms:

    Are you saying that first I have to inhale, and then exhale, and then inhale, and then exhale again, and then think about what I want to write, and then move my hands to the keyboard, and then start typing, and then hit the backspace key when I mis-type, and then keep moving my eyes back and forth, and then shift my feet under my chair, and then remember to breathe again, just so I can respond to some inane post on slashdot...

    Still, you have a point that we could improve the interface rather than make other people accomodate. However, HTML forms are rather limited which makes the interface designer's job difficult: What about those with 640x480 resolutions for example? The comment box looks a lot bigger on their screens.

  482. This could be VERY bad by Kyaphas · · Score: 5

    Just what we need. A high-profile company that has decent lobbying skills getting hacked just as we face more and more legislation against hacking.

    And this on the hells of the story below about pushing for more UCITA support. crap.

    --
    ---- The price of freedom is eternal vigilance. -Thomas Jefferson
  483. Posted MS Source == MS excuse for extortion by bear_phillips · · Score: 1

    Lets see, if Microsofts source code is posted all over the web, Microsoft would start a massive campaign to protect its intellectual property. 1. MS goes through StarOffice, KOffice, AbiWord code. 2. MS states that your "search and replace" code looks just like our "search and replace" code, you must have used our stolen code. Please remove it now. 3. MS gets a judge to believe that other closed source programs contain stolen MS code. Judge allow MS to view the closed source code. MS uses that info for all kinds of bad stuff.

    --
    http://www.windmeadow.com/
  484. Who knows.... by testcase · · Score: 1

    Maybe they were just trying to figure out how to make the paperclip go away?

  485. Segfault Coverage by Diskore · · Score: 2

    Segfault has some underreporte d details in its coverage :)

  486. This is bad news by dvd_maximus · · Score: 1
    The MSNBC report says, apparently with a straight face:

    While there is no evidence that any changes have been made to the [MS source] codes .... any unauthorized alterations to Microsoft's products would raise broad questions about the trustworthiness of some of the world's most widely used software applications.

    Right. Because they've always been so reliable and trustworthy until now.

  487. Umm... so has everybody been rooted now? by roystgnr · · Score: 2

    It doesn't look like it; the news articles seem to imply that it was just some low level accounts cracked and just read-only access to anything important. (Yeah, like they could slip an extra bug into Windows source code and anyone would notice)

    But that wasn't my first thought. That headline, "Microsoft cracked", is terrifying! Are all the Windows users here keeping their systems up to date? If you aren't, you're probably vulnerable to the new "Win9x doesn't always check whole SMB passwords" bug, the old "malformed IP packets confuse the hell out of Microsoft engineers" bugs, or a whole plethora of Outlook exploits (including a buffer overflow when email is downloaded, so turning off previewing and javascript won't help).

    But if you are keeping your Windows box up to date, then you'll be one of the hundred million computers that get 0wn3d by the first person to crack windowsupdate.microsoft.com and stick in a trojan. This isn't just a Microsoft problem, of course; every OS vendor (even taking the broadest definition of "vendor" for Debian people) keeps their repository of updates, and all the good ones have an easy way for users to sync with those updates.

    I still think that Windows Update, and the idea of autoinstalling security updates from vendors in general, is a good thing; it certainly beats having millions of exploitable computers hanging off the net. But that central download source then becomes a central point of failure for your operating system security; God help us all if Microsoft ever really gets cracked.

  488. It's funny ya know by crivens · · Score: 1

    It's funny that none of the articles raised any issues of how this affected any networks that relied on MS servers for security. They all managed to pick up on the industrial espionage quote though.

  489. maybe just maybe by martin · · Score: 1

    M$ will now overhaul their security architecture (yeah I know alot of poeple think don't have one).

    It will also make many of their customers think carefully about implementing a proper security policy as well.

    IMHO this will be a good thing for the world as M$ will finally have to do something more than just issue patches...

  490. Stupid Human error or do they know for firewall? by loncarevic · · Score: 1

    Bottom line of this event is human error.

    It doen't matter what OS are you having AFTER Firewall as long as stupid human error is not involved in "Network Design".

    Human error is main issue here, you may ask why? Simple, if you are Network Admin of Microsoft Network you are really stupid if you leave enabled direct communication between WORLD and local host on network (remember official story of how breakin happened, trojan -> connection from NET -> spread deases...).

    What happened with "Bastion host(s)", "Demilitared zone", "Network Address Translators", etc.

    Igor Loncarevic

  491. Re:/. edit box (Was: See what happens when you...) by Nightlight3 · · Score: 1
    However, HTML forms are rather limited which makes the interface designer's job difficult: What about those with 640x480 resolutions for example?

    One can customize here anything one can think of, and then some, when dealing with displaying the threads. That component is one of the better thought out than any I've seen. It doesn't seem beyond the current technology to have an extra checkbox on the customization screen to select small or large edit box. And if the author of this component really gets creative, some day we even may get the medium size option, too.

  492. is this all created by ms themselves ?? by meatburger · · Score: 1

    How many of you out there have considered this to be all one big Microsoft conspiracy ?? think about this: Microsoft are facing the DOJ about their monopoly and so forth. Microsoft may have even gone as far as to release a dodgy version of it's source code, and setup for a "hacker" group to download it. (whether this "hacker" group are employed my MS ??). If this dodgy version of it's source code gets out ... then when Microsoft appeals to the courts, they will try and rule the case obsolete, as all the company secrets and source code are out. ... well that's my 2c worth n e way :-)

  493. This is more than funny by twitter · · Score: 2
    Think about your next binary windoze install. Not that corrupted binaries were'nt already in circulation, but this adds a whole new dimension to Warez distros, even legit looking boxed software. Got mine from RISE, how about you? Mine comes from St Petersburg... Came in a box with a seal and everything.

    Oh well, I have not installed windows on a machine in more than 2 years. Will not be doing it again anyway.

    --

    Friends don't help friends install M$ junk.

  494. Ammunition against H/Cracker by ebresie · · Score: 1
    I believe someone mentioned about there being another issue here, and I think it could very well be linked to the attempt to make hacking info illegal.

    With all the weight M$ has, I am sure they probably have a lot of influence regarding these concerns in the national and internation world. Now they can use it to say, "Hey look what the mean old nasty crackers did with public information, we must do away with all of it/censor it/arrest anyone with the info...including all the wonderful known bugs."

    Is it just another coincidence, that the major coverage of both stories comes from MSNBC...hmmmmm...

    BreezyGuy

    --

    Eric B
    ebresie@gmail.com
  495. They had access for maybe 3 months. by fluor2 · · Score: 1
    But still the sourcecode is massive. Period. I think even 3 months would be to short for real sourcecode download.

    But I think this raises a lot of questions.

    Sun is pushing for sourcecode both in the EU and US. They feel the right to "steal" other sourcecodes.

    Why do people think that stealing is OK to do this?

    Why do people think that regaining market shares is legally done by looking into copyrighted sourcecode?

  496. Hey, scroll down to my post (ch-ch) by ch-chuck · · Score: 2

    and read an account of the Windows upgrade that was behind the Kursk disaster.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  497. And the best thing about .NET is. . . by kfg · · Score: 2

    that all your data is stored on a remote, secure server at Microsoft.

  498. What I am worried about by Geeky+Frignit · · Score: 1

    What I worry about is the blatant use of the word "hacker" in the articles. Yet another situation that will put a bad spin on hackers. No matter how many times we insist that the proper term to use is "crackers," they keep coming back with "hackers." Unfortunately, the general public does not hear about the good things that hackers do, such as this or this. If only the media would not blur the line between the two.

    Oh, and did you notice that in the articles about M$, it almost sounded like they were talking about a country. You could substitute "nation" in for "company", and it would still make perfect sense.


    Vote Libertarian. The only party that wants to treat you like a grown up.

    --
    Tired of sitting at that karma cap? Start a flame war today! See just how low you can go!
  499. According to Ballmer by YanceyAI · · Score: 1

    According to Steve Ballmer, "I can assure you that...the source code...has not been modified or tampered with in any way." Damn.

    --
    Can I bum a sig?
  500. The future of hacking and computer security by arikb · · Score: 2
    Hello all

    I'd like to jump into conclusions. Bear with me for a second here.

    Say that the recent high profile cracks (a.k.a. hacks) are only the beginning of a tidal wave, where companies are attacked for fun and profit. The world cries for help, and out goes the countries (US and Europe, for starters) and

    • Ban hacking tools (burglary tools)
    • Ban hacking conventions (subversive activity)
    • Ban hacking discussion forums (subversive, of course)
    • Mandatory licensing and auditing system administrators (holders of forbidden knowledge)
    • Mandatory deployment of monitoring tools allowing full accountability, complete with phone record cross references
    • Etc.

    What will happen? At first, things will look promisingly better:

    • Hacking sites will be banned and closed. The few which will remain will go on-line and off-line quite a bit, and spend their time mirroring and evading law enforcement
    • The script kiddiez will be gone! What used to be a game will have some kids arrested, and the rest will be scared s***less and cease to function
    • High profile cracks will become the sign of stupidity, as the cracker is sure to find the feds outside his place in a matter of hours
    But in the long run, we will start to see, IMHO, deeper influences:
    • Underground groups would form. They will use the Internet for communications, just as before, but will probably be more closely-knit and use steganography and/or encryption as standard means for communications.
    • Most of these groups would be benign, acting with the spirit of true hacking, but some will be malignant secret societies. I'm speaking of highly intelligent people, with the know-how and intention to commit those cyber-crimes, and some form of fscked up ideology about how "we must hurt them to prove they can't touch us".
    • All kinds of those groups will work feverishly in research of new technologies to subvert security systems, which will be slower but continue nevertheless, while
    • OTOH the security systems development will shift into lower gear. After all, the hackers are gone, right? The high profile dudes are in jail or on the run. Let's leave the door open at night, who cares?
    A dark era is coming. Information will be limited to the few who dare have it. The majority will live in the bliss of ignorance, while the few will silently loom in the shadows, waiting for their chance. Some will treat it as a game, knowing they control the power and get high on the feeling. Some will silently slip into places and perform subtle acts which will really pass unnoticed, like long range logic bombs and backdoors. System administrators will grow lax and less educated, while hackers-crackers will rummage their systems undisturbed.

    Call me paranoid and pessimistic. Flame like hell.