Microsoft Refuses To Fix NT 4.0 Exploit
shmigget writes "The Register is reporting that Microsoft is throwing in the towel as far as NT 4 is concerned on the latest security flaw to affect Windows 2000, XP, and NT 4. They quote Microsoft as saying 'The architectural limitations of Windows NT 4.0 do not support the changes that would be required to remove this vulnerability.'" There still is a workaround for NT 4.0. Instead of patching the problem, it's advised to firewall off port 135 on an affected machine.
So in effect, ZoneAlarm could be considered as a patch for this problem??
M$ Programmers - "But its a product that is still in use, we have a responsibility to our customers."
M$ Exec's - "Wats this respongeability you say?"
After running this through the honesty filter, we come out with:
"Windows is fundamentally insecure. Suck it up."
Gotta love the honesty.
-Waldo Jaquith
Ve haf ways of making you upgrade, ya!?!
- - -
"The sixth sick shiek's sixth sheep's sick."
"Windows XP Professional is built upon the rock-solid reliability of Windows NT technology, the architechture that is so fundamentally limited that it does not support the changes required to remove significant vulnerabilities."
Doesn't have quite the same ring to it.
- JoeShmoe
.
-- I wonder which will go down in history as the bigger failure: the War on Drugs or the War on Filesharing
I'm confused at that - those keys aren't even next to each other - how could that typo have existed? Maybe a Dvorak?
Or is it a bizarre acronym? Back-Exploit, 'cause its an old software version?
Plus, why are people so irksome in not upgrading to ever newer and more expensive operating systems like they're supposed to? Constantly forcing Microsoft to keep looking back over legacy code. It's ugly, dirty and scary back there, not like in candy XP land.
Those Eastards!
NT4: I'm not dead yet.
..and on and on.
Microsoft: Yes you are, you just don't know it.
NT4: Really, I'm very much alive.
Microsoft: No, you're very sick and could give over any minute now.
(I'm so ashamed I can't recall that conversation verbatum...
Getting old, I suppose.)
Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
>blocking port 135 on a firewall is a better option.
I can't help but wonder how many brainwashed MSCE's will "solve" the problem by setting up a firewall running Win2K.
I find it interesting that the "Windows" topic has finally been used. This is the first time I can remember seeing it
Me too. However, since we're discussing a Windows security hole, shouldn't one of the glass panes be broken?
Didn't you read the EULA? It specifically said, "This product is supplied without any warrantee for any use whatsoever. Even as a high tech coaster in an oversized box. If the media is damaged, we will replace it with undamaged media, which we also don't guarantee has any usable software on it, within 90 days of the purchase date. Do not use in the presence of electric current. If cough persists, discontinue use."
The net will not be what we demand, but what we make it. Build it well.
There goes Unix, being more efficient than Windows again!
oh, you are so forgetting microsoft bob.
2 1337 4 u!
Close, but here's what they'd really do:
:-)
-Announce a 'strategic partnership' with the Plexiglas people
-Send their own team of glaziers to study Plexiglas
-Suddenly announce that they are changing strategic direction and dissolve the partnership
-Six months later, Microsoft ClearPane, which looks remarkably like Plexiglas, is shipped.
~Philly