[GH-ISSUE #202] Keystrokes are not visible when Bitwarden is running in the background #170

New issue

Closed

opened 2026-05-05 05:03:16 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 05:03:16 -06:00

Owner

Originally created by @darmiel on GitHub (May 6, 2021).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/202

When Bitwarden is running in the background, the keystrokes are no longer displayed. Only when you close Bitwarden completely, the keystrokes are shown again. Is this the way it should be?

https://user-images.githubusercontent.com/71837281/117328900-605c8100-ae94-11eb-9ba1-c5cddb60673b.mov

Originally created by @darmiel on GitHub (May 6, 2021). Original GitHub issue: https://github.com/keycastr/keycastr/issues/202 When Bitwarden is running in the background, the keystrokes are no longer displayed. Only when you close Bitwarden completely, the keystrokes are shown again. Is this the way it should be? https://user-images.githubusercontent.com/71837281/117328900-605c8100-ae94-11eb-9ba1-c5cddb60673b.mov

gitea-mirror closed this issue

2026-05-05 05:03:19 -06:00

gitea-mirror commented

2026-05-05 05:03:23 -06:00

Author

Owner

@akitchen commented on GitHub (May 8, 2021):

That's interesting, my best guess is that somehow keycastr isn't getting key events while Bitwarden is enabled. Not sure there's much we can do about it without being able to debug it locally, and I'm not a Bitwarden user.

@akitchen commented on GitHub (May 8, 2021): That's interesting, my best guess is that somehow keycastr isn't getting key events while Bitwarden is enabled. Not sure there's much we can do about it without being able to debug it locally, and I'm not a Bitwarden user.

gitea-mirror commented

2026-05-05 05:03:26 -06:00

Author

Owner

@darmiel commented on GitHub (May 9, 2021):

Looks like this is an electron thing: app.setSecureKeyboardEntryEnabled

By using this API, important information such as password and other sensitive information can be prevented from being intercepted by other processes

👉 Apple TN2150

Doesn't look like there's anything you can do about it (on keycastr-side). I think that the issue can be closed with this.

EDIT: There is already an issue on Bitwarden/Desktop that describes exactly the problem: https://github.com/bitwarden/desktop/issues/738

@darmiel commented on GitHub (May 9, 2021): Looks like this is an electron thing: [app.setSecureKeyboardEntryEnabled](https://www.electronjs.org/docs/api/app#appsetsecurekeyboardentryenabledenabled-macos) > By using this API, important information such as password and other sensitive information can be prevented from being intercepted by other processes 👉 Apple [TN2150](https://developer.apple.com/library/archive/technotes/tn2150/_index.html) Doesn't look like there's anything you can do about it (on keycastr-side). I think that the issue can be closed with this. **EDIT**: There is already an issue on Bitwarden/Desktop that describes exactly the problem: https://github.com/bitwarden/desktop/issues/738

gitea-mirror commented

2026-05-05 05:03:28 -06:00

Author

Owner

@akitchen commented on GitHub (Jun 13, 2021):

It sort of makes sense, if secure input mode is meant to stop other applications receiving potentially sensitive keystrokes (similar to a password entry mode).

Closing this since we're not able to do anything about it, but thank you for opening an issue and following up.

@akitchen commented on GitHub (Jun 13, 2021): It sort of makes sense, if secure input mode is meant to stop other applications receiving potentially sensitive keystrokes (similar to a password entry mode). Closing this since we're not able to do anything about it, but thank you for opening an issue and following up.