keybase / keybase/keybase-issues
Keybase OS X client enables secure input before logging in
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
I run TextExpander and after a reboot, TextExpander complains that a process has enabled secure input and that this is preventing TextExpander from working.
I have traced this down to the Keybase client because as soon as I quite the client from the menu bar, TextExpander was happy and started working.
From my tests it appears that the initial state of the Keybase client (showing the icon and Login button) causes this secure input mode. After I login to Keybase the problem goes away.
I know we should all be logged in to Keybase all of the time, but could this be addressed in a future update so that TextExpander doesn't start complaining until I log in to Keybase?
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reproducing the issue on the macOS client with TextExpander before and after logging in, then trace the secure-input behavior in the pre-login state; done means TextExpander no longer reports secure input until Keybase login.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100