Skip to contentSkip to conversation

Securing my box

DISCUSSION 1stFlight 3 participants 3 messages Nov 15, 2002

lore
Share & tools
lore

1stFlight

author
#0 lore raw

I recently had a friend port scan me as a test of my ip_tables based firewall And like I wanted he discovered there were no ports open. However if I do a "netstat -a | grep LISTEN" I see

tcp        0      0 localhost.localdom:1024 *:*                     LISTEN
tcp        0      0 *:printer               *:*                     LISTEN
tcp        0      0 *:sunrpc                *:*                     LISTEN
tcp        0      0 *:x11                   *:*                     LISTEN
tcp        0      0 *:ssh                   *:*                     LISTEN

What's going on here? Did I mess up my config? Thanks!

Darryl
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#1 lore raw

As far as I know this is the way it should be, I mean
you closed the access from outside; but not from your server. So someone from outside cannot connect to them, but you, from a shell on the server, can, of course...
Or did I misunderstood the question?

Greetz,
Bencze.

Quoted 11 lines · On Fri, 15 Nov 2002, 1stFlight wrote:

I recently had a friend port scan me as a test of my ip_tables based firewall And like I wanted he discovered there were no ports open. However if I do a "netstat -a | grep LISTEN" I see

tcp        0      0 localhost.localdom:1024 *:*                     LISTEN
tcp        0      0 *:printer               *:*                     LISTEN
tcp        0      0 *:sunrpc                *:*                     LISTEN
tcp        0      0 *:x11                   *:*                     LISTEN
tcp        0      0 *:ssh                   *:*                     LISTEN
Quoted 9 lines

What's going on here? Did I mess up my config? Thanks!

Darryl
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

#2 lore raw
In reply to 1stFlight
Quoted 4 lines · At 06:19 AM 11/15/02 -0500, 1stFlight wrote:

I recently had a friend port scan me as a test of my ip_tables based firewall And like I wanted he discovered there were no ports open. However if I do a "netstat -a | grep LISTEN" I see

Quoted 8 lines
tcp        0      0 localhost.localdom:1024 *:*                     LISTEN
tcp        0      0 *:printer               *:*                     LISTEN
tcp        0      0 *:sunrpc                *:*                     LISTEN
tcp        0      0 *:x11                   *:*                     LISTEN
tcp        0      0 *:ssh                   *:*                     LISTEN

What's going on here? Did I mess up my config? Thanks!

What's "going on here" is that you have applications on the host that are listening on those ports for incoming traffic. Offhand I can't say for sure what, but probably you are running lpd, sshd, the portmapper (say for NFS mounts) and XFree86 (I don't even have a guess for the 1024 entry).

From what your friend found in his portscan, you have firewalling software running somewhere between him and you that blocks his access to these same ports. If the " ip_tables based firewall" is software (more accurately, kernel configuration) running on this same host, -AND- it has only a single network interface, then running the apps that listen on these ports may be pointless (or not; X11 and lpd are surely providing local services as well). Except for the memory they use, running them is harmless. And if you have multiple interfaces (for example, a dial-up PPP connection and a NIC connecting you to a LAN), the firewall *might* be blocking access from the Internet while permitting it from the LAN ... that's one of the things firewalls do, after all.

So ... bottom line ... whether you "messed up" your config depends on undescribed details of your overall setup, and your intent.

--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [email protected]
-------------------------------------------------------------------------------

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs