B
Barry Watzman
The firewall configuration is very simple for almost all programs.
Basically, the first time that you use a program that tries to use a
blocked port, you get a windows with 3 choices:
-Unblock that port for this program [only] -- whenever this program is
run (window won't come up again for that program)
-Unblock that port for this program -- one time only (window will come
up again next time that program is run)
-Don't unblock the port (the program probably won't run correctly, of
course)
In most cases, it's trivial and you don't need to know anything about
what port the program is using, just tell the firewall if it is or is
not "ok" to run that program.
There's a control panel that you can get into where you can manually add
and remove programs, change their status, or diddle with the list
allowed on a program by program basis. It's there, but will rarely be
used by typical users running typical programs.
Actually, I think that they did it very, very well.
Basically, the first time that you use a program that tries to use a
blocked port, you get a windows with 3 choices:
-Unblock that port for this program [only] -- whenever this program is
run (window won't come up again for that program)
-Unblock that port for this program -- one time only (window will come
up again next time that program is run)
-Don't unblock the port (the program probably won't run correctly, of
course)
In most cases, it's trivial and you don't need to know anything about
what port the program is using, just tell the firewall if it is or is
not "ok" to run that program.
There's a control panel that you can get into where you can manually add
and remove programs, change their status, or diddle with the list
allowed on a program by program basis. It's there, but will rarely be
used by typical users running typical programs.
Actually, I think that they did it very, very well.