[Courses] New to this list, so, hi!

[Elwing]

If you're blocking those ports at the firewall (from remote machines),
then the only thing you have to worry about are people inside the
firewall.  If you have other machines that could potentially be
compromised, I still suggest blocking the X ports locally.

Laura


> Hi laura, in reply to another reply, *sigh* this is

> confusing, i ran 'nmap -sT Mirrus'
>
> tarting nmap V. 2.54BETA34 ( www.insecure.org/nmap/ )
> Interesting ports on localhost (127.0.0.1):
> (The 1550 ports scanned but not shown below are in
> state: closed)
> Port       State       Service
> 22/tcp     open        ssh
> 37/tcp     open        time
> 111/tcp    open        sunrpc
> 113/tcp    open        auth
> 515/tcp    open        printer
> 6000/tcp   open        X11
>
> Nmap run completed -- 1 IP address (1 host up) scanned
> in 0 seconds
>
> *but* i ran a port scan at another site, port's
> 6000-6255, came back "stealth" like closed but better!
> Is it really needed to shut down access to these
> port's in this case, i have a firewall in place,
> blocking all remote, accepting all connection's from
> my box.
> Joe. :)
> P.S. if you think i'm being a little *over* safe, i
> like it that way!
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> Courses mailing list
> Courses at linuxchix.org
> http://mailman.linuxchix.org/mailman/listinfo/courses
>
>
>