/openpgp4info

Web-based openpgp4fpr: handlers

Primary LanguageHTML

OpenPGP 4 Fingerprint Handler

This repository contains the configuration needed to set up a simple proxy that allows browsers to handle the openpgp4fpr: URI scheme. When the URI handler was registered, the proxy would return a 301 redirect to a search for the OpenPGP fingerprint on either an HTTP or HTTPS keyserver.

In October 2014, I set up https://openpgp4.info to teach myself about handling URIs and in the process became interested in browser support for this specific scheme. This led to requesting openpgp4fpr: be added to the WHATWG whitelist and then supported by Chrome/Chromium, and the site was useful in providing a proof-of-concept demonstrating the function the URI provides.

After a year, the concept has been proven, and support has been added. I intentionally didn't keep logs, which, while providing privacy to any users I might have acquired, means I actually have no idea whether this sees any use. I assume it was minimal, but I want to preserve the configuration needed to construct it.

The proxy service was disabled on 5 October 2015. The site was shut down on 13 October 2015.

About openpgp4fpr

In 2010, the Monkeysphere project introduced the openpgp4fpr:<FINGERPRINT> scheme for sharing OpenPGP key fingerprints, where <FINGERPRINT> is the full 40 hex character fingerprint of a primary key, and has since been adopted in vCards for sharing public keys.

Perhaps more significantly, several Android applications (APG/OpenKeychain, and the Guardian Project's GnuPG port) now accept this scheme as a means of quickly exchanging public keys via QR codes. The Android "intents" interface paves the way for openpgp4fpr URIs to become increasingly common. The purpose of the site was to provide a proof-of-concept that demonstrates their applicability outside the realm of Android applications.

In early 2015, the WHATWG accepted openpgp4fpr: as a whitelisted scheme.

Browser Support

Firefox/Iceweasel allow for the registration of web-based protocol handlers without restriction.

Google Chrome/Chromium follow WHATWG recommendations. Chromium has included openpgp4fpr: in its whitelist, which entered production as of Chromium 44.

External Links

Donate

On the off chance there were any users who want to see this service return, you may donate bitcoins to 1EiWCrKkjspVcLFgAkevd3yEh6xfqfymAx. If money appears at this address, it it will be spent to re-register the domain and pay for hosting.