Stricter Login Impermanence [Private Key in RAM, etc]
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Presently, the iOS and Mac apps stay logged in indefinitely. I appreciate that I can keybase logout...
It'd be great to see a timeout feature for logins so that loss of physical hardware didn't pose as much of a threat.
On iOS this could be simply passcode or touch ID based.
On MAC this could be "timeout after x minutes of inactivity of kbfs, etc"
This is related to concerns surrounding having the private key available in RAM or on disk for these devices as well, which is the case so long as Keybase is logged in.
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
The issue names no files or tests; the entry points mentioned are keybase logout, KBFS activity, and iOS passcode or Touch ID. Start by locating login and session handling for the Go client and iOS/macOS apps, then define platform-specific timeout behavior and tests that verify logout or reauthentication after inactivity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, ios, macos
- Domain
- authentication, desktop, mobile, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100