From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: 'Spiro Azkoul' <spiro@snacorp.net>, netfilter@lists.netfilter.org
Subject: RE: SUN RPC portmap
Date: Sat, 26 Jun 2004 11:51:04 -0700 [thread overview]
Message-ID: <SERVER7VjCRGryWtIIZ00000003@server7.bandwidthco.com> (raw)
In-Reply-To: <200406251600.i5PG0vD4005549@ylpvm29.prodigy.net>
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Spiro Azkoul
Sent: Friday, June 25, 2004 9:01 AM
To: netfilter@lists.netfilter.org
Subject: SUN RPC portmap
Can anyone think of a reason to simple block SUN RPC via iptables rather
than simply stopping the service if it is a mail/pop/imap/web server?
Thanks
It's normally referred to as "Defense-in-Depth". It is not recommended to
rely on a single method of security for anything. If the attacker gets
through the front line, it's always nice to know there is a second or third
or fourth, etc, etc, layer of defense to stop them.
prev parent reply other threads:[~2004-06-26 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 16:01 SUN RPC portmap Spiro Azkoul
2004-06-25 16:22 ` Daniel Wittenberg
2004-06-25 17:32 ` delay after [time patch] rule's expire =?unknown-8bit?q?m=2Ebar=FD=FE?= demiray
2004-06-25 17:57 ` Antony Stone
2004-06-25 17:59 ` SUN RPC portmap Antony Stone
2004-06-26 18:51 ` Mark E. Donaldson [this message]
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=SERVER7VjCRGryWtIIZ00000003@server7.bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=netfilter@lists.netfilter.org \
--cc=spiro@snacorp.net \
/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