4 ms·
Form a security standpoint I don't understand why Microsoft would even 'launch' any app (that's not necessary for login) while lock screen is on. The lock scree
by ROARosen 6y ago
Form a security standpoint I don't understand why Microsoft would even 'launch' any app (that's not necessary for login) while lock screen is on. The lock screen should be completely decoupled. It would be like trying to enter a URL in a browser while the browser app is closed which is basically impossible (I'm not talking about adding it as a cmd param).
- sp332 6y agoAccessibility tools are necessary for login.
- Retric 6y agoThen they should be part of the login application.
- derefr 6y agoThat would be even worse than the current state of things. Accessibility services are necessarily kernel services, since they tie deeply into considerations of what the OS should/shouldn’t allow the user to do at any point. Giving the login application its own copy of those services, would mean giving the login application (⇒ applications in general) the ability to tie as deeply into the OS as the accessibility services themselves do. Avoiding that is the whole reason accessibility was made an OS-level feature in the first place!
- Retric 6y ago> Giving the login application its own copy of these services... It’s much easier to have a lock/login screen that ties closely with the rest if the OS, but that’s not an actual requirement. As an extreme example Windows could split things so you have the login screen and the rest of windows as effectively two completely different VM’s that get swapped between. I am not saying that’s a good idea, but Microsoft is building the OS from the ground up they have a lot of options.
- deleted 6y ago[deleted]
- nine_k 6y agoThe idea is that the screen lock should directly call the kernel accessibility API, and not start other processes at all.
- derefr 6y agoIIRC, in this case it's the kernel accessibility API that's spawning these client processes from kernel-space, due to events the kernel is observing directly, rather than events being reported to the kernel from a userspace process — which is precisely how these accessibility helper UX processes get to be privileged in a way that regular userland processes aren't.
- shawnz 6y agoWhat about third-party accessibility tools, input methods, logon methods, etc?
- selfishgene 6y agoBackdoor for law enforcement?
- fortran77 6y agoUnfortunately, for people who need to type on letter at a time, or type with a mouthstick, there's a need to run accessibility helper programs.