Web key directory

Open
#121 35 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
backend, documentation, security

Research direction

Start by reviewing the keyserver's existing public-key serving entry points and configuration documentation, then compare the expected behavior with the GPG Web Key Directory specification. Document the required DNS records and client or GPG-version support, and verify that keys can be auto-detected through the documented setup.

Written by the indexing model from the issue text.

Description

Can this expose the public keys according to GPG Web Key Directory?

It would also be helpful to guide on what DNS records need to be set and other such setups in order to get the keyserver to be auto-detected, and which clients/gpg versions support which setup.

Dominant language
JavaScript
Stars
481
Forks
80
No merged PRs in 30d

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.

More from mailvelope/keyserver

All issues in mailvelope/keyserver

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.