keys.mailvelope.com is hard coded in homepage and manage keys page for hkp usage

Open
#144 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
frontend

Research direction

Search the homepage and manage keys page for the hard-coded keys.mailvelope.com reference, starting with the page entry points that render the HKP and REST API text. Update the displayed server reference to follow the configured keyserver, then verify both pages show the expected value for keys.puri.sm.

Written by the indexing model from the issue text.

Description

I have setup keys.puri.sm, but it still shows keys.mailvelope.com but https://keys.puri.sm/manage.html shows,

HKP and REST Apis

The server offers a modern REST api over HTTPS with HSTS and public key pinning that can be integrated into any app architecture. It is also compatible to the OpenPGP HTTP Keyserver Protocol (HKP). Just copy and paste hkps://keys.mailvelope.com into your current OpenPGP plugin and go. Learn more.

Dominant language
JavaScript
Stars
481
Forks
80
PR merge metrics
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.