XP2 Spotted In The Wild
LostCluster writes "WinXP SP2 has just been released to the public via Automatic Update, but eWeek and PC Magazine are together reporting that Windows XP SP2's 'Windows Security Center' is just about as insecure as it could possibly be. According to them, any program (including ActiveX controls) can access and edit the Windows Management Instrumentation database, and therefore spoof the security status of an insecure box to report that it is properly secured."
any program can access and edit the Windows Management Instrumentation database
That MF'ing Clippy.exe in MS Word better stop accessing my Instrumentation database or I'll punch that SOB into the middle of next week. Really any program can access and edit the Windows Management Instrumentation database; I knew solitrae and tetris and an altier motive.
My box says it's insecure! So therefor, I can't possibly have some spoofing ActiveX control thingie, can I?
if every user were root.
I was told it was rolled out today (SP2), so can someone explain why my XP machines wanted to install the SP2 patch a few days ago?
Fact: You cannot bolt on security to something after the fact-- it has to be designed in from the ground up, or it's worthless.
Exhibit A: Windows.
Bill can announce a new security initiative every day from now until Doomsday, and it won't mean a damn thing unless they scrap Windows completely and start over. Period.
To build in a security overview system and leave it wide open so that its easy to fake the current status of things like your firewall and anti-virus.
So this is what the Internet Meltdown Predicted for Tomorrow article was referring to!
According to them, any program (including ActiveX controls) can access and edit the Windows Management Instrumentation database, and therefore spoof the security status of an insecure box to report that it is properly secured."
;)
That's ok. MS probably wants it to be easy to use so that everyone can use it.
Little Bricklets
If a boxen is 0wned then we can savely assume that the 0wner/w0rm has root access. And with root access it can do anything anyway.
This is like complaining that one can shut down your computer by removing the power plug.
Step 1: Go to http://www.mikx.de/scrollbar/
Step 2: Drag the scrollbar down a bit and let go
Step 3: Start -> Programs -> Startup
That's just spooky.
Karma: Segmentation fault (tried to dereference a null post)
I'm seeing reports all over the shop that its easy to spoof the security centre into claiming that (for example) the firewall is turned on when it isn't.
What I've yet to see is any indication that its possible to actually do the turning off of things, which would be rather more serious.
As it is, surely the only problem is if you forget that you turned something off? I've no big plans to make my box insecure now I've done configuring it on installation.
"I Know You Are But What Am I?"
To spoof the Windows Security Center WMI would require system-level access to a PC. If the user downloads and runs an application that would allow for spoofing of Windows Security Center, they have already opened the door for the hacker to do what they want. In addition, if malware is already on the system, it does not need to monitor WSC to determine a vulnerable point of attack, it can simply shut down any firewall or AV service then attack - no WSC is necessary."
Sadly just about everyone runs shit as Administrator (it is the default mode for XP Home installs) to make life easier and as MSFT has noted they are opening themselves up to the attacks... For those that will mention that Linux is so much better remember that these are the same people that wouldn't like to have to change to root (sudo, su, login, whatever) to install anything and would be opening themselves up to the same vulnerability level as if they had been running Windows.
Basically the problem was in design... They should not have had an open API controlling the "WSC" and thus malware would not be able to detect the presence of the programs' status from a single location. The real problem is that MSFT isn't admitting that it is a serious problem and needs to be changed on a different level... Saying that malware writers are going to use the direct route and disable the firewall/AV outright, while true, doesn't get them off the hook for creating this hole that is more difficult even for a more advanced user to notice.
Is there a way to distinguish Windows XP with SP2 from older versions through the User Agent String?
Seriously, this is just more scaremongering. The WMI system has to be accessed locally, and their examples of how this could be circumvented is pretty silly. ActiveX apps on a web page won't run unless you specifically tell them to. The only other ways are via a downloaded application. It boils down to "you have to do something on your computer that lets a malicious application run". How is that any different from any other operating system in the world? Even as a non-root linux user you can fuck up a system by running a malicious script... I don't get it.
Am I missing something?
Let's be honest. Did anyone really expect SP2 to not need a slew of new patches after release?
Personally, I'm just glad that it doesn't bomb randomly after install. Yet.
No, most user's don't need to be root most of the time. Yet:
While we are not aware of any malware exploiting this, we think it will only be a matter of time. The one mitigating factor that we found is that to change the WMI, and spoof the Security Center, the script has to be running in Administrator mode. If executed in Windows XP's Limited Mode, it will give an error, and not allow changes. Unfortunately, most home users who will be at risk, run in the default administrator mode.
How can we convince people not to run admin mode? It's easy at work, in UNIX land (most people don't get to know root pw.) But most Windows users I know don't even know the difference.
Every windows security problem I know of can be solved, or at least significanly mitigated, by users not running root.
everything in moderation
Windows XP SP2's 'Windows Security Center' is just about as insecure as it could possibly be.
and you were expecting what???
Remember Windows Management Instrumentation requires administrator credentials. If you have admin priveledges on any box, you can do much harm, regardless of the Operating System
Consensus is good, but informed dictatorship is better
Cue Marlin Perkins (of the old Mutual of Omaha Wild Kingdom shows):
MP: "Today, we are going to find and capture the elusive XP2 Leopard. My associate, Jim, is armed with a toe-nail clipper and a badminton raquet. Jim, why don't you start marching down that trail over there? I'll be back at the truck with the cameraman and a bottle of scotch."
Administrator is the default context for XP Pro, too, if you create users at install time. I run as administrator, but I use Firefox to browse everything but windows update, and I have Norton installed and auto-updating itself every day. Hence I am operating in an insecure fashion, but with little risk.
(Watch me get owned tomorrow or something, but nonetheless, I stand by my statements.)
On Linux I do typically do everything as me, and sudo when I can, but some programs don't work right when you sudo, they need a full root environment. On windows, using run as often doesn't work right because spawned programs revert to your user context (though not always? I'm not sure what's going on there), and many processes spawn new processes to do their dirty work. Even a lot of installs work this way, unfortunately.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
I noticed it was up last night to I installed it.
It's 94.50 mb which takes a while to download. Upon installation and restart the new windows security center pops up and trys to get you to turn on your firewall, automatic updates and antivirus software. By default if any of these are off, there's an obnoxious red shield in the system tray. Turning off alerts for these makes it go away.
Otherwise there doesn't seem to be any major changes.
So far nothing's borked.
Maybe MS could get NASA to send a few rovers in there to see what they can find out.
There is one subtle difference between linux and window admins: There is a lot of window software that is written to be run as administrator. Finding all the files to give permissions to causes quite a headache.
Linux, I feel, has a better system at the moment. However, as this is the developers fault, I see no reason why linux would be immune from this problem.
Mod me down with all of your hatred and your journey towards the dark side will be complete!
They're claiming that it's much more secure that Unix/Linux with this service patch. In terms of being 0wned, it's hard to totally cover your tracks in a Unix box- you leave a trail of breadcrumbs somewhere that typically can be seen (most tools simply automate the process...). In the case of an SP2 XP box, it'a apparently rather easy to cover one's tracks and you have to rely on signature scanning (i.e. Virus/Trojan scanning...) to hope you can find the intruder.
I don't consider that to be a non-problem, nor do I consider it to be more secure. It's definitely not secure enough to be allowed exposure to critical infrastructure of any kind.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
To make Windows secure, that is. I know lately that Microsoft-bashing has gone from being the in thing to being "trolling", but it's true. Just because it's become less fashionable to say so doesn't change the fact. I don't understand how Windows users can continue to use these machines. I live in a relatively remote area of Japan, and yet somehow within 4 minutes after hooking up my brand-spanking new machine to the Internet, I started getting Code Red connection attempts and repeated assaults on various four-digit ports. I guess they don't respect geographic boundaries either. By the way, this all happened while I was downloading XP2/SP2. It's not going to help when we don't even have time to install it before getting our machines "owned".
I've always criticised Linux users for being sloppy and the like, but the operating system itself is at least rock solid. It rarely crashes, it has a decent windowing system, and I don't see advisories for it on Bugtraq every 8 hours. Windows is easy to install, but it's all too easy for someone else to compromise. Ease of use is nice, but I think I'll take peace of mind with GNOME on Fedora Core.
Right. I can only assume you're using Linux now, and I apologize if i'm wrong. So you probably never have to: upgrade your kernel, upgrade applications or do an fsck. If this is the reason why you abandoned windows, it's a silly one. As far as i know, only consoles (Nintendo, PS1/2 & Co.) don't require updates. Everything else does.
The next thing to be said is usually: "But most home users run as admins." (The article also mentions this.) Well, that's not a Windows problem; that's a user problem. Even if Windows forced users to run in "limited mode" (which would cause an outcry in itself - "eek, Microsoft is trying to take away control over our own computers from us"), it also doesn't help that most third-party software for Windows requires admin rights either to install or *gasp* to run. Of course, this is ancient news to everyone with a clue
Of course, even when running as admin, protecting yourself against malicious code is fairly trivial; simply use a firewall (SP2 incidentally includes one), don't run binaries from untrusted sources, surf the web and check your email using something other than IE/Outlook, use a virus scanner/shield, and keep your apps and OS updated. Again, no news to anyone with a clue.
Quality, performance, value; you get only two, and you don't always get to pick.
I guess that depends on what you mean by "have to". An out of the box Fedora Core 2 system will work and play just nicely with your email, office, internet, graphics, video, etc. An OOB Windows XP install will only last 20 minutes once connected to the internet.
LilMikey.com... I'll stop doing it when you sto
Great work Microsoft! After all the beta-testing, SP2 is still broken. Here's what I've found so far that's messed up badly:
What I find funny is that ZoneAlarm's AntiVirus monitor feature detects AVG and Norton properly.:P
My Systems
Of course, you can "update" them also with mod chips, but I don't think that that is what you had in mind :)
I love my Linux box but I expend far more effort keeping it locked down with constant updates than I do my Windows boxes.
I'll say it again, OSS will never suceed with end users as long as so many in this community take an "Anything But Microsoft" stance.
I guess that depends on what you mean by "have to". An out of the box Fedora Core 2 system will work and play just nicely with your email, office, internet, graphics, video, etc. An OOB Windows XP install will only last 20 minutes once connected to the internet.
Out of the box Fedora may work with everything, but at some point in time, security vulnerabilities will be found in some piece of open source software, and a patch will (quickly) be made available. An unpathed *nix machine can be just as dangerous as a Windoze box.
Whereof we cannot speak, thereof we must be silent. --Ludwig Wittgenstein
What Microsoft is doing is analogous to me trying to turn my apartment into a bank:
Initially I just put up a sign that says "Bank" and leave the money lying on my sofa. Then when I get tired of people walking in and taking the money I lock my door. Then they kick in my door, so I get a thicker door. So now they climb in through a window, so I close and lock the windows. They break a window, I put up shutters. They cut through the floor, I lay down cement; ceiling, I add an alarm; they cut the electricity, I buy a generator. Maybe at some point I buy a safe, which works until they pick the safe up and roll it out of a hole cut into my wooden walls. This goes on for years, until eventually I get fed up and move out, and have a building built to purpose that's secure as a bank should be.
Where this analogy breaks down is at some point pretty early on customers would stop giving me their money until I got my act together, where they've shown no intention of doing the same to Microsoft.
Which again points out just how much of a joke Unix is. If the OS makes no distinction between folders (that's what directories are called in an Object Oriented operating system like Windows) and files, then how can you explore the C: drive? I mean, having to open a file called 'paths.dir' in notepad.exe just to find your files? I'm beginning to suspect that someone is taking the mickey.
and I apologize if i'm wrong.
That was the smartest thing you said. You don't need to upgrade your kernel. In favt many choose to use the older more stable kernels instead of the newer unstable ones - i.i 2.6.8.1
Hackers just dont pay the same attention to Linux, and when they do, they are not able to have the same penetration. Linux security is a public work in progress so exploits can be spotted long before they are with Windows. Windows is a good OS - good enough to warrant a small piece of the pie - not the huge amount it actually does. Windows offers: a good GUI, decent plug'n'play, a half-decent office suite, amongst a couple of other things. It deserves credit for that, but thats it. But its not free - like a bird.
So it tells you the firewall is up when it 'may' be down. If you can't remember wether you put it up or not, PUT IT UP ANYWAYS DUMBASSES!! (Not that I'd trust a Windows Personal Firewall anyways - wasn't UPnP supposed to revolutionize something?)
This is a training issue. Just as anyone who hasn't used Linux before would need help setting it up, anyone using Windows will need to know how to not be a dumbass; 99% of all security issues I've come across could've been prevented with liberal application of common sense.
I was going to mod you down, but just in case you really are ill-informed and not just a troll, in the interest of enlightenment I'll reply instead.
I don't know what Unix you're using (perhaps Version 7 on the Interdata 7/32 or some other forgotten vintage system), but modern Unix-like operating systems, such as *BSD, Linux and Solaris, by default create user's home directories with permissions user: read/write, group: no permissions at all, world: no permissions at all, and no special ACLs. Filesystems for these operating systems support ACLs (much like NTFS ACLs. Personally, I've found the user/group/world permissions have covered every case I've encountered, but that may not be true for everyone hence POSIX ACLs were created).
Certainly in the Linux world, major distributions turn the firewall on by default (RedHat since at least 7.x, and continuing into Fedora Core) during the install process. It's been a proper stateful inspection filter since before XP was even out. Also in a Redhat or Fedora install, you are asked to create a non-root user. The Windows XP install also asks you about what users you want to create, but by default creates them all with root privileges.
Oolite: Elite-like game. For Mac, Linux and Windows
I didn't mean you should uprade your kernel every time a new version comes out. The same goes for windows. You don't upgrade to a newer version every time either, right? For my firewall i still use 2.2.x series and don't bother to upgrade because it's of no use. Only times i upgraded the kernel was when a root exploit was fixed in a later version. I'm saying that if you switch from windows to because then you don't need to upgrade, is nonsense.
What is this Windows XP thing I keep hearing about?
"I used to have that really cool,funny sig
People just conveniently forgot that running as a common user does NOT guarantee that a malicious app does not runs as admin (or SYSTEM, more precisely). IIS, RPC, Messenger, lots of others run as a service with SYSTEM privileges. If you do attack it and find any vulnerability then you can run your malicious code as SYSTEM as well.
Sure, running as ADMIN is almost stupid and multiplies your chances of being 0wned by large. But its not the only source of being 0wned as people said above. As long as I remember, IIS (along with Sendmail, Bind, IE and some others) where considered the worst software in terms of security in the SANS Institute list. Break-ins are common in these softwares and would grant you good priviledges for doing some nasty things.
Just to be fair the same can happen in Linux/Unix but it's a bit less easy to do it. And you can always run an UserMode Linux, for example, and host the application inside it which would turn the host system almost invunerable and this is quite difficult to do in Windows (I can only think of VMWARE). Normally people are a little better educated to not use root in daily use and every installation program of recent distros explicit says it.
The only way to make joe user NOT want to use an Administrator account is to make it anoying to use. IE: -Display a NAG window everytime the user launches an application. (Maybe only if the user spends more than 30 minutes in the account) Maybe even make it easy to do some admin tasks easily as a Limited user by prompting for the administrator pw when required like Linux distros do today.
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
I find it amazing and certainly think someone should alert the NIMH. Software and hardware are each capable of EMOTIONS! Not just that, but complex ones at that. Who knew my little hunk of plastic, silicon, and metal would be so insecure? Is it because of my incessant banging away on the keyboard? Am I touching the mouse inappropriately? How do you tell?
I'd bet it's when I'm taping out the BPM for the music loaded on the drive. It has to be like the Chinese water torture. Poor little computer.
Please, let us make amends. I'm offering a sincere apology and promise to do what I can in the future to keep you from feeling battered and furthering your feelings of insecurity.
Good thing I've got all your patches up to date, or you might find strangers abusing you from far away locations. I'd never let you have such unsecured access. It' would only lead to more insecurity.
Plant a tree in a developing country.
They bypass this obvious lack of security as a feature, and that the application is rather to serve as an extra barrier of obscurity to hackers, and not as a solution to the problem (which it will ultimately be marketed as.)
This unfortunately isn't an adequate mentality. Microsoft appear to make the mistake to think that hackers are as technically challenged as their regular home user base.
Yes! certainly a home user wouldn't be able to craft some accidental software that rips a hole through the new security centre features. However, hackers which discover holes in Windows (Without ever seeing the source code.) have the competency to add the extra layers of dodging to their worms. This it at Microsoft's peril, as now worms can fool a system into reporting that everything is fine, in turn fooling the technically challenged home user into also thinking, that their new DDoS server is also functioning without a hitch.
Microsoft needs to understand that hackers are significantly "gifted" in comparison to their regular user base (many of which who'd think Mac OS X is another version of Windows.) They must craft their security devices such that they can not be trivially undermined, and put an end to the assumption that more easily bypassed road blocks lead to greater security.
I installed the official release of SP2 and installed it on my mom's laptop last night, only to be greeted with a nice informative blue screen upon reboot.
n ews.jhtml?articleId=23905071
http://www.crn.com/sections/breakingnews/breaking
I had to boot into recovery mode and run a batch script to uninstall SP2, just like the article outlines. Then I had to go into the registry and change some keys, then do an uninstall via the add/remove programs wizard. Man, thanks Microsoft for a full night.
I'm not sure if I'm going to try again, we'll see how I feel after stewing about it all day...
Actually, under XP, many programs take advantage of NETWORK SERVICE and LOCAL SERVICE accounts, which are not quite the same as SYSTEM. I believe IIS is one of these programs.
We're out 'ere lookin for signs of the elusive XP2 that's been said to be lurkin' in the wild...
Crikey, I've just spotted a wild paypah-clip in it's natural 'abitat! Look at those big ole eyes an'.. oh!.. there he goes trying to ask me if he can 'elp me!! You see, this creature is what's known as a parasite, 'ee leeches off o' your Windows Management Instrumentation databases. It's 'ard to satisfy one o' these buggers, they'll never leave ya alone until they've done your work for ya.
</steve irwin>
They would invade a country run by a dictator, continue the dictator's tortures even in the same places, inflame the world and make the world an insanely dangerous place to live.
Oh, wait...
Victims of 9/11: <3000. Traffic in the US: >30,000/y
Hey. I hate Windows as much as the next guy, but if you want to make a compelling argument you should at least be fair.
Windows XP came out in 2001. Do you really need me to tell you that running a RedHat distribution from 2001 would be suicide right now?
-If God wanted people to be better than me, he would have made them that way.
People, get a clue: a "malicious site" can't do anything to your computer, unless your box has already been compromised.
PC Mag, here's an idea: tell the users what the real problem is. You damn well know what it is. But you're afraid, because they spend a shitload of money on ads.
As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
I was about to Ask Slashdot about wherever it is relevant to upgrade XP to SP2 given the fact that:
Seeing all the potential problems XP SP2 can bring in, is it worth the update?
What do you guys think?
Despite what you say, they are trainable.
I got my sister (15, and understands precisely nothing technical about computers), after much yelling, screaming, and misunderstanding (this one mostly on my part), to use an unprivledged user for normal work and to make changes and install as Administrator.
That said, not only are default accounts admins, but you cannot only have unprivledged accounts; you must have a named admin in addition to Administrator. Very dumb.
Then disable both WMI and WSC Services and get yourself another personal firewall here or here.
MS opened the WMI to third-party sources and that is why we may mistakenly call it a hole, while in the reality it's an option.
What do you mean *They*?
It's the same guy Anonymous Coward every time!
"The likes of Facebook and WhatsApp are free to those whose privacy is of zero value."
Windows XP came out in 2001. Do you really need me to tell you that running a RedHat distribution from 2001 would be suicide right now?
Assuming you never patch the system, I agree. However, assuming that you're the slightest bit proactive about maintaining the box, I strongly disagree.
I use RH7.3 as a baseline for my systems (because RHEL costs too damn much, and because I'm not particularly fond of 8, 9, or FC) and while it's not quite that old (early 2002 as opposed to 2001) it's stable and secure. Of course, I do make use of Fedora Legacy via yum for most of my updates, but presuming such are not available it's not exactly a dificult task these days to, say, rebuild OpenSSH from source if security issues are found.
What part of "shall not be infringed" is so hard to understand?
Maybe you've seen the old motto. MS: "The whole world is our beta test site."
Why is MS software so insecure, and just plain sloppy? Maybe their management model just does not allow a programmer to finish his work. Later some poor guy is assigned to fix a terrible bug that is getting publicity, but it is difficult, boring work trying to understand what someone else did, and he makes mistakes.
Even if you could get a user to dot run as admin all the time, it's not going to help. Why? Because users WANT to run the stupid shit that infects their comptuer. They go to install Kaazaa, it says "I need root to install", you think they are NOT going to enter the root password? Of COURSE they will, they want Kaazaa on their computer, they'll do whatever it asks them to do.
As a receant example later variants of one of the receant worms was zipping itself and encrypting the zip to try and evade virus scanners (successfully, for a little while). That means you had to get the password from the e-mail, and use it to unzip the executable, then run it.
Guess what? People did. They went through all that trouble, because they believed the program to be something they wanted.
There is really no defense against stupid users, when they own the box. They can get admin, and will whenever they want it, even if it's not the default.
Either that, or you are doing something wrong. Here at work we have, oh about 500 Windows machines and maybe 200 Solaris machines and some Linux machines too. Of the Windows machines, I'd say 200 or so are already on SP2. They don't crash on bootup and SMB traffic is ALWAYS flying over our building (it's a single large subnet too).
As for AVG, well, you screwed something up. It detects fine on every system I've put it on. As for Norton, it is a documented Norton problem, and they (Norton) are working on it.
As for security centre, yes, this is by design. They know users ignore the update installation requests, so they want it automatic. Just tell it to quit bothering you, and it will.
What I find really funny is that this user, who appears quite clueless, is modded informative when all the replies are not. Look folks, anti-MS != informative.
If the animated dog says my machine is secure who am I to argue with it...
All the torrents you could want.
As far as I've managed to tell it has only "broken" one thing for me. The outbound TCP connections were limited to 10/sec. But then I went here:
http://www.lvllord.de/?url=tools#4226patch
And found a fix for it. All of the FUD that I've seen about SP2 breaking things mainly focuses around which apps aren't automagically detected by the built in firewall as "allowed". Considering that having to add rules to a firewall config is pretty standard amongst all firewalls, I'm pretty lost as to why this is considered "breaking" an app. I'll admit the TCP thing was frustrating, but that's the only problem I've encountered.
So for what it's worth, I've been running SP2 in beta and release form for about 1 month now on my primary system. And I've had only the one TCP issue. I've also had it running on 5 other "test" boxes (read: other family member's computers). And so far no one has reported a problem. Although obviously YMMV.
I'll admit I haven't formally been running the XP firewall (I turned it on to check it out, but I have my own firewall solution that I prefer). But turning it off was easy enough and I checked into configuring it and that seemed easy enough as well (you go into the control panel icon and select the programs you want to allow incoming access on).
Now lets not continue down the road complaining that it's broken because it's too difficult for "Joe Blow" to configure his firewall and as a result we should consider it "broken". Realize that at the same time "Joe Blow" probably can't properly configure ANY firewall. User ignorance doesn't mean something is broken. If I put power steering fluid in my brake lines because I don't know better, and my brakes lock up, that's not the car's fault.
What would happen if Microsoft limited the administrator account to 16 colors and maybe a low resolution. Would people learn quickly to use a user account to play games? Would administrators still be able to get their work done with said limitations?
This is just one of those off-the-top-of-the-head-and-not-thought-out type ideas, but i'm curious.
Why do I have this? I don't smoke.
IE is actually usable for the first time since, err, ever. The extra nag dialogs and the pop-up blocker go a long way towards keeping spyware off your machine. Lets face facts, most people will never stop using IE. They will go to their deathbeds using bundled software. They will never switch to Firefox or Opera. This is the service pack for them.
The nag "Where if your anti-virus" box is a reminder that windows needs an AV program to run properly. I can't stress how important a built-in firewall is, even if it is "weak" its still going to introduce people to the concept of a firewall much more than the old version did. Personally, I dont think ports over 1025 should be blocked by default, but that's just me.
I've been running SP2 since MS released the final version and am pretty pleased with it. XP even feels snappier. It passes the "grandma" test fairly well and like you wrote is a good first step towards securing windows. If it only helps fight spyware installs its worth its bytes in grams of gold. Especially for us techies who get called, bothered, etc for stuff that is completely preventable.
This is really the first step to securing windows for the everyman, if such a thing is truly possible. Soon enough current machines will be replaced with machines with processors which understand NX, thus making the feared buffer overflow much less fearsome.
Even though SP2 is going to cause all sorts of headaches with clients, friends, and family, I'm very optimistic about what it can do to help stop spyware and to a lesser extent worms and viruses. Its a real shame there isn't an equivalant SP for the HUGE win2k user base out there. Seems like the script kiddies will now be focusing on win2k machines from now on.
Add to this that Windows doesn't give the user a facility to promote (and demote!) themselves easily its really hopeless. This problem has been around since NT 3.1 and has been compounded by the integration of IE into the kernel. And yes I know about "runas" but it doesn't work correctly for many apps (even ones provided by MS).
So Windows offers you as an IT manager two options:
- Remove admin rights from users but anytime an application requires a minor elevation in rights you will get pestered.
- Give everyone admin rights but watch installations like hawk because they might accidently misclick some link at some googled web site that wasn't what was said.
Either path is expensive. I curse MS every day for creating a flexible permission system, access control lists that are well integrated across the enterprise and then promptly not use them in any of the right places.
I'm stumped and have given up all hope of figure out what to do beyond pray. As long as MS clings to this system this Windows will be an expensive PITA system to maintain on the enterprise.