All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raymond Leach <raymondl@knowledgefactory.co.za>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: Source Port
Date: 15 Apr 2003 13:11:26 +0200	[thread overview]
Message-ID: <1050405086.1439.47.camel@raylinux.internal> (raw)
In-Reply-To: <1050404537.1482.19.camel@india>

[-- Attachment #1: Type: text/plain, Size: 959 bytes --]

Why? In the specific example that you give, what would be the
implications?


On Tue, 2003-04-15 at 13:02, Dharmendra.T wrote:
> Hi Everyone, 
> 
> I am a regular reader of this list and I have absorbed that most of
> the users won't use the source ports in their rules. Say for ex, 
> 
> #iptables -A INPUT -s 192.168.1.0/24 -p tcp -d 0/0 --dport 23 -j
> ACCEPT 
> 
> In these kind of rules they will not specify the source port from 1024
> to 65545. I strongly recommend all Linux Users to specify the exact
> rules what is allowed and what is not allowed. 
> 
> Any Comments? This could be a good practise? 
> -- 
> Regards
> Dharmendra.T
> 
> 
> This message is intended for the addressee only. It may contain privileged or Confidential information. If you have received this message in error,please notify the sender and destroy the message immediately.Unauthorised use or reproduction of this message is strictly prohibited.



[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-15 11:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 11:02 Source Port Dharmendra.T
2003-04-15 11:11 ` Raymond Leach [this message]
2003-04-15 12:50   ` Dharmendra.T
2003-04-15 15:22 ` Michael K
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16  7:26 Julian Gomez
2003-04-16 10:07 ` Michael K
2003-04-16 11:12   ` Dharmendra.T

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=1050405086.1439.47.camel@raylinux.internal \
    --to=raymondl@knowledgefactory.co.za \
    --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.