Slashdot Mirror
Complete List of Bugs Fixed in SP2
callipygian-showsyst writes "Microsoft has published the complete list of bugs fixed in Service Pack 2.
They range from the obscure like: 'File Appears to Be Deleted Although You Do Not Have Permissions on the OS/2 Warp4-Based Server' to the serious-sounding: ' Stop error message on a blue screen when you transfer data to a USB device in Windows XP'"
This is a giant list of all of the updates, and then links to the KB numbers on the left, so you can read what each one was.
... but after reading the KB, it's an ActiveX problem that can allow a webpage to access your media library. Then again, MS has always really vague and stupid titles.
Side note: one of my favorites:
MS03-021: A flaw in Windows Media Player may permit the Media Library to be accessed
At first, I was thinking that it was supposed to do that
Why is it so hard that the editors can't use the appropriate icons for them?
It's time this site starts to grow up.
Slashdot Moderation: From positive to terrible in 2 "insightful" posts.
is the list of bugs they've *introduced*.
--Rob
This list is all the bugs that have been fixed in Windows XP through SP2, not bug fixes exclusive to SP2.
if we're close to the time when the majority of slashdot readers don't know what OS/2 Warp4 is?
I mean, this guy printed the list : http://www.microbizz.nl/buglist.jpg
Well, out of the many bugs listed as being fixed thirteen were repaired that could cause code execution...
;)
Were these bugs found internally by their team or were these found by outsiders and then patched months later because knowledge was never released?
Not Prompted to Obtain a Digital Rights Management License for Installations Created by Using Sysprep
This was one bug they could have left unfound
But, but, but...then it wouldn't be slashdot any more!
There are a lot of instances of the word "cumulative" in this list ("Cumulative patch for Internet Explorer..."). I wonder how many true bugs are fixed with this, not just support article entries.
Out of an amazing 805(?) bugs listed, this has to be my favorite.
Some programs do not work as expected when large files are opened
Are there any fixes in terms of usability or user interface?
Like the damn message that comes up VERY TIME I wake a windoze laptop from sleep: "Hi! You're connected to your wireless network again. The same network as always, but I just wanted to remind you. The signal strenght is excellent. Click me, and I'll disappear. But be sure that I'll return the next time you start or wake your computer!"
I wonder how many suicides are directly related to windows error and/or informational messages.
Ciryon
* Microsoft Windows 2000 Advanced Server SP4
* Microsoft Windows 2000 Professional SP4
* Microsoft Windows 2000 Server SP4".
Are they intentionally driving up the number of bugs fixed?
-- "I'm not a religious man, but if you're up there, save me Superman..."
326971 - Operating system does not work
Here's an excerpt from a recent article on the debacle.
Okay, tell meonce again how many months it took to root out those errors? Some where known for a long time. And I expected a longer list... waaaaay longer!
Modifying a large operating system while attempting not to "break" any end-user configurations is nothing short of a prodigious task.
The modifications were probably developed and committed to the Windows source tree in a relatively short period of time. However, Windows must accommodate a diverse array of configurations, including many that are very "fragile" and obscure. Because of this, the modified build likely endured an extensive testing process, hence the multiple delays.
Do you like German cars?
Issue:
Error message on a blue screen when you transfer data to a USB device in Windows XP.
Resolution:
Error message now placed on gradient green screen when you transfer data to a USB device in Windows XP.
And you have to be in administrator mode. Oh no, you mean if I log in as administrator the programs can do bad things.
If I logged on to linux as root and ran a program it could cause the same sort of problems
I/O, I/O, its off to disk I go, with a read and a write, and a bit and a byte, I/O, I/O, I/O, I/O
326863 Operating system throttling does not work
I beleive a lot of files have been re-compiled to prevent buffer overflows and take advanateg of the NX flag on processors that support them. Many of these programs don't have a 'bug' as such, but are being made more secure.
It is a bit scary watching the install and seeing all these things being replaced.
Also the ~250MB is the admin version, that has every update. The version for home users will only have the necessary ones they need, and should be quite a bit smaller if the machine is reasonably up to date.
Probably still the biggest SP for windows ever though.
I'm not complaining. The fact of the matter is that 90% of WinXP users run as administrators. By allowing *any* software to tamper with the firewall, MS has made a mistake. All a virus will have to do is trick a user into clicking a link on a web page or something and the fw will go down. This isn't possible with zone alram or sygate firewalls... nor should it be.
It's a bit of a design flaw in the Windows security model.
I agree 100%. The Windows security model is broken. As I just commented in another discussion: "I hope Microsoft decides to join the 21st century and changes the default configuration so ordinary users do not run with excessive privileges, and instead requires an explicit action (as in the UNIX 'su' command, or Apple's authentication dialog) to grant installers and configuration tools temporary rights when they need it."
I honestly can not comprehend the selective blindness that Microsoft seems to suffer from when it comes to understanding freshman-level computer security.
However.
Going back to my original point: this is not a security flaw in Windows Firewall, and other firewalls like Zone Alarm are not inherently any safer... they are simply depending on security by obscurity. Unless they lose market share to the point where they don't matter to malware authors there will undoubtedly be software that disables them.
Look at antivirus software. They don't have a "Disable" API, but there are still viruses that disable them... and the code to do it as available to anyone with a copy of the world's premier virus distribution tool (Outlook).
Before you checkin code, it must be code reviewed -- this is manditory. Someone checking in a fix described as "fixed a spelling error", while adding 2000 lines of code, will be told to remove it (or get a bug opened for the new stuff that they added, and deal with it in a different change).
/will/ result in immediate termination.
Depending on the group you work in and the phase of the dev cycle you're in, you also have to get triage approval -- this means you have to justify your change to a group of people trying to keep code churn to a minimum.
When code is checked in, the change is mailed to one or more mailing lists. Among the things in the mail are the changelist description and the file in the changelist. Again, red flags will be rased when someone looks at the diff (and believe me, some anal retentive fucker like me will catch it).
If, somehow an employee managed to get through all of those layers and snuck in those 2000 lines of easter egg code under the radar, and the "easter egg" is discovered (and it will be), they lose their job. It's one of the few things you can do at Microsoft which
I agree. After I switched to linux I noticed how many people make it seem they're running linux (because of their pro linux comments and being modded up for praising linux), but run windows. Look how many people comment on big microsoft stories. Sometimes it's over a thousand.
I want to see slashdot's webserver statistics showing what people are really running. I wouldn't be surprised if it's only 10-15% of people running linux.
I think in addition to our karma, we should have a linux-o-meter linked to our ID name. That would expose that asshole who shouts out "winblowz," "Micro$oft" and all that other childish crap who's really running windows xp in his mother's basement. There's nothing wrong with people using windows. Hell, I use it at work. It's just when the slashdot "politics" skew the reality of the situation that it starts to get aggrivating.
And by the way, yes I did switch to linux to seem cooler on slashdot because that is all that matters in life.