Account security in semi-trusted client
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
I have a Keybase install on a MacOS system which I consider to be reasonably secure. I thought I'd also install Keybase on Windows, but my Windows system is not quite as secure.
I assume that my Windows Keybase doesn't have access to the keys on my MacOS Keybase. However, if my Windows system were stolen, for example, would an attacker be able to use the installed Keybase client to delete my account or change my password?
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, tests, or entry points are mentioned. First establish the client's account-deletion and password-change behavior from a semi-trusted Windows device; done requires documenting the verified security behavior and its limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- authentication, authorization, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100