Re: firewall
On Wed, 4 Jul 2012 15:04:03 +0800
lina <lina.lastname@gmail.com> wrote:
>
> Ha... I just realized mine is exposed at least in our department. I
> can see the open ports and the OS. Just sometimes wish it can be
> invisible in some way.
>
Most ports can be closed by configuration, even the infamous portmap
can be limited to localhost if you're not using it externally e.g. for
NIS or NFS. If you have a standalone Linux machine in a foreign
network, pretty much everything can be closed.
I'd have thought most of the simple firewall frontends would do what
you need. If they are simple to configure, then they tend not to be
very flexible, so if you need the full power of iptables, you have no
choice but to learn to use it. But just to keep out random automatic
attacks, which may or may not be looking for Linux machines in a
Windows network, one of the simple ones should work.
I gave firestarter a go on my workstation, but it didn't really suit me
and is now not under development. The package description suggests gufw
as a modern replacement, but I know nothing about that.
--
Joe
Reply to: