Keyoxide Project Update #2
A prosperous 2021 to all. Let's dive into some Keyoxide news.
The Keyoxide web client just got updated to 2.4.0 which introduced a few minor bug fixes as well as a robots.txt and noindex meta tags.
The most exciting new feature in this release is the support for "signature profiles", a new way of creating decentralized profiles that is both simpler to generate and solves a few drawbacks that come with the traditional method of storing identity claims as notations in cryptographic keys.
From the newly added signature profiles guide:
Storing claims inside the key as notations is a powerful method. Wherever the public key goes, so go the identity claims. This allows one to use the existing vast network of key sharing tools to also share these identity claims.
There are drawbacks to this: you lose granularity. You cannot pick and choose the claims you want to send to certain people or use for certain purposes. There is also the possibility that notations in keys could be scraped as the keys are publicly available.
Putting (certain) claims in a signature profile solves both drawbacks. You can choose which claims to be associated with each other and you can choose which persons can see this by only sending it to them. You can even encrypt the signature profile! Since the signature profile is not publicly available (unless you make it so), there is no possibility to scrape the contents of it.
Note that there is one catch: the person you send it to could publish it. Only send claims you wish to keep secret to people you trust!
What does a signature profile look like?
Here's an example:
-----BEGIN PGP SIGNED MESSAGE-----
Hey there! Here's a signature profile with proofs related to the DOIP project (https://doip.rocks).
Verify this profile at https://keyoxide.org/sig
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
I only wrote the four lines after
Hash: SHA512! The rest is generated by an OpenPGP-compatible library.
The first two lines are meant for humans. They state my intent with this signature profile as well as give an instruction to whomever receives it.
The remaining two lines are my identity claims. They follow a specific syntax that Keyoxide and any other service using doip.js can interpret.
The text around it is the signature. They make the message both provably beyond doubt written by yours truly, and untemparable. Try it in the next step, change any character in the text, it will fail. This ensures that no bad actor could intercept my signature on its way to you and modify its content.
What to do with it?
When put into keyoxide.org/sig, the website will perform two verifications.
First, is the signature valid? Has the text been tampered with? If the signature is valid, a so-called 'fingerprint' is extracted from it and displayed. Preferably, I have already mentioned my fingerprint to you. This ensures that you didn't simply get a signature from someone else pretending to be me.
The fingerprint of the key that I used for the signature above is
Second step is the verification of the identity claims. I could write a perfectly valid signature profile filled with absurd and incorrect identity claims! We don't want that.
The fingerprint we just extracted from the signature is now used to verify these identity claims. For example, the first claim (doip.rocks) will have a DNS record with that value. And the second claim (fosstodon.org/@keyoxide) has the fingerprint in the bio section of the account.
Both should verify. This allows you to say:
Whoever signed this profile, holds the doip.rocks domain name and the fosstodon.org/@keyoxide account.
Granular and non-scrapable identity claims
There you have it. Identity claims that can be sent granularly (you pick and choose which to include) and are non-scrapable (signature profiles are not publicly available).
And if you wish to go a step further, you can even encrypt the signature profile to make sure it can't be read while in transit to the intended recipient.
Release 0.9.0 of doip.js introduced support for the verification of signature profiles. In fact, Keyoxide simply relies on doip.js for all identity verifications. This makes it possible for new projects to get started quickly with fully decentralized identity verification and always have the same feature set that Keyoxide has.
This is the way.
Until next time.