From: Georgi Alexandrov <georgi.alexandrov@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: opening port for SSH
Date: Wed, 14 Dec 2005 22:46:31 +0200 [thread overview]
Message-ID: <43A084A7.9070003@gmail.com> (raw)
In-Reply-To: <uizoe3jefxt.fsf@false.linpro.no>
Bjørn Ruberg wrote:
>Because you don't want to run the risk of your SSH server being
>replaced by some shady regular-user process which will gladly pick up
>your login credentials, the smart thing is to bind services like SSH
>to ports below 1024.
>
>
Yes, it's better to run it < 1024 but different from 22 (default).
Actually the only plus for binding it != 22 is that you avoid filling
your log files with automatic scans/attacks.
regards,
Georgi Alexandrov
next prev parent reply other threads:[~2005-12-14 20:46 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
2005-12-14 20:46 ` Georgi Alexandrov [this message]
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=43A084A7.9070003@gmail.com \
--to=georgi.alexandrov@gmail.com \
--cc=netfilter@lists.netfilter.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