Slashdot Mirror


WinXP SP2 Sacrifices Compatibility for Security

goldragon writes "TechRepublic is reporting that "Microsoft is pulling out all the stops to improve security. So much so, in fact, that it will cause many problems because SP2 will de-emphasize backward compatibility with legacy systems and code for the sake of security." One small step forward for Microsoft, one giant leap backwards for mankind?"

9 of 773 comments (clear)

  1. Compatible by panxerox · · Score: -1, Troll

    HAHA ! Cedega makes linux more compatible with windows and windows makes windows less compatible with windows. I guess everybody has agreed then, the only way to make windows secure is to abandon it. LMFAO

    --
    "It's so convenient to have a system where everyone is a criminal" - A. Hitler
  2. compatibility doesn't have to be insecure... by vladb · · Score: -1, Troll

    Hmm... but backward compatibility may not always directly translate into less secure systems. I figure if Microsoft really cared about security they'd still manage to make the SP 2 as secure as it should be.

    It seems that Microsoft relies too much on third party hackers to help find flaws. And as always, the users will bite the bullet!

  3. let me guess, open source code will no longer run by Anonymous Coward · · Score: 0, Troll

    This is an oppurtunity for Microsoft to get rid of any software that competes with their products, along with any open source software they dislike. All in the name of security.

    so is Mozzila on the list of incompatable programs now? how about openoffice, or Lilo?

  4. going forwards... by mikael · · Score: 0, Troll

    One small step forward for Microsoft, one giant leap backwards for mankind?"

    An enormous step forward for the Penguin.

    --
    Vintage computer adverts: http://www.vintageadbrowser.com/computers-and-software-ads
  5. Re:Compatibility Woes? by cluckshot · · Score: -1, Troll

    The compatiblity problems induced by applying security to the M$ OS is that by structure and by design the M$ OS(s) were progressively more and more "Insecurity Systems."

    The essential thing here is to understand the most basic underlying logic of the M$ empire. They own your computer! In order to maintian their control they had to leave the system open to external takeover. Hackers have had a field day with this design decision.

    If M$ is to stop having hackers romp their systems, they have to abandon the concept that they own the user's machine. If they abandon this, they abandon their revenue stream. The conclusion is obvious. You will never get security out of an M$ OS. They are in a box. If they lock out hackers they lock themseves out and their money out. If they don't lock out hackers, the SPAM, POPUPS and SPYWARE and other MALWARE will collapse the Internet and their fortune.

    It will be curious to see if they can find their way out of the box that they have so deliberately constructed.

    --
    Never Politically Correct ~ I prefer the facts If you don't like what I say, get a life, or comment yourself.
  6. Re:Compatibility Woes? by deadlinegrunt · · Score: 0, Troll
    What will the slashdot community do when Microsoft fixes all of their problems? If they execute the antivirus and spyware solutions properly, It'll be a while until I look back.

    For one you place too much emphasis on yourself, more directly - your subjective perspective.

    Some of us do not use windows for a variety of reasons:

    It simply is not the best tool for the job

    They may fix their product; can they fix other things broken by lost mindshare

    They are a convicted monopoly

    They break standards

    They do not innovate, they stifle

    Long track record of saying but not doing

    etc...

    "You are what you do when it counts."

    I could go on and on but then those are my subjective opinions. To answer your question though:

    Continue on just fine. From what I can infer from your post it does not sound like you brought that much with you to begin with.

    --
    BSD is designed. Linux is grown. C++ libs
  7. Re:Compatibility Woes? by Anonymous Coward · · Score: -1, Troll

    > The XP compatibility issue is that self-modifying code will no longer run on certain processors

    AMD64 currently has no official Windows support, so this doesn't "break" anything -- it just means that new Win64 programs have to be compiled to allow self-modifying code.

    If that's the only "compatibility issue", then /. has made a mountain out of a molehill.

  8. Re:Compatibility Woes? by Anonymous Coward · · Score: -1, Troll

    just a "new look" shell that makes it harder to navigate around your own file system (let's hide C:\ from the user, that's scary stuff, we don't want to confuse him).

    How exactly do they hide C:\ from the user? If you are referring to the empty desktop, they maybe hide it from the average user. But it can take maybe 10 seconds for any user (especially ones who browse this website) to just right-click on their start button, select properties, and then select Classic Start Menu. This should put the shortcuts back on the desktop. If that is too difficult, you can always just click on Start, Run, C:\ ... Is it that hard?

  9. Re:Compatibility Woes? by cpeterso · · Score: 1, Troll


    Why should the user have to manually insert A HREF tags? Slashdot should automatically detect URLs and add the appropriate A HREF tag, just like Microsoft Outlook does to URLs in emails. This is not that hard..