mafintosh / mafintosh/webcat

support other key hosts beyond github

Open
#5 6 comments 0 reactions 0 assignees View on GitHub
help wanted
Dominant language
JavaScript
Stars
449
Forks
26
PR merge metrics
No merged PRs in 30d

Description

right now we use github because: https://github.com/maxogden.keys

but we should be able to use any scheme where you can type a username and it can figure out how to get a public key. it should probably prompt the user and double check that they wanna trust the public key from the domain it resolves, similar to what keybase does.

keybase might be a good next one to support actually, as they have a CORS enabled endpoint to get the pgp key for any user

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the existing GitHub public-key lookup described in the issue and how webcat authenticates users with those keys. Define the supported username-and-scheme flow and the trust confirmation; done means another host can provide a user's key only after the user approves the resolved domain, with Keybase considered as the next provider.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, javascript
Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.