Slashdot Mirror


Microsoft Lists SP2 Incompatibilities

thejuggler writes "ZDNET has a story about how the new XP SP2 causes conflicts with over 50 applications and causes problems with others including some of Microsoft's own products. The 'glitch' as they are calling it seems to be that the Windows firewall system is turned on by default and blocks unsolicited connections to your computer. You have to unblock certain ports as your applications require to make the apps work again. They are calling this a glitch, but I thought we wanted everything blocked by default so we would have to choose what was unblocked?" The BBC has a story as well.

22 of 539 comments (clear)

  1. SP2 incompatible by bunburyist · · Score: 5, Interesting

    I've not seen it mentioned anywhere, so maybe it's just a drive incompatibility issue, but when I installed SP2 RC1, I could no longer play DVDs - I would receive an error telling me that the TV OUT on my card must be disabled first. I rolled back to SP1 and bingo, everything would play fine again.

    1. Re:SP2 incompatible by jrockway · · Score: 4, Interesting

      Solution? Ignore the flags. Install mplayer.

      Oh but that's ILLEGAL. Please tell me why it's illegal to play a DVD i bought on a computer i bought. Thanks.

      --
      My other car is first.
  2. Re:News Flash: Firewall Blocks Inbound Traffic by halowolf · · Score: 5, Interesting
    Yes it was exactly my response. They had games listed that require internet access to play them online like Unreal Tournament.

    What I think is the "real" issue here is that customers that have installed SP2 simply don't have a clue about what a firewall is, what it does, and how to use it. The problem is also no doubt being exacerbated by programs that needlessly try to access the network.

    But I always take the time to say "shame on you" to programs that needlessly try to access the network when their primary function has absolutely nothing to do with networking, ESPECIALLY when their networking options are turned "off".

  3. Re:Time for change? by GoofyBoy · · Score: 3, Interesting

    If I don't know how to open up ports on a firewall or even what a firewall is, how the hell am I going to know figure out how to install Gentoo?!?!?

    --
    The surprise isn't how often we make bad choices; the surprise is how seldom they defeat us.
  4. Re:Time for change? by King_TJ · · Score: 4, Interesting

    I'm sorry, but I'd almost have to call your post a "troll" - even though you're not necessarily wrong about everything you said....

    Realistically, how is a Linux distro like Gentoo a real "alternative" at all, for the average PC user wanting a "workstation OS" that runs all of their purchased "off the shelf" software packages??

    Just as one little example, a good friend of mine recently wiped Windows XP off his Dell Latitude laptop and replaced it with the latest Gentoo Linux distro. He could only stand it for about 3 days before deciding it just made his laptop *less functional* than it was worth, and went back to XP.

    It's not that he dislikes Linux! He thinks it's great! (So do I, for that matter.) It's just that Linux is based on a *server-centric* OS (Unix), and all the attempts to reconstruct it as a desktop workstation OS with user-friendly GUI are less than fully realized.

    I'm all for competition, but as much as some people want it to be, I don't think Linux is really the direct competition for Windows XP right now. If anything, it's poised more as a sensible alternative for something like Windows 2000 or 2003 Server.....

    If you want a Unix type OS done right as a workstation, I think Apple already pulled it off better than anyone else -- but that's getting into a whole new hardware AND software investment.

  5. Re:Default Port Blocking is wrong when... by EvanED · · Score: 3, Interesting

    According to this Register article, it's not like MS made SP2 come out of the blue. App vendors have had plenty of time to start thinking about the changes they might need to make.

  6. Designed for newbies by ktorn · · Score: 4, Interesting

    Turning on the firewall by default is a design for newbies, and rightly so.

    My mother doesn't know what a firewall is, nevermind how to switch it on.
    Those who know what it is, and how to configure it, will be able to open the required ports or allow the required programs access to those ports.

    The clueless might not be able to use some programs, but if that means viruses and worms will not spread as much as before then it's something I think we all can live with.

  7. Re:Not a big deal... by WhatAmIDoingHere · · Score: 3, Interesting

    In IE, just go to "tools"/"Popup Blocker"/"Settings" and there's about the same settings as in Firefox.

    --
    Not a Twitter sockpuppet... but I wish I was.
  8. Re:Like we didn't see this coming... by obeythefist · · Score: 3, Interesting

    Okay Mr. FUD, let's look at Linux. Say you had a linux install. And you ran Mozilla and you used that to browse websites, mozilla came *bundled* with your operating system.

    This is all well and good.

    Now you install a Firewall, perhaps one bundled with your Linux distro.

    Suddenly, Mozilla doesn't work anymore! You can't browse the internet!

    Is this the fault of your Linux distributor? Why are people saying that Windows is useless because the new firewall *blocks* traffic unless you open the right ports? Why aren't people saying the same for Linux, when Linux works *exactly* the same way?

    Or do you just like to spread anti-MS FUD so you can get karma on slashdot?

    --
    I am government man, come from the government. The government has sent me. -- G.I.R.
  9. Mac OSX manages this just fine by goombah99 · · Score: 5, Interesting
    On mac OSX the sharing-related services GUI and the Firewall GUI are coupled. Turn on Apache and it unblocks port 80 automatically. Turn on SSH and it unblocks 22 automatically. and so on for FTP, AFP. turn off he services and the ports get bliocked automatically.

    At present if you want other ports to open, other than these default services, you have to open the ports manually. however I would imagine this coupled action is handled by some .plist xml configuration file. So its probably possible for an application to add its own services to the sharing menu and have them coupled to the firewall if you turn the service on.

    On my mac I do manually block the incoming and outgoing license manager ports for MS Office. If you dont and want to share the app on your laptop and desktop then you will lose any open edited docuements if you inadvertently plug them into the same network. I wonder if this lic manager is the reason why MS gave the firewall the ability for apps to open ports in the firewall and to have outbound connections?

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:Mac OSX manages this just fine by FireFury03 · · Score: 4, Interesting

      you're clueless, right?

      No

      firewalls can also be used to get some sort of acl functionality out of them (you might want to enable ssh access to only a few known ip's on the internet), can do packet inspection, perform rate limiting tasks, prevent DoS attacks

      Right, because how many Windows personal firewall users are going to be doing that? I haven't seen Microsoft's offering but I'd be quite supprised if it could be configured any mroe specifically than "block this port" and "open that port".

      protect the internet from _your_ machine should some malware be running

      IMHO blocking outbound traffic from personal firewalls is of dubious use at best - once the machine has been compromised the malware can quite happilly disable your firewall (a number of viruses are known to disable ZoneAlarm automagically) or look at the firewall rules to see which port it can make connections on.

      Running a firewall to block outbound traffic only seems sane if it's a completely separate device since once the device running the firewall is in a position to send malicious data the security of the firewall should already be considered void. As far as I can tell, all it does it provides a false sense of security, which is a very bad thing.

    2. Re:Mac OSX manages this just fine by pellaeon · · Score: 3, Interesting

      Right, because how many Windows personal firewall users are going to be doing that? I haven't seen Microsoft's offering but I'd be quite supprised if it could be configured any mroe specifically than "block this port" and "open that port".

      So now we're suddenly talking about Microsoft's firewall only? Well, I haven't seen it either, but I'm pretty sure there's a personal firewall available somewhere that can do at least some of these things. Configuring your OS/services well still doesn't protect you from a DoS on your computer though.

      IMHO blocking outbound traffic from personal firewalls is of dubious use at best - once the machine has been compromised the malware can quite happilly disable your firewall (a number of viruses are known to disable ZoneAlarm automagically) or look at the firewall rules to see which port it can make connections on.

      And some compromises will not achieve sufficient access to disable the firewall or view its config. How about home-dialing malware that would in this situation be prevented from running, or spyware?

      IMHO having a firewall running is useful even if only to provide an extra stumbling block for malware.

      Running a firewall to block outbound traffic only seems sane if it's a completely separate device since once the device running the firewall is in a position to send malicious data the security of the firewall should already be considered void. As far as I can tell, all it does it provides a false sense of security, which is a very bad thing.

      Ok, how about a home network then? Many people use one Windows computer using "internet access sharing" to enable other computers to connect to the internet. In this case the internet-connected computer running a personal firewall would be a seperate device and could defend itself (and the internet) much better against the internal compromised machine.

      Err on the side of safety, I say.

      --
      -- /bin/coffee missing. universe halted.
    3. Re:Mac OSX manages this just fine by FireFury03 · · Score: 3, Interesting

      Configuring your OS/services well still doesn't protect you from a DoS on your computer though.

      Depends what sort of DoS you're getting - I don't really see a firewall as a solution to any of them though:

      - SYN flood: this problem was solved years ago through the introduction of SYN cookies - anyone who isn't using SYN cookies these days has no business allowing anyone connect to them anyway.

      - Bandwidth flood: A firewall ain't gonna help you here - even if you're blocking the packets, they have already traversed your (reasonably low bandwidth) internet connection... The only thing that's going to help here is to block the packets on the ISP side of the connection.

      - Slashdotting (i.e. many concurrent connections - may be legitimate connections but they're gonna kill your server anyway): Most services will let you limit the number of connections they will serve at the same time - a firewall is not the answer (unless it's on the ISP side of your internet connection).

      IMHO having a firewall running is useful even if only to provide an extra stumbling block for malware.

      It's a stop-gap solution - when 99% of computers block outbound traffic by default the malware will all automatically work around the firewalling. Malware is a very fast evolving problem, just like spam - simple stuff like this will only have an effect for a very limited amount of time. I think it's exceptionally bad that it will produce a false sense of security, and the very protocols that worms will be using are likely to be open anyway since they're protocols that people need to use.

      Ok, how about a home network then? Many people use one Windows computer using "internet access sharing" to enable other computers to connect to the internet. In this case the internet-connected computer running a personal firewall would be a seperate device and could defend itself (and the internet) much better against the internal compromised machine.

      I wouldn't suggest that a firewall is useless in this situation, however I was talking about personal firewalls and would argue that once you start protecting a whole network instead of a single machine you can nolonger consider it a "personal" firewall.

  10. Scary quote by roystgnr · · Score: 3, Interesting
    From the support.microsoft.com link:
    The number of ports that the process uses may affect how this issue is resolved:

    * If the process uses more than 1024 ports, the number of ports probably will not change.
    * If the process uses less than 1024 ports, the program may be using a range of ports. Therefore, opening individual ports may not reliably resolve the issue.

    It just fills you with confidence in their network security qualifications, doesn't it? I'm sure their audience won't be too confused (even most online gamers know the difference between "port number" and "number of ports"), but that just makes it even stranger that they hired a technical writer who can't make that distinction clearly.
  11. Re:News Flash: Firewall Blocks Inbound Traffic by surprise_audit · · Score: 4, Interesting

    On the other hand, the list of "programs that behave differently" includes Excel, Office 2003, Office XP, Outlook, Visual Basic, Visual C++ and Visual Studio. I can see various personal firewalls and p2p apps like Kazaa being broken by port issues, and maybe the Office suite because of email & calendaring, &c, but why on earth would VB & VC++ be affected??

  12. Re:Forgive my ignorance by Erik+Hollensbe · · Score: 3, Interesting

    for a standard setup and ports 1-1024 it's not as big of a deal, really, as your "friendly neighborhood cracker" needs to crack your machine completely to open ports. (Should be obvious, but if your user has root, you just lost all benefit of the firewall as it can be modified)

    However, if the cracker just manages to get user privilidges on the box, *ka-blam*, if you don't block inbound you are a mail relay, a DoS zombie, you name it. An easy way to prevent that is to block everything incoming that you don't use.

    Heck, with the way some rootkits work, and the relative naievete of the cracker, blocking hte lower ports may prevent something more sinister happening automatically and give you time to shutdown/clean/whatever the system before things get too screwed up.

    A good firewall plan always starts with "block everything".

    Another neat trick is to use NAT and port forwarding to send all incoming traffic on the firewall from the internet to a host on the local net that doesn't and will never exist. Depending on implementation and how you use it, this prevents the cracker from even touching the box (save a hole in the networking stack) and installing services on it, even if cracked, is fairly pointless. Of course this trick is useless if you don't follow firewalling best practices and block all incoming traffic from the outside that appears to come from internal-only network blocks.

  13. /Library/Prefereces permissions by SuperKendall · · Score: 3, Interesting

    The directory /Library/Preferences has perms of g+w, so group users can write to it - thus as the other poster noted you can potentially overwrite the file. At least, TextEdit sure does.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  14. Re:Default Port Blocking is wrong when... by Tarkwyn · · Score: 3, Interesting

    Most of us conscientious 'app vendors' have been diligently studying the various release candidates coming out of Redmond.

    Before beating on the ISVs make sure you check out a legitimate bug in SP2. This particular bug wasn't present in RC2 and has caused a good few slashdot-friendly vendors some undue heartache (notably PuTTY).

    Yes, there are vendors out there who ought to have been more prepared, but MS certainly needs to take a good deal of responsibility for these current issues.

    --
    Tarkwyn.
  15. Re:Like we didn't see this coming... by obeythefist · · Score: 3, Interesting

    Like you can configure Windows firewall as a part of the installation process (I've applied SP2 at home).

    As Mr FUD is suggesting, Windows users won't configure the firewall at install time (which is why those apps don't work). To be fair we'll also assume that you won't configure your linux firewall at install time.

    Any good firewall will block outgoing traffic just as well as it blocks ingoing traffic, by default. The new windows firewall in SP2 blocks outgoing traffic (the SP1 version of the firewall was inbound blocking only).

    So, without configuration, you'll find all those linux distros you've listed share this same problem - when you install an unconfigured (all ports closed 2-way) firewall on them, some applications will break.

    You can't go and say that it's a "non-existent" problem, because you have to assume that any user who can't configure a firewall under Windows couldn't do it under Linux either. What we're really seeing here is Windows moving closer to Linux's security methodology - secure by default. So the problems mentioned in the article are directly applicable to any Linux distro that is secure by default - yet people are hanging it on MS despite this.

    --
    I am government man, come from the government. The government has sent me. -- G.I.R.
  16. Re:You nailed it. by blane.bramble · · Score: 4, Interesting

    For example, everyone should know: what the Internet is; that not everyone on it is trustworthy, and most importantly to READ BEFORE YOU CLICK.

    My 7 year old daughter knows to do this - I have taught her that if any box appears on the computer to read the message, and if she doesn't understand it or know why the message appears, to ask me. As an example, a while ago she was trying to play a game (probably from the BBC web-site). After a few minutes she came and told me the game wouldn't work - it turned out everytime she clicked on it, she got the standard IE "do you want to run this, blah blah, may cause damage to your computer", so she clicked Cancel (not wanting the computer to be damaged...). After 4 or 5 goes round this she decided it was time to ask for help.

    Why is this so difficult to get into other peoples heads?

  17. I think Microsoft have done the right thing by pandrijeczko · · Score: 4, Interesting
    It seems to me that the listed applications do not work purely because of the default firewall settings in SP2 in which case Microsoft have done the only thing that they could.

    The fact is that the majority of Joe Public is far too stupid & lazy to want to bother understanding how a computer works so Microsoft has had to force their hand into making their systems more secure.

    Whilst I consider Microsoft "it's own worst enemy" by portraying its OSes as error free and requiring minimal management in advertising, they have taken the right action here because hopefully this starts to make it more difficult for viruses and worms to propagate meaning that we all benefit.

    If there's one big advantage we have in the Linux world over the Windows world is that our proportion of idiot users is virtually zero - I for one hope it stays that way also.

    --
    Gentoo Linux - another day, another USE flag.
  18. Which defeats the whole purpose by Moraelin · · Score: 3, Interesting

    I'll tell you a story.

    I once had to install Windows 2000 on a box, and as Loki would have it, I had no Zone Alarm or Sygate Personal Firewall on a CD at hand. Just as Joe Average would.

    So I could go download it somewhere else, or I could do a scapegoat installation just to download a firewall. I chose to just sacrifice an install to the gods of Hacking. I _knew_ I'd get hacked, but that was OK, since I'd reformat immediately after anyway. (Takes less time than whining on /. about MS security, btw.) Joe Average wouldn't know, and wouldn't reformat.

    (And I'm not disappointed. It takes less than a minute to get my uplink bandwidth saturated with mysterious outbound packets.)

    Still, it will serve to illustrate what happens after you get your machine 0wn3d by some l337 skr1p7 kiddi3.

    So I decide to play with it a bit longer, and see what happens with a firewall and an 0wn3d machine.

    I start the newly downloaded and installed Sygate Personal Firewall, and immediately it pops up a window telling me the name of the application _and_ what's it trying to do. I block it, and that's that. No more outbound packets. I can tell struggles long and hard to send crap, but it can't. Both its inbound and outbound pipes have been sealed shut.

    I can now toy with that machine as long as I wish, trying to disinfect it. Again, which is what Joe Average would want. If it's _not_ a sacrificial install, but some machine where his resume and a few gigs of other important data is, Joe will not want it reformatted.

    I can even surf the net looking for information on the trojan, safe in the knowledge that it's blocked. No need to pull out the network cable.

    Whereas you tell me that Apple would have allowed it to open its own ports, as it damn pleases. Inbound or outbound, whatever. And not even told me about it.

    Well, gee. Sorry, that's not the kind of security I'm looking for. Dumbing down a firewall to the point where it doesn't actually block anything, in the name of "user-friendliness" is _not_ the way to go.

    --
    A polar bear is a cartesian bear after a coordinate transform.