Microsoft confirms 17-year-old Windows vulnerability
Microsoft confirms 17-year-old Windows vulnerability
... affects every release of the Windows NT kernel — from Windows NT 3.1 (1993) up to and including Windows 7 ...
http://blogs.zdnet.com/security/?p=5307
- William (Dthdealer)
- Posts: 146
- Joined: Thu 30 Oct 2008, 06:41
- Location: Australia (GMT +10)
Nice picture
Microsoft is big from the 'we don't care' policy. It means when they release a new version of Windows they can label it 'More secure' and reap the benefits. Meanwhile users buy Installation discs to re-install over malware-ridden systems.
By the way, the correct word they should have used in the article is cracker, not hacker. The basic difference is this: hackers build things, crackers break them.
Microsoft is big from the 'we don't care' policy. It means when they release a new version of Windows they can label it 'More secure' and reap the benefits. Meanwhile users buy Installation discs to re-install over malware-ridden systems.
By the way, the correct word they should have used in the article is cracker, not hacker. The basic difference is this: hackers build things, crackers break them.
-
- Posts: 17
- Joined: Tue 06 Oct 2009, 05:19
GMAFB - - -
If Microsoft was an auto maker, would they still be around today??
Give Me A F$(&$n Break. One more piece of evidence that
the left hand knows not what the right hand is doing, within
MS. Un-Be-Lieveable. 17 years ?!?!?!?
I cannot remember, in all my 54 years, any other company
whose products performed so poorly, and who stayed in
business.
What scares the HELL out of me is knowing that much of
our military systems are running this garbage !! OMG !!!
Planning a flight to RIO soon? Rest assured your air traffic
controller software is.....Microjunk ....YOIKS!
Ahhh....so what if it says you're too low.....just wing-it.....
Oh-wait: gotta RE-BOOT to upload the newest flight patterns.....
please wait....there we go....ooops - gotta re-boot again to
upload the latest topo-maps.....please wait..........
(tower) - KLM 164, if you're still there, pull up 17 degrees to get onto glide
path, acknowledge..........KLM 164.......? .....?.............KLM 164 ??????
Screen msg: Internet Explorer encountered an error and must close-
Do you wish to send an error report?
Yeh - I wish to say that a B-747 went down with 287 people on board
and all are assumed DOA.
--------------------
Folks, some things can be forgiven. Some things can be passed
off as 'innocent' errors. But geez....17 years later ??
GMAFB. Where are the code checkers at MS ? Where are the
people who are hired to insure this stuff can't happen?
Surely, in all the tens-of-thousands of code-writers there,
someone must have spotted a hole......or they fell into it
and were never seen again.
I'll give MS another 5 years - I'm guessing we won't hear much
from them beyond that point....at least I hope not.
Give Me A F$(&$n Break. One more piece of evidence that
the left hand knows not what the right hand is doing, within
MS. Un-Be-Lieveable. 17 years ?!?!?!?
I cannot remember, in all my 54 years, any other company
whose products performed so poorly, and who stayed in
business.
What scares the HELL out of me is knowing that much of
our military systems are running this garbage !! OMG !!!
Planning a flight to RIO soon? Rest assured your air traffic
controller software is.....Microjunk ....YOIKS!
Ahhh....so what if it says you're too low.....just wing-it.....
Oh-wait: gotta RE-BOOT to upload the newest flight patterns.....
please wait....there we go....ooops - gotta re-boot again to
upload the latest topo-maps.....please wait..........
(tower) - KLM 164, if you're still there, pull up 17 degrees to get onto glide
path, acknowledge..........KLM 164.......? .....?.............KLM 164 ??????
Screen msg: Internet Explorer encountered an error and must close-
Do you wish to send an error report?
Yeh - I wish to say that a B-747 went down with 287 people on board
and all are assumed DOA.
--------------------
Folks, some things can be forgiven. Some things can be passed
off as 'innocent' errors. But geez....17 years later ??
GMAFB. Where are the code checkers at MS ? Where are the
people who are hired to insure this stuff can't happen?
Surely, in all the tens-of-thousands of code-writers there,
someone must have spotted a hole......or they fell into it
and were never seen again.
I'll give MS another 5 years - I'm guessing we won't hear much
from them beyond that point....at least I hope not.