keybase / keybase/keybase-issues
Browser extension security
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
There was some technical issues regarding the browser extension : https://palant.de/2018/09/06/keybase-our-browser-extension-subverts-our-encryption-but-why-should-we-care/ or https://nakedsecurity.sophos.com/2018/09/11/keybase-browser-extension-weakness-discovered/
Is there any big changes in Keybase extension since these articles ? Is there any public response of keybase to those threads ?
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
Start by reviewing the two linked articles and checking the public Keybase issue and repository history for changes to the browser extension. No files or tests are named; done means documenting whether the reported weaknesses were addressed and whether Keybase publicly responded.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100