From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DYfC1-00031V-Rh
	for qemu-devel@nongnu.org; Thu, 19 May 2005 03:11:42 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DYfBA-0002mf-Bb
	for qemu-devel@nongnu.org; Thu, 19 May 2005 03:10:49 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DYfAp-0000vA-0n
	for qemu-devel@nongnu.org; Thu, 19 May 2005 03:10:27 -0400
Received: from [64.233.184.197] (helo=wproxy.gmail.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DYfHB-0003Mv-Pf
	for qemu-devel@nongnu.org; Thu, 19 May 2005 03:17:01 -0400
Received: by wproxy.gmail.com with SMTP id 71so314392wra
	for <qemu-devel@nongnu.org>; Thu, 19 May 2005 00:08:33 -0700 (PDT)
Message-ID: <dd8f98f4050519000856f28781@mail.gmail.com>
Date: Thu, 19 May 2005 00:08:33 -0700
From: John Hogerhuis <jhoger@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] slirp 64-bit fixes
In-Reply-To: <20050518230154.GE3051@sentinelchicken.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <Pine.LNX.4.58.0505171054360.21768@thalys.mandrakesoft.com>
	<dd8f98f405051721077d31756a@mail.gmail.com>
	<20050518230154.GE3051@sentinelchicken.org>
Reply-To: jhoger@pobox.com, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

On 5/18/05, Tim <tim-qemu@sentinelchicken.org> wrote:
> I found a number of security holes in slirp before, and tried to notify
> them.  I found the package isn't being maintained anymore.
>=20


I contacted the current maintainer, and he said the package needs a
new maintainer. I advised him to make a note of this on his webpage
since this is not mentioned, hopefully he'll find someone.

If anyone is interested in taking over maintenance of standalone
Slirp, contact Kelly Price: tygris _at_ cablespeed  "dot" com.

-- John.