From: "Paul Ranson" 

Are you proposing a 'super administrator' priviledge to over come this?

Sticking used Elastoplasts on the firewall configuration options to attempt
to protect users running as administrator from malware running as
administrator is completely futile. Say it asked for the password, as
administrator I just set the password to something I know before
configuring the firewall. And if as administrator I cannot configure the
firewall configuration password the system is unusable by any real person.

Paul

"Geo"  wrote in message
news:432f6e2c$2{at}w3.nls.net...
> So who doesn't run as administrator on their own machine?
>
> Geo.
>
> "Paul Ranson"  wrote in message
> news:432ed47e{at}w3.nls.net...
>> Because you cannot adjust the firewall settings without 'administrator'
>> priviledge.
>>
>> Paul
>>
>> "Geo"  wrote in message
news:432a2b1d{at}w3.nls.net...
>> > What is already the case? I suggested that when a firewall rule change
> is
>> > detected that the firewall software verify that the change is
>> > authorized
>> > by
>> > asking the user for a password before allowing the change to go into
>> > effect.
>> >
>> > Geo.
>> >
>> > "Paul Ranson"  wrote in message
>> > news:43294b61$1{at}w3.nls.net...
>> >> If you're running as a 'USER' then surely that is already
the case? If
>> >> you're running as administrator then you've already authenticated
>> >> yourself
>> >> to the machine.
>> >>
>> >> Paul
>>
>>
>
>

--- BBBS/NT v4.01 Flag-5