From: Ethan Benson <erbenson@alaska.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Why I can't bind the 1023 port?
Date: Tue, 11 Jun 2002 00:02:38 -0800 [thread overview]
Message-ID: <20020611000238.E9152@plato.local.lan> (raw)
In-Reply-To: <1023738158.3382.17.camel@whitefusion.lan>; from owen@penguinppc.org on Mon, Jun 10, 2002 at 07:42:37PM +0000
On Mon, Jun 10, 2002 at 07:42:37PM +0000, Owen Stampflee wrote:
>
> On Tue, 2002-06-11 at 02:18, Daniel Lao wrote:
> > The running result was that I could not bind these ports: 1023, 1022, ...
> > but it was success in bind 1024 port.
> > And while I su to as the super-user, I could bind all these ports!
> > I am wondering if the ports were really protected, and how can I use the ports?
>
> Yes, ports < 1024 are reserved ports for "public" applications and only
> the superuser can bind them. To use them, you need to be a superuser. I
> am not familar with rcp (I would use scp even for local transfers) but
> it should be able to run on another port.
no it can't, thats why rcp must always be suid root, the entire
no-security model behind rcp/rlogin etc is `if its connecting *from* a
privileged port it can't lie to us about the user its trying to
connect as so we allow the connection'
obviously this is completly flawed model and why you should use ssh/scp
and not rcp/rlogin.
--
Ethan Benson
http://www.alaska.net/~erbenson/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-11 8:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 2:18 Why I can't bind the 1023 port? Daniel Lao
2002-06-10 19:42 ` Owen Stampflee
2002-06-11 8:02 ` Ethan Benson [this message]
2002-06-11 2:38 ` [OT] " Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2002-06-11 3:20 Daniel Lao
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=20020611000238.E9152@plato.local.lan \
--to=erbenson@alaska.net \
--cc=linuxppc-dev@lists.linuxppc.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).