On 29 June 2018 at 15:13, Alistair Francis <[email protected]> wrote: > Can you import it manually? The armour export is below:
Aha. I tried that, which didn't work either, which prompted me to try --verbose, which says: e104462:xenial:qemu-for-merges$ gpg --verbose --import /tmp/alistair.gpg gpg: armour header: Version: GnuPG v2 gpg: can't handle public key algorithm 19 gpg: pub 0E/0xE48E3BC2C123ED93 2017-12-15 Alistair Francis <[email protected]> gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user ID "Alistair Francis <[email protected]>" gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm on user ID "Alistair Francis <[email protected]>" gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm gpg: key 0xE48E3BC2C123ED93: unsupported public key algorithm gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis <[email protected]>" gpg: key 0xE48E3BC2C123ED93: skipped user ID "Alistair Francis <[email protected]>" gpg: key 0xE48E3BC2C123ED93: skipped subkey gpg: key 0xE48E3BC2C123ED93: skipped subkey gpg: key 0xE48E3BC2C123ED93: skipped subkey gpg: key 0xE48E3BC2C123ED93: 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 So the problem is that your key is using some algorithm that's too newfangled for my gpg to cope with... thanks -- PMM
