keybase / keybase/keybase-issues

Tracking command line clients or use in general.

Open
#694 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

Are there any plans to track which machines/ip addresses have a CLI client logged in? Or, perhaps more usefully, tracking of events performed with the help of keybase which could cover the web interface too? Something as brief as a timestamped list of events such as logins, use of keys and so forth. It'd be useful to check for evidence malicious activity, which is probably important for anyone who decides to host their private key on keybase.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. Clarify the desired audit scope, privacy, and retention requirements with maintainers, then locate the CLI and web authentication or event paths and define what timestamped login, key-use, and related activity records should cover.

Written by the indexing model from the issue text.

Assessment

Domain
cli, security, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.