full-disclosure - closing ports

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20031107163748.4b03aab2.chrome@liquidinfo.net>
From: chrome at liquidinfo.net (marko)
Subject: closing ports

Hi,

On Fri, 07 Nov 2003 02:58:04 -0500
"Christ-Henning Ljosheim" <chris@...asat.no> wrote:

> I've closed port 1214 and 6881 to 6889 . Anyone else I should close ?

I recommend you take the default approach of denying everything instead
of closing certain ports. After this has been done, allow the necessary
inbound traffic to your host(s) that you need. 

Home-users rarely need any inbound traffic, unless they're using some
P2P programs or similar stuff. Public servers on the other hand require
some ports open (how else could they serve?). For example a web-server
requires port 80 to serve any pages to clients, assuming the server is
setup to listen on that port.

-m-
-- 
- Liquid Information - http://www.liquidinfo.net
- E-mail: Remove NOS_PAM if present in address (Usenet)
- PGP: http://www.liquidinfo.net/about.html
--