keybase / keybase/keybase-issues
Binary Transparency for client updates
Open
- Dominant language
- No language data
- Stars
- 899
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
Are there plans to introduce [Binary Transparency](https://wiki.mozilla.org/Security/Binary_Transparency) - whether or not based on CT logs - to keybase updates?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the linked Mozilla Binary Transparency proposal and reviewing how Keybase client updates are handled. Determine whether transparency should use CT logs or another approach, then document a concrete implementation plan for binary transparency in client updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100