Re: Other Open Ports

2012-07-24 Thread Mike McClain
Howdy, On Mon, Jul 23, 2012 at 01:21:55PM -0500, Charles Kroeger wrote: > I'm thinking my firewall 'Shorewall' encompasses an extensive enough design to > cover any attempts of intrusion that may occur, I do notice notwithstanding, > that > although ports 0 and 1 are closed, they still show up on

Re: Other Open Ports

2012-07-23 Thread Bob Proulx
Charles Kroeger wrote: > PORT STATE SERVICE > 25/tcp open smtp > 53/tcp open domain > 111/tcp open rpcbind > 631/tcp open ipp > 6566/tcp open sane-port That seems pretty reasonable. Except if you aren't using NFS and don't need the portmapper (rpcbind) then I would uninstall it. >

Re: Other Open Ports

2012-07-23 Thread Charles Kroeger
>Try probing your system with nmap and see what it > says. > nmap localhost Thanks for this information, I didn't have nmap installed..however after I did install nmap I received this: /charles# nmap localhost Starting Nmap 6.00 ( http://nmap.org ) at 2012-07-23 22:30 CDT Nmap scan report for

Re: Other Open Ports

2012-07-23 Thread Bob Proulx
Charles Kroeger wrote: > I'm thinking my firewall 'Shorewall' encompasses an extensive enough design to > cover any attempts of intrusion that may occur, I do notice notwithstanding, > that > although ports 0 and 1 are closed, they still show up on test like grc.com's > 'shields-up' port scanner.