From: Koyama Mituru <netfilter@gvelo.ddnn.jp>
To: netfilter@lists.netfilter.org
Subject: Re: ssh
Date: Thu, 15 Jul 2004 00:57:59 +0900 (JST) [thread overview]
Message-ID: <20040715.005759.28779742.netfilter@gvelo.ddnn.jp> (raw)
In-Reply-To: <2E314DE03538984BA5634F12115B3A4E62E89F@email1.mitretek.org>
[-- Attachment #1: Type: Text/Plain, Size: 593 bytes --]
From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
Subject: RE: ssh
Date: Wed, 14 Jul 2004 11:26:10 -0400
> Should all incoming ports that relate to a service such as SSH, FTP use
> -m state --state NEW?
>
> I have never used this with iptables; but I remember using it with
> ipfilter.
>
> What are the security implications (if any) of not using -m state
> --state NEW?
iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A INPUT -p tcp --dport 22 -m state --state NEW -j ACCEPT
I don't want other packets.
--
Koyama Mituru netfilter@gvelo.ddnn.jp
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-14 15:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 15:26 ssh Piszcz, Justin Michael
2004-07-14 15:42 ` ssh Antony Stone
2004-07-14 15:57 ` Koyama Mituru [this message]
2004-07-14 16:07 ` ssh Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2004-07-14 14:15 ssh IT Clown
2004-07-14 14:25 ` ssh Koyama Mituru
2003-01-14 21:28 ssh Simpson, Doug
2003-01-15 12:09 ` ssh Zander
2003-01-15 18:44 ` ssh MAB
2003-01-14 19:59 ssh Simpson, Doug
2002-06-24 12:23 ssh Daniel Sercaianu
2002-06-24 13:31 ` ssh Antony Stone
2002-06-24 13:47 ` ssh Maciej Soltysiak
2002-06-24 13:56 ` ssh Ramin Alidousti
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=20040715.005759.28779742.netfilter@gvelo.ddnn.jp \
--to=netfilter@gvelo.ddnn.jp \
--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