I did some experimentation with the new GnuPG 2 changes (not yet deployed to production). Only some key types work as yet. I found that an ed25519 key isn't supported by the version of gpgme1.0 that we have in xenial, while xenial's gpg2 failed to import a secp256k1 key with this somewhat mysterious message:
gpg: key A719B12D: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg: w/o user IDs: 1
However, a nistp256 key works OK, although we do need to add it to `GPGKeyAlgorithm` before it will actually be possible to add one of those in Launchpad.
I did some experimentation with the new GnuPG 2 changes (not yet deployed to production). Only some key types work as yet. I found that an ed25519 key isn't supported by the version of gpgme1.0 that we have in xenial, while xenial's gpg2 failed to import a secp256k1 key with this somewhat mysterious message:
gpg: key A719B12D: no valid user IDs
gpg: this may be caused by a missing self-signature
gpg: Total number processed: 1
gpg: w/o user IDs: 1
However, a nistp256 key works OK, although we do need to add it to `GPGKeyAlgorithm` before it will actually be possible to add one of those in Launchpad.