From: Chris Wedgwood <cw@f00f.org>
To: Arun Sharma <arun.sharma@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving "special" port numbers in the kernel ?
Date: Sat, 16 Nov 2002 16:03:54 -0800 [thread overview]
Message-ID: <20021117000354.GA443@tapu.f00f.org> (raw)
In-Reply-To: <uel9mbcyi.fsf@unix-os.sc.intel.com>
On Fri, Nov 15, 2002 at 04:00:37PM -0800, Arun Sharma wrote:
> One of the Intel server platforms has a magic port number (623) that
> it uses for remote server management. However, neither the kernel
> nor glibc are aware of this special port.
Odd.
charon:~% grep -c 623 /etc/services
0
rfc1700:
[...]
WELL KNOWN PORT NUMBERS
The Well Known Ports are controlled and assigned by the IANA and on
most systems can only be used by system (or root) processes or by
programs executed by privileged users.
[...]
npmp-gui 611/tcp npmp-gui
npmp-gui 611/udp npmp-gui
# John Barnes <jbarnes@crl.com>
ginad 634/tcp ginad
ginad 634/udp ginad
I don't see port 623 in there. Where is this documented?
> As a result, when someone requests a privileged port using
> bindresvport(3), they may get this port back and bad things happen.
Indeed. It seems like they should be able to get this port.
What bad things happen?
> Has anyone run into this or similar problems before ? Thoughts on
> what's the right place to handle this issue ?
User-land. Fix broken applications.
--cw
prev parent reply other threads:[~2002-11-16 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-16 0:00 Reserving "special" port numbers in the kernel ? Arun Sharma
2002-11-16 0:11 ` Xavier Bestel
2002-11-16 0:53 ` Arun Sharma
2002-11-16 0:58 ` Sean Neakums
2002-11-16 1:00 ` Randy.Dunlap
2002-11-16 1:46 ` Arun Sharma
2002-11-16 2:03 ` Randy.Dunlap
2002-11-16 2:43 ` Alan Cox
2002-11-17 16:37 ` Arun Sharma
2002-11-17 22:59 ` Alan Cox
2002-11-16 7:30 ` Willy Tarreau
2002-11-17 0:03 ` Chris Wedgwood [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=20021117000354.GA443@tapu.f00f.org \
--to=cw@f00f.org \
--cc=arun.sharma@intel.com \
--cc=linux-kernel@vger.kernel.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