Slashdot Mirror
Microsoft Releases SP4 for Windows 2000
Snake_Plisken writes "I checked Windows Update today on a lark and found that Windows 2000 Service Pack 4 has been released." You can read a short CNet article discussing the media player patches as well as one more about
the fixes in SP4.
Any brave souls out there already applied this yet? I am looking at about 100 Win2K boxes that will potentially need this...so anyone with feedback would be greatly appreciated.
And here you can read about the newest security leak which is not patched by this servicepack ;) :)
That guy who analysed the buffer overflow also found a funny easteregg in the buggy dll file.
The Scary part is, I've found Win2000 to be the most stable and reliable Windows ever released. 63,000 defects? I wouldn't doubt it. The part that worries me with how well 2000 works, how many defects do the 9x, XP, and NT versions contain?
The preceding post was not a Slashvertisement.
This site has a pretty good list of weird MS Support documents.
I'm not looking at the terms of the EULA to confirm this, but I've read that MS Service Packs are cumulative, in that when you install SP4 you are agreeing to install SP3 (along with its EULA). If true, this means that by installing SP4 you are agreeing to the terms of SP3.
Nope, no sig
Except this is what it was: a trojan, but with an all new date, and an all new filename. Someone has just rereleased this baby.
Fortunately, a few things clued me in:
(1) It said it was from Microsoft. But the URL said from a Verizon ad.
(2) It called me a Microsoft Client. I've never felt so humiliated. I do *NIX or Mac.
(3) It claimed to fix ALL the known security flaws in Windows. This one should have been obvious.
(4) It was advertised to work on Win9x, ME, and 2000. My guess is that Microsoft doesn't do a whole lot for Win95 people who haven't upgraded. I could be wrong.
(5) It included an executable. [??? how did that slip past my ISP??? They normally strip executables.]
Anyhow, for those of you who use Windows, be aware [once again, and again and again] that those trojans are not to be run.
Correct Horse Battery Staple: 72 bits of entropy. Enter "Correct H" into google. When it generates the phrase, that's
Of course, the existence of the bug in the first place never put their customers at risk. What a crock of shite. Reminds me of MS's recent purchase of a virus protection sooftware company.
1. Sell software with security holes
2. Sell protection against those same holes
3. Profit!
The arrogance is astounding.
You can use the handy official Microsoft desktop support lifecycle wizard to see how long they plan to support each desktop OS version. Windows 2000 will be fully supported through 3/31/05, then it will enter "extended support" for two more years (extended=more expensive). After that you're on your own. Win2k server follows basically the same guidelines, except that in the "extended" support period you need to pay for non-security-related hotfixes.
Because XP feels so flashy, childish and dumbed down, I'd either go to Linux or Win2k if my current XP install goes completely ka-boom. 99% of what I've done with XP is make it like 2k, but once that was done I don't see any technical reason to downgrade either.
Kjella
Live today, because you never know what tomorrow brings
Anyone know how badly this breaks terminal services? Damned MS, they never could make a service pack that didn't break terminal servers in some way or other.
You have a very good point. It can be difficult to understand what is going on using things like group policy. I fully agree that writing a script that simply logs into the machine and runs the executable is much more.....understandable. However, once you do learn and understand group policy, it becomes very easy to administer and use it to your benefit.
That said, yes, I know very well what is going on when I use group policy. ( I do it on a daily basis) Troubleshooting failed group policy can be major a pain in the ass, but, like anything, once you've done it a few times, you get better at it. Typically I wouldn't monitor traffic flow, although that would give you a good idea if it was actually downloading the software. There are some tools to troubleshoot GP, gpresult being the first one I use. It's not perfect, but I do trust it.
Also, a windows sysadmin could also just write a script to install the pack, you just wouldn't use ssh to log in to the machine, you would use something like sysinternal's psexec. So, to sum up...yes, I know what it does and I trust it, but that doesn't mean you couldn't do it similar to your method on windows box.
Geek used to be a four letter word. Now it's a six-figure one.
... is somewhat troubling. I am unable to cleanly reboot the box (it just lays there like a lame date), and I had to remove two instances of a file called mobsync.exe in order for my system to regain stability. With this file running, I was unable to run any instances of the explorer (including control panel) and the entire system became unstable. Luckily, I was able to bring up the Task Manager to kill it, and used Find to find/delete the files. The file protection box will pop up, of course, but you can decline to have the files reinstalled.
Just my experience so far...
"You're getting brutal, Sark. Brutal and needlessly sadistic."
"Thank you, Master Control"
-Sark and the MCP
Never update or make a change on Friday or before a holiday. This is a best practice.
As for SP4, I'll wait a few weeks before I upgrade my wife's laptop (on the off chance Microsoft will have to pull it or update it).