You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by tspivey on 2011-03-28 02:52
In secure mode, the logging level can be adjusted. This makes it possible to log
all keystrokes typed to the nvda.log file for that session.
The usefulness of this as an attack technique is questionable because the log file is only
readable by administrators, but the log is still being
written to disk, and could easily be read by a rescue system.
Would it be a large issue if logging was disabled in secure mode? If something
needed to be debugged on the secure desktop, the serviceDebug registry key could be set to disable secure mode.
The text was updated successfully, but these errors were encountered:
Reported by tspivey on 2011-03-28 02:52
In secure mode, the logging level can be adjusted. This makes it possible to log
all keystrokes typed to the nvda.log file for that session.
The usefulness of this as an attack technique is questionable because the log file is only
readable by administrators, but the log is still being
written to disk, and could easily be read by a rescue system.
Would it be a large issue if logging was disabled in secure mode? If something
needed to be debugged on the secure desktop, the serviceDebug registry key could be set to disable secure mode.
The text was updated successfully, but these errors were encountered: