keybase / keybase/keybase-issues

Availability of certificates in the browser

Open
#2,100 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
899
Forks
40
PR merge metrics
No merged PRs in 30d

Description

There is a huge lack of support for client-side certificates in browsers. It seems [this will not change](https://lists.w3.org/Archives/Public/public-webappsec/2016Feb/0076.html). Some European countries on the other hand are strong in e-government, you can fill taxes online, you get state issues digital certificates which you can use to sign documents and signatures are equivalent to normal signatures. But the issue is that it is hard to really build around those digital certificates. You cannot make web applications which would use them.

So it would be great if keybase keychain would be available in the browser. So that apps could request it to sign documents.

I wanted to make a simple web applications where people could sign petitions using state-issues certificates, but it is not possible. Even if users have key pair imported into the browser.

Maybe keybase could address this ecosystem issue.

Contributor guide

No contributing guide indexed for this repository

Research direction

No files, tests, or entry points are identified. Start by reviewing the browser client-side certificate limitation and the proposed Keybase keychain integration described in the issue. Define a concrete integration path and acceptance criteria before implementation.

Written by the indexing model from the issue text.

Assessment

Domain
authentication, security, web-dev
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.