Subject: Crash in _ipllog
To: None <netbsd-help@netbsd.org>
From: James Webster <jamesweb@tsi-net.com>
List: netbsd-help
Date: 08/14/2001 10:59:06
This is a multi-part message in MIME format.

------=_NextPart_000_0027_01C124B0.23181770
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm running 1.3.3 on my gateway.  Since there are a bunch of people =
using it, I havent had time to upgrade it in some time, but within the =
last couple weeks I've seen a crash in _ipllog with eax set to =
0xdeadbeef.  Could someone point me a patch to fix this exploit, or =
should I just tell my users they have to be without connectivity for a =
couple hours while I move to 1.5.1?

Thanks,
James

------=_NextPart_000_0027_01C124B0.23181770
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2523.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I'm running 1.3.3 on my gateway.&nbsp; =
Since there=20
are a bunch of people using it, I havent had time to upgrade it in some =
time,=20
but within the last couple weeks I've seen a crash in _ipllog with eax =
set to=20
0xdeadbeef.&nbsp; Could someone point me a patch to fix this exploit, or =
should=20
I just tell my users they have to be without connectivity for a couple =
hours=20
while I move to 1.5.1?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>James</FONT></DIV></BODY></HTML>

------=_NextPart_000_0027_01C124B0.23181770--