Roger
Thu Feb 22 14:23:04 CST 2007
The first determines whether password is needed to unlock
screensaver once it has kicked in. Since .Default is also used
for the machine in state when no one is locally logged in it is
doubtful one would want this set to 1 although that would make
it so in subsequent, new profiles.
The second is a bigger concern. These are the filenames of
dlls that get passed the clear password during a password
change and are intended to allow for custom password strength
control, the dll being able to tell LSA to refuse the new pwd,
but these have since found other uses including invasion.
These, commonly called password filters, go away in the
Longhorn/Vista era.
I am not sure what your scanner is saying, but it apparently
is seeing more than scecli and not commonly provided dlls
from MS (?).
http://technet2.microsoft.com/WindowsServer/en/library/5d71e79e-cbdf-40cd-8dcd-3b630bdc1bbd1033.mspx?mfr=true
"Jarrath" <jarrath.mooney@gmail.com> wrote in message
news:978D6050-7EA2-4A6A-8BDB-9AC71F031C08@microsoft.com...
> We've been running a security application to scan some of our servers and
> it
> flagged the below reg keys. Can someone explain what these reg keys are
> and
> what they are used for. I've included the error msg flagged with the
> HKEY_LOCAL_MACHINE reg... Thanks for any help
>
> HKEY_USERS\\.Default\\Control Panel\\Desktop\\ScreenSaverIsSecure
>
> HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\LSA\\Notification
> Packages
> (error msg received.)
> Data: FPZECLQT RTTSTM SDCEEC scecli; expected data to match regular
> expression: PAWWFGLT; comment: Palefilt
>