1996-12-03 - Re: IP address

Header Data

From: The Deviant <deviant@pooh-corner.com>
To: “Bruce M.” <bkmarsh@feist.com>
Message Hash: 6d2b301e19b5a0c3faec9167557cc7ce222fc80cb6cf928aa7658a7582d21695
Message ID: <Pine.LNX.3.94.961203034021.3667A-100000@random.sp.org>
Reply To: <Pine.BSI.3.91.961202185629.4826A-100000@wichita.fn.net>
UTC Datetime: 1996-12-03 03:43:02 UTC
Raw Date: Mon, 2 Dec 1996 19:43:02 -0800 (PST)

Raw message

From: The Deviant <deviant@pooh-corner.com>
Date: Mon, 2 Dec 1996 19:43:02 -0800 (PST)
To: "Bruce M." <bkmarsh@feist.com>
Subject: Re: IP address
In-Reply-To: <Pine.BSI.3.91.961202185629.4826A-100000@wichita.fn.net>
Message-ID: <Pine.LNX.3.94.961203034021.3667A-100000@random.sp.org>
MIME-Version: 1.0
Content-Type: text/plain


-----BEGIN PGP SIGNED MESSAGE-----

On Mon, 2 Dec 1996, Bruce M. wrote:

> On Mon, 2 Dec 1996 ichudov@algebra.com wrote:
> 
> > > >What is the risk of publishing your dynamic IP address to a web page while you are on line?  How vulnerable is someone just connected to the internet, w/o any server running? What attacks are feasable? --Internaut
> > > 
> > > Well, if you are running Win95 (all) or 3.1 (w/certain TCP/IP stacks) your
> > > machine can be locked up or rebooted at *any* time using just PING!
> > > 
> > 
> > Isn't is Unix that is actually vulnerable?
> 
>     I have never been able to cause more than a mild performance 
> degredation by pinging a Windows 95 machine with large packets.  When 
> testing the idea I kept increasing the packet size until the machine no 
> longer responded, but the machine still had TCP/IP capabilities (in terms 
> of transmitting data and forming connections).  Ping flooding is another 
> matter though.  You probably could cause a larger performance drop.
> 

try sending big udp packets instead of big tcp packets; this kills windows
faster.

 --Deviant
   PGP KeyID = E820F015 Fingerprint = 3D6AAB628E3DFAA9 F7D35736ABC56D39

Traveling through hyperspace isn't like dusting crops, boy.
                -- Han Solo


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQEVAwUBMqOhizCdEh3oIPAVAQGmwQf8DFO8mdlkk2TQBTpmsYtGmjw5UsezqjkA
AayPyzks+6gcylQiqmOZkNb7LTAdClP3lVdz4nxBJYNUzYBSvYDlAJtRgFC+CR0u
NXTdr+FZVOjaqaQkFjyIipOCx51Ljsxzr6zXbKIOHTZI5FU20n/NZJaVYzluC9xm
VRu/DEXE54esI5QZIM77d8x5lltj15i88D5/Cq/ufb3xr0EBNK3FxklTgFIzxwuP
Bdedcf8Vb1EfI958RxAeZ/AQWFujlZSZPwQ6CScBfJiGb4CNv5zNcbiNP0vdpnl6
DgehGTXRNtD27pA2Y0gx9/AOQIiGGZ2RAmG94iJXn/iEecHQqunqpg==
=Tz+8
-----END PGP SIGNATURE-----






Thread