keybase / keybase/client

[mobile] Add password/finger print before opening the application

Open
#10,597 2 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

Currently anyone who can unlock my phone can also read my keybase messages.

Even worse when later KBFS will be implemented for mobile devices, one could even access my very private files.

And even though we can assume that phones are locked via password, pin, finger print or any other means, we also have to assume that there are backdoors built in by manufacturers, device administrators, legal authorities, or even compromised third party software (aka viruses, troyans, etc).

Therefore I'd suggest adding an optional password and or finger-print screen in front of the mobile keybase client.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the mobile application's launch flow and its existing password or biometric integration, then define how an optional gate should work on supported devices; done means the gate appears before the application can be opened and does not block users who leave it disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
react-native
Domain
authentication, mobile, security
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.