Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Object navigation works when the system is locked #2449

Closed
nvaccessAuto opened this issue Jun 13, 2012 · 4 comments
Closed

Object navigation works when the system is locked #2449

nvaccessAuto opened this issue Jun 13, 2012 · 4 comments

Comments

@nvaccessAuto
Copy link

Reported by aliminator on 2012-06-13 15:43
When using NVDA (both portable or installed) it is possible to explore the screen although the system is locked.
In some cases, it was even possible to click on some elements.
In that scenario, navigation commands such as NextObjectInSameHierarchy etc. have been assigned to the keys of a braille display.
If there is a script handler executing those commands it should check whether the system is locke rather than catching specific keys such as the numlock key strokes.

@nvaccessAuto
Copy link
Author

Comment 1 by jteh on 2012-06-13 17:12
The correct solution is to suspend braille on secure desktops, though we may need to come up with an interim solution. See also #2315.
Changes:
Milestone changed from None to 2012.3

@nvaccessAuto
Copy link
Author

Comment 2 by aliminator on 2012-06-18 07:40
Maybe suspending braille on secure desktops can be implemented as unloading the braille display driver when it becomes active and then reload the driver again when secure desktop is left.
However, this issue doesn't seem to be resolved when NVDA is active (with general system settings) on secure desktops. Hence, it might be necessary to check the current environment (secure desktop etc.) and then trigger execution of the object navigation scripts. Maybe this should be extended to other scripts which should not be executed in secure desktops.

@nvaccessAuto
Copy link
Author

Comment 3 by jteh (in reply to comment 2) on 2012-06-18 07:49
Replying to aliminator:

However, this issue doesn't seem to be resolved when NVDA is active (with general system settings) on secure desktops. Hence, it might be necessary to check the current environment (secure desktop etc.) and then trigger execution of the object navigation scripts.

It isn't resolved because the secure desktop copy of NVDA can't access the braille display unless the main copy releases it. If the main copy suspends braille as it should, you won't be able to perform object navigation via the main copy.

@nvaccessAuto
Copy link
Author

Comment 5 by jteh on 2012-08-01 05:21
Fixed in 32ec953. This doesn't suspend braille as I suggested, but it does solve the security problem by putting NVDA in sleep mode while a secure desktop is active.
Changes:
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants