From: John Hogerhuis <jhoger@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] slirp 64-bit fixes
Date: Thu, 19 May 2005 00:08:33 -0700 [thread overview]
Message-ID: <dd8f98f4050519000856f28781@mail.gmail.com> (raw)
In-Reply-To: <20050518230154.GE3051@sentinelchicken.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.
>
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.
next prev parent reply other threads:[~2005-05-19 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 8:57 [Qemu-devel] [PATCH] slirp 64-bit fixes Gwenole Beauchesne
2005-05-18 4:07 ` John Hogerhuis
2005-05-18 23:01 ` Tim
2005-05-19 7:08 ` John Hogerhuis [this message]
2005-05-20 3:07 ` Adrian Smarzewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd8f98f4050519000856f28781@mail.gmail.com \
--to=jhoger@gmail.com \
--cc=jhoger@pobox.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).