mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Satchell <list@fluent2.pyramid.net>
To: Daniel Egger <degger@fhm.edu>, hps@intermeta.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: One for the Security Guru's
Date: Fri, 25 Oct 2002 09:38:54 -0700	[thread overview]
Message-ID: <5.1.0.14.0.20021025091912.01d986d0@fluent2.pyramid.net> (raw)
In-Reply-To: <1035500731.439.4.camel@sonja.de.interearth.com>

At 02:28 PM 10/25/02 +0200, Daniel Egger wrote:
>Don't laugh; I had such a box reinstalled from ground just the day
>before yesterday because I found a RedHat full Install on it. Not to
>mention that there're "admins" out there who use GNOME as root on a
>fairly busy mailserver <shudder>...

I'm not laughing, I inherited a firewall box that had a full install of Red 
Hat 7.1, complete with GUI.  I got the network information, loaded up 7.3 
with minimal installation, and cleaned up that "minimal install" by using 
"rpm -qa" (it's your friend) to identify and rid the system of every single 
package not necessary to the operation of a firewall.

GCC.  PERL.  Sendmail (!). The eight different version of FTP.  (I may be 
exaggerating, but the stream of packages that offer FTP client and server 
services seems to be endless.)  Things that a root kit would find extremely 
useful to install back doors and other nasties.  Debuggers.  Those were 
just the extra packages -- I also scanned for unnecessary SUID binaries 
when I was finished and blasted them to the ol' game grid.

I then used IPTABLES to implement the security policy of the client, and 
part of that policy was that the only packets that were allowed to talk 
directly  to the firewall was SSH, and only from my range of IP addresses, 
and ping from anywhere...and I rate-limited the ping to 10 per second so 
that a ping flood would not hose the return channel.

Incoming SYN requests to the firewall (except for SSH directed to the 
firewall) are alway dropped silently, and the vast majority of UDP packets 
also find their way to the bit bucket.  Oddball TCP attacks (the log showed 
a LAMP-TEST packet attack last week) are also given the heave-ho.  I have 
NAT in the outgoing direction, and only those ports necessary to the 
operation of the client are open.  That means no ICQ, at all, for 
example.  No streaming audio.  And, as you can guess, no outbound 
connections are accessible to the likes of BackOrfice.

I'm sure there is a hole somewhere in that firewall box, but I have plugged 
all the ones I found documented on CERT.

Oh, and a low-volume Web server was moved off the firewall and onto a 
separate box, with the firewall forwarding packet traffic via IPTABLES rules.


  parent reply	other threads:[~2002-10-25 16:32 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23 13:02 Robert L. Harris
2002-10-23 13:13 ` John Jasen
2002-10-23 13:20 ` Keith Owens
2002-10-24  7:56   ` Greg KH
2002-10-23 13:45 ` Alan Cox
2002-10-23 13:59   ` Gilad Ben-ossef
2002-10-23 22:14     ` James Cleverdon
2002-10-23 22:17       ` James Stevenson
2002-10-23 22:39         ` James Cleverdon
2002-10-23 22:44           ` James Stevenson
2002-10-24  6:12         ` Gilad Ben-Yossef
2002-11-06 21:39       ` Florian Weimer
2002-10-23 14:57 ` Richard B. Johnson
2002-10-23 17:56   ` Gerhard Mack
2002-10-24  9:38     ` Henning P. Schmiedehausen
     [not found]       ` <ap8f36$8ge$1@dstl.gov.uk>
2002-10-24 10:01         ` Tony Gale
2002-10-24 16:13           ` Gerhard Mack
2002-10-24 16:39             ` Henning P. Schmiedehausen
2002-10-24 16:34               ` David Lang
2002-10-24 17:04               ` Gilad Ben-Yossef
2002-10-25  9:44                 ` Henning Schmiedehausen
2002-10-25 20:52                   ` H. Peter Anvin
2002-10-26 10:43                     ` Henning P. Schmiedehausen
2002-10-27 10:17                       ` Rogier Wolff
2002-10-28  7:47                       ` Chris Wedgwood
2002-10-24 22:02               ` Danny Lepage
2002-10-25  9:40                 ` Henning Schmiedehausen
2002-10-24 14:23       ` Gilad Ben-ossef
2002-10-25  4:09       ` Stephen Satchell
2002-10-25 13:47         ` Stephen Frost
2002-10-26 10:38           ` Rogier Wolff
2002-10-26  9:44       ` Rogier Wolff
2002-10-26 10:46         ` Henning P. Schmiedehausen
2002-10-23 16:23 ` Henning P. Schmiedehausen
2002-10-23 17:55   ` David Lang
2002-10-23 19:46     ` H. Peter Anvin
2002-10-23 22:15 ` James Stevenson
2002-10-24  9:47   ` Henning P. Schmiedehausen
2002-10-25 12:28     ` Daniel Egger
2002-10-25 15:22       ` Alex Riesen
2002-10-25 16:38       ` Stephen Satchell [this message]
2002-10-25 18:21       ` [OT] " J Sloan
2002-10-26 10:40     ` OT " Rogier Wolff
2002-10-24 10:11   ` Ville Herva
2002-10-24 11:09     ` Henning P. Schmiedehausen
2002-10-24 11:55       ` Alan Cox
2002-10-24 14:40         ` Henning P. Schmiedehausen
2002-10-24 15:36           ` Alan Cox
2002-10-24 16:46     ` Eric W. Biederman
2002-10-24  6:04 ` David Wagner
2002-10-23 21:49 Hank Leininger

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=5.1.0.14.0.20021025091912.01d986d0@fluent2.pyramid.net \
    --to=list@fluent2.pyramid.net \
    --cc=degger@fhm.edu \
    --cc=hps@intermeta.de \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®