From: /dev/rob0 <rob0@gmx.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: opening port for SSH
Date: Thu, 8 Dec 2005 08:23:10 -0600 [thread overview]
Message-ID: <200512080823.10443.rob0@gmx.co.uk> (raw)
In-Reply-To: <dn9dag$je3$1@sea.gmane.org>
On Thursday 2005-December-08 07:43, Edwin Kapauni wrote:
> Now, I need some help teaching me how to open ports for SSH and VoIP.
> That shouldn't be too difficult, right?
SSH, simple. VOIP, depends on what protocol[s] you mean, but no, in
general it should not be difficult.
iptables -A INPUT -p tcp --dport ssh -j ACCEPT
Ensure that your users have strong passwords and/or disable password
authentication altogether, because many worms/bots (I think run by and
for phishers) are probing the Internet for openings in TCP port 22 and
attempting to login using common usernames and passwords.
For any well-configured host these attacks are nothing more than an
annoyance, but you might wish to do some kind of blocking to limit the
login attempts, if for no other reason than to reduce the noise in
logging. There have been "-m recent" and "-m limit" ideas posted here
to do that. If you have the "recent" match extension, that is probably
better overall, but the "limit" approach is good enough for me.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
next prev parent reply other threads:[~2005-12-08 14:23 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 [this message]
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
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=200512080823.10443.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.