["Stephen Samuel (leave the email alone)" <samnospam@xxxxxxxxxxx>]

I kinda squirm at the thought of loading yet more code into windows
memory on boot, ehen it's not always used.  I think that the best
approach would be to have it not loaded by default, but have it
still be an install-time option (for systems that use ethereal
rather often).

I realize that the code may not be all that big, but when
deciding policies, my backup thought is 'what would happen if
*everybody* did this?"  Besides, if it adds capabilities for
non-priveledged processes, some people might consider this to
be a security issue.


Lars Roland wrote:
> Mark Pizzolato schrieb:
> (snip)
>
> > The ethereal windows installer could probably be offer an option to 
> > enable the starting of NPF at system startup.  This would completely 
> > solve privilege separation for Windows and avoid the overhead of 
> > attempting to do these things in a separate process and pass all data 
> > to a display process.
> I've checked in a change to the installer. The option to start the NPF 
> at system startup is disabled by default. Should it be enabled by default?

--
Stephen Samuel +1(604)876-0426             samnospam@xxxxxxxxxxx
		   http://www.bcgreen.com/
   Powerful committed communication. Transformation touching
     the jewel within each person and bringing it to light.