From: "Bjørn Ruberg" <bjorn@ruberg.no>
To: Nick Drage <nickd@metastasis.org.uk>
Cc: netfilter@lists.netfilter.org
Subject: Re: opening port for SSH
Date: Wed, 14 Dec 2005 23:06:25 +0100 [thread overview]
Message-ID: <43A09761.8050400@ruberg.no> (raw)
In-Reply-To: <20051214203623.GF21572@metastasis.org.uk>
Nick Drage wrote:
> On Wed, Dec 14, 2005 at 06:39:26 +0100, Bjørn Ruberg wrote:
[...]
> In order to bind to the correct port wouldn't the existing SSHD process
> need to be killed? Or at least redirected to listen on another port so
> the "shady" process could act as an intermediary. For that to happen
> wouldn't the attacker need root privileges anyway?
There are several ways to escalate privileges, most of which are not
netfilter related.
The point I was trying to make is that important services should not be
told to listen to ports above 1024.
--
Bjørn
next prev parent reply other threads:[~2005-12-14 22:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 13:43 opening port for SSH Edwin Kapauni
2005-12-08 14:23 ` /dev/rob0
2005-12-09 14:23 ` Georgi Alexandrov
2005-12-09 14:42 ` myhapwcforever
2005-12-09 15:37 ` Georgi Alexandrov
2005-12-14 16:02 ` Edwin Kapauni
2005-12-14 17:28 ` Rob Sterenborg
2005-12-14 17:39 ` Bjørn Ruberg
2005-12-14 20:36 ` Nick Drage
2005-12-14 22:06 ` Bjørn Ruberg [this message]
2005-12-14 20:46 ` Georgi Alexandrov
2005-12-10 14:43 ` myhapwcforever
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=43A09761.8050400@ruberg.no \
--to=bjorn@ruberg.no \
--cc=netfilter@lists.netfilter.org \
--cc=nickd@metastasis.org.uk \
/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