sudo without password

[Adriano Varoli Piazza]

2006/6/9, Luis <lemsx1 at gmail.com>:
> I like the MacOS X approach in this manner. Install a firewall that's
> integrated with the known packages that listen for known ports.
> Essentially, when you go to open/close a port in your firewall, it
> allows you to add your own custom ports, and in one list allows you to
> quickly check/uncheck the ports that are already listening in your
> system. It works the other way around as well, installing a new system
> assumes that you want that system to listen for a connection, and
> opens the port in the firewall for you. Risky? Well, you should read
> the description of the program you are installing before you actually
> install it. I like the Debian approach, but I see a problem with new
> comers. There is no easy fix that satisfy both worlds. But the MacOS X
> approach is very intuitive.

On the subject of firewalls, I'd like something on Linux that by
default closes everything and then graphically or CLI-lly asks you
when you first try to open a port. The way I've seen Windows Firewall
doing, lately. It's a way to know when something's trying to talk
behind your back.

-- 
Adriano Varoli Piazza
The Inside Out: http://moranar.com.ar
ICQ: 4410132
MSN: moranar at gmail.com