On 08/02/2010 10:06 PM, themagicm wrote:
>
> I have a box running 11.3. I have a non-standard ssh port setup for
> myself. If I have only 2 ports being allowed… NFS and ssh of course.
>
> Is it safe to say that any other port is being blocked? If is not
> specifically allowed in SuSEfirewall2, then it should be blocked,
> correct?
>
> If this is not the case, is there a simple way to block ALL ports other
> than the ones I specifically want to let through?
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> By default, that is how it works, yes (block all, allow exceptions) which
> is the correct way to do something in security terms.
>
> Two of my favorite iptables commands:
>
> sudo /usr/sbin/iptables -L -v -n
> sudo /usr/sbin/iptables-save
>
> Good luck.
>
>
>
>
>
> On 08/02/2010 10:06 PM, themagicm wrote:
>>
>> I have a box running 11.3. I have a non-standard ssh port setup for
>> myself. If I have only 2 ports being allowed… NFS and ssh of course.
>>
>> Is it safe to say that any other port is being blocked? If is not
>> specifically allowed in SuSEfirewall2, then it should be blocked,
>> correct?
>>
>> If this is not the case, is there a simple way to block ALL ports other
>> than the ones I specifically want to let through?
>>
>>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.12 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
<snip>
> -----END PGP SIGNATURE-----
themagicm;
If you have any doubts about open ports, just run a port scanner such
as “nmap” from a remote machine against your machine. nmap should be
available for all major linux distributions and has been ported to Windows
versions NT and later.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green