Groups > alt.comp.os.windows-10 > #182491

Re: Windows Spotlight shows picture information data on lock screen of one PC, but not others.

From	Java Jive <java@evij.com.invalid>
Newsgroups	alt.comp.os.windows-10
Subject	Re: Windows Spotlight shows picture information data on lock screen of one PC, but not others.
Date	2025-02-22 20:50 +0000
Organization	A noiseless patient Spider
Message-ID	<vpddaq$4f8p$1@dont-email.me> (permalink)
References	<vpctqt$1jqq$1@dont-email.me> <vpd8ad$3i85$1@dont-email.me> <vpddef.ufg.1@ID-201911.user.individual.net>

Show all headers | View raw

On 2025-02-22 19:52, Frank Slootweg wrote:
>
> Java Jive <java@evij.com.invalid> wrote:
>>
>> As Paul suggests, this is, or at least used to be, something of a
>> security issue, as described here ...
>>
>> https://www.manageengine.com/vulnerability-management/misconfiguration/logon-security/how-to-enable-secure-login-ctrl-alt-delete-logon-via-group-policy.html
>>
>> ... and accordingly I've always previously disabled this policy on my
>> builds, so that <Ctrl-Alt-Delete> is required to log on.  How much of an
>> issue this is still, or whether more recent versions of Windows are more
>> secure against logon window spoofing rendering the policy redundant, I'm
>> no longer sufficiently in the know to be able to comment further.
> 
>    Be aware that 'Require CTRL-ALT-DEL' [1] might be turned on again
> behind your back. At least that happened to me (on Windows 11) when I
> (temporarily) set the lock screen timeout ('If you've been away, when
> should Windows require you to sign in again?') to 'Never'.
> 
>    That seemed to be a temporary change, because after a reboot,
> CTRL-ALT-DEL was no longer needed to sign-in.
> 
> [1] There is an applet (netplwiz) where you can tick/untick 'Require
> users to press Ctrl+Alt+Delete' ("Secure sign-in"), but (at least in my
> experience) it doesn't work, i.e. after unticking the setting,
> Ctrl+Alt+Delete is still required.

Thanks for the warning.

Looking at your experience described above, depending on how it was 
changed, I suspect a reboot can be required to pick up a permanent 
change to this setting.  To be exact, I'm guessing:
     Legacy method, such as netplwiz or gpedit:
         Changes policy, reboot required for new policy to be copied to 
current run settings;
     Settings app:
         Changes only current run settings, not underlying policy, so 
lost on reboot.

Does this make sense?  Frank or anyone else care to comment?

-- 

Fake news kills!

I may be contacted via the contact address given on my website: 
www.macfh.co.uk

Thread

csiph-web