-----  !PLEASE READ THIS DOCUMENT IN IT'S ENTIRELY! ------

                      ***-<{Devilz Script}>-***

I am now providing an undo_fix.reg file which will bring the BSDUrgent key
back to its default state.  Please note that this will NOT remove the 
BSDUrgent key from the registry, but instead replace it with the original
value.  The default state of the registry is without the BSDUrgent key
entirely.  So, if you never played with this key before the OOB issue,
the undo_fix.reg file will put the parameter to 1, which is the default
when no BSDUrgent key is there.

Microsoft has also provided a patch.  Note that I have not tested it,
and there have been several reports that it does not work against the
mac or linux nukes, similar to the NT SP3 patch.  Information on it is
available at http://www.microsoft.com/kb/articles/q168/7/47.htm .

NEW INFORMATION DISCOVERED
After you apply this patch, any TCP servers you run will not handle OOB data
in an expected way.  This can be anything from a minor inconvience to you to
a major problem.  Therefore, once again, if you do not feel comfortable
doing this, wait for Microsoft's fix; one is expected soon.  For example,
FTP servers will not be able to process abort transfer commands correctly.

NOTE: WORKS ON WINDOWS 95 ONLY.  DO NOT APPLY TO WINDOWS NT
NOTE: THIS PATCH IS PROVIDED TO YOU AT YOUR OWN RISK. NO ONE IS
RESPONSIBLE TO ANY DAMAGE TO YOUR MACHINE EXCEPT YOU. IF YOU DO NOT
UNDERSTAND THE CONSEQUENCES, WAIT FOR AN OFFICIAL MICROSOFT FIX.

This is the latest and best(?) fix for the Windows 95 OOB hole that allows
anyone to crash your machine. This fix works on all releases of Windows
95 (950/950a and 950b/1111[OSR2]). This patch *does* allow Netbios to
work as it usually does (e.g. LAN f/p sharing) Simply double click on
the .reg file included in this zip and reboot.
 
You may then undo whatever temporary fix you have done. To undo it, you
must use regedit to remove the BSDUrgent key entirely. Please let any
one of us know of any troubles.

Here is a direct quote from my source (for win95)
http://www.microsoft.com/kb/articles/q158/4/74.htm

Hkey_Local_Machine\System\CurrentControlSet\Services\VxD\MSTCP

BSDUrgent = 0 or 1

If this value is 1, specifies that Microsoft TCP/IP is to treat urgent data
the way some UNIX systems do (with a maximum of 1 byte of urgent data, for
example). If this value is 0, it specifies that the stack is to handle
urgent data as specified by RFC 1122. The default is 1.

Join #SuSuFamily or #15thn in DalNet/WEBNET for the latest in breaking news.


Aizat Jani {CoLd^^pLaY}
Malaysia MIRC embassador  