![[Home]](http://www.msboycott.com/images/navbar/1a.gif){kind=small} |
![[NewsSource]](http://www.msboycott.com/images/navbar/2b.gif){kind=small} |
![[The Alternative]](http://www.msboycott.com/images/navbar/3a.gif){kind=small} |
![[SuperList]](http://www.msboycott.com/images/navbar/4a.gif){kind=small} |
![[Bulletin]](http://www.msboycott.com/images/navbar/5a.gif){kind=small} |
![[About Us]](http://www.msboycott.com/images/navbar/6a.gif){kind=small} |
![[.Community]](http://www.msboycott.com/images/navbar/7a.gif){kind=small} |
![[Search]](http://www.msboycott.com/images/navbar/8a.gif){kind=small} |
WinNuke!
(05/26/97) Last Week's News News Archives
Last week we forgot to mention the new Windows bug - OOB, or WinNuke as it's commonly known. As you probably already know, it allows anyone with a Unix shell acount to shut down someone else's Win 95/NT PC. Contrary to reports by most of the mainstream 'reliable' tech sources, this bug does not affect Windows 3.x, only the network-enhanced 3.11 version is at risk, and just over a network.
The bug patch released last week by Microsoft to fix the OOB problem has a large hole in it that still allows anyone with a Mac to WinNuke a patched 95/NT PC. Ms has came out with a second patch for NT that corrects that mistake, but we can be sure more will be found eventually... No word on a second patch for 95 users.
|
|
|
|
|
|
|
|
![[Copyright Bar]](../bottom.gif){kind=small}
Saturday, 16-Nov-2002 17:22:42 EST