assistance:Secure_Input_Problem
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| assistance:Secure_Input_Problem [2017/11/05 04:02] – peternlewis | assistance:Secure_Input_Problem [2024/08/13 03:07] (current) – peternlewis | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Secure Input Problem ====== | ====== Secure Input Problem ====== | ||
| - | Mac OS X will not let applications watch the keyboard when you are in a password field (to prevent hackers getting hold of your passwords). However, the system can sometimes get into a state where it thinks it is permanently in a password fields. There are many possible culprits for this but almost anything that asks for a password could cause the problem (eg, web password fields, web password managers, VPN connections, | + | macOS will not let applications watch the keyboard when you are in a password field (to prevent hackers getting hold of your passwords). However, the system can sometimes get into a state where it thinks it is permanently in a password fields. There are many possible culprits for this but almost anything that asks for a password could cause the problem (eg, web password fields, web password managers, VPN connections, |
| Keyboard Maestro will tell you if it detects the system is in Secure Input Mode and if possible indicate the process which is causing the issue in the Keyboard Maestro status menu or by clicking the yellow warning triangle in the bottom right corner of the Keyboard Maestro editor. | Keyboard Maestro will tell you if it detects the system is in Secure Input Mode and if possible indicate the process which is causing the issue in the Keyboard Maestro status menu or by clicking the yellow warning triangle in the bottom right corner of the Keyboard Maestro editor. | ||
| - | Note that there is nothing Keyboard Maestro can do to “work around” | + | Note that if a background process enables |
| - | There is a [[https:// | + | If Keyboard Maestro reports the `loginwindow` as the process, that just means that it is likely a Startup Agent or Daemon asking for the password that is causing the problem, but unfortunately Keyboard Maestro was unable to determine which process in particular has the Secure Input Mode enabled. |
| + | |||
| + | Note that there is nothing Keyboard Maestro can do to “work around” Secure Input Mode - it is a system security feature that has been erroneously left on. Keyboard Maestro can detect and report it, but it can no more work around the problem than it could bypass any other security features of macOS. | ||
| + | |||
| + | There is a [[https:// | ||
| + | |||
| + | * 1Password | ||
| + | * Authy | ||
| + | * Box | ||
| + | * Chronories | ||
| + | * Firefox | ||
| + | * Fluid | ||
| + | * Game Center | ||
| + | * Google Chrome | ||
| + | * Hulu Desktop | ||
| + | * iFinance | ||
| + | * Keybase | ||
| + | * LastPass | ||
| + | * loginwindow | ||
| + | * Notational Velocity | ||
| + | * Parallels Desktop 9 and 10 | ||
| + | * Quicken Scheduler | ||
| + | * Safari | ||
| + | * Slack | ||
| + | * Terminal | ||
| + | * Webroot SecureAnywhere | ||
| + | |||
| + | I also have reports of: | ||
| + | |||
| + | * Bitwarden (possibly the " | ||
| If you continue to have problems, [[https:// | If you continue to have problems, [[https:// | ||
assistance/Secure_Input_Problem.1509854553.txt.gz · Last modified: by peternlewis
