From: Lionel Ulmer <lionel.ulmer@free.fr>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Feature request: option to disable protection in user mode networking
Date: Thu, 30 Sep 2004 22:04:31 +0200 [thread overview]
Message-ID: <20040930220431.A6196@bbland> (raw)
In-Reply-To: <1096574231.10584.10.camel@aragorn>; from jhoger@pobox.com on Thu, Sep 30, 2004 at 12:57:11PM -0700
On Thu, Sep 30, 2004 at 12:57:11PM -0700, John R. Hogerhuis wrote:
> Why would you consider a "forward-all" option to be a DoS?
Because, as you explain later in your mail 'slirp [...] has to create a
listening socket [...] on every port.' which means that you won't be able to
start any application on the box which needs to listen to a port.
I agree that 'DoS' is maybe too big a word as 'listening' applications are
rare, but well, it would still be a pain in the ass to have all 65535
available ports taken by one application.
Lionel
--
Lionel Ulmer - http://www.bbrox.org/
next prev parent reply other threads:[~2004-09-30 20:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-28 4:36 [Qemu-devel] Feature request: option to disable protection in user mode networking Mike MacCana
2004-09-30 7:25 ` Lionel Ulmer
2004-09-30 19:57 ` John R. Hogerhuis
2004-09-30 20:04 ` Lionel Ulmer [this message]
2004-09-30 8:45 ` Johannes Schindelin
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=20040930220431.A6196@bbland \
--to=lionel.ulmer@free.fr \
--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).