From: Dan Kegel <dank@kegel.com>
To: Ralf Baechle <ralf@uni-koblenz.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: socket connected to itself with RH 2.2.14-5.0? (Problem with example from Stevens)
Date: Wed, 22 Aug 2001 20:03:49 -0700 [thread overview]
Message-ID: <3B847295.5127D1F8@kegel.com> (raw)
In-Reply-To: <3B82C7F2.43A60829@kegel.com> <20010822120619.A13189@dea.linux-mips.net>
Ralf Baechle wrote:
>
> On Tue, Aug 21, 2001 at 01:43:30PM -0700, Dan Kegel wrote:
> > tcp 0 0 127.0.0.1:2003 127.0.0.1:2003 ESTABLISHED 965/client
> >
> > Erm, could the client have connected to *itself* somehow?
>
> I would not consider that a bug even though certainly not very helpful.
> Now I wonder if this could potencially be abused for nice DoS attacks ...
After running the server on a port not in the ephemeral range,
the problem goes away. It's just a funny thing that can happen
when you're connecting to a server on your own box, so no big deal.
- Dan
--
"I have seen the future, and it licks itself clean." -- Bucky Katt
prev parent reply other threads:[~2001-08-23 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 20:43 socket connected to itself with RH 2.2.14-5.0? (Problem with example from Stevens) Dan Kegel
[not found] ` <20010822120619.A13189@dea.linux-mips.net>
2001-08-23 3:03 ` Dan Kegel [this message]
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=3B847295.5127D1F8@kegel.com \
--to=dank@kegel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@uni-koblenz.de \
/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