-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
feat: Add keystroke telemetry & overlay support #980
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
Open
dasabhishk-buildstuff
wants to merge
2
commits into
webadderallorg:main
Choose a base branch
from
dasabhishk-buildstuff:feature/keystroke-overlay
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🛡️ Analyzed with Security Review | 🟠 Major | 🏗️ Heavy lift
Sensitive Data Exposure
Reachability: External
Exploitability: Moderate
CWE: CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor
Enforce protected-input suppression on every keyboard capture backend.
The Windows and Linux path has no protected-input check. The macOS path permits capture when the check cannot determine the focused element or subrole.
electron/ipc/cursor/interaction.ts#L369-L377: verify that the focused input is not protected before callingrecordKeystroke.electron/native/NativeCursorMonitor.swift#L410-L414: return a protected or unknown state when Accessibility inspection fails, and suppress the event.Without these controls, password keystrokes can enter the persisted telemetry sidecar.
📍 Affects 2 files
electron/ipc/cursor/interaction.ts#L369-L377(this comment)electron/native/NativeCursorMonitor.swift#L410-L414🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I missed adding the same to windows and linux paths and chromium password fields, however the sidecar is an internal local project artifact and is not part of the user-shared export. I think the existence of raw keystrokes in the sidecar should not itself be considered an exposure of credentials. However, since issue #969 explicitly requires no capture in password fields, protected-field suppression I will try to extend the implementation to meet this requirement. The 'Shortcuts' mode independently guarantees that ordinary typed characters are not rendered into the exported output.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dasabhishk-buildstuff, agreed that a local-only sidecar has a different exposure scope than exported media.The remaining concern is the capture requirement from issue
#969.Shortcutsmode filters rendered output, butonKeyDownstill captures and persists ordinary input before that filter applies.The finding should remain open until each capture backend suppresses input from protected fields, including cases where protected-field detection is unavailable.
✏️ Learnings added
You are interacting with an AI system.