[ANDROID] Keybase client won't work at all when key is not on server
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Noticed the keybase Android client wont allow login at all when you have selected to not store private key on server.
I Think the keybase client should instead ask the user to Point to a storage location on-device where the private key is located.
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 does not name files or tests. Start by locating the Android login flow and the handling of private keys that are not stored on the server; verify how an on-device key location could be selected. Done means users with server storage disabled can complete login using a private key stored on the device.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile-dev, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100