mic92 / ssh-to-pgp

Convert SSH RSA keys to GPG keys

ssh-to-pgp

Convert SSH RSA keys to GPG keys

Usage

• Exports the private:

$ ssh-to-pgp -private-key -i $HOME/.ssh/id_rsa -o private-key.asc
2504791468b153b8a3963cc97ba53d1919c5dfd4

• Exports the public key:

$ ssh-to-pgp -i $HOME/.ssh/id_rsa -o public-key.asc
2504791468b153b8a3963cc97ba53d1919c5dfd4

Install with nix

$ nix-shell -p 'import (fetchTarball "https://github.com/Mic92/ssh-to-pgp/archive/main.tar.gz") {}'

Install with go

$ go get github.com/Mic92/ssh-to-pgp

ssh-to-pgp's Issues

Output is Broken Again

It seems the Problem has reappeared in Version 1.1.3

          hopefully we no longer have this issue because we switched away from this fork of the crypto library: https://github.com/Mic92/ssh-to-pgp/blob/main/go.mod

Originally posted by @Mic92 in #12 (comment)

Invalid key generated

I think I found a bug, introduced in ff31dcb.

Output before that commit:

./ssh-to-pgp -i test-assets/id_rsa
-----BEGIN PGP PUBLIC KEY BLOCK-----

xsDNBAAAAAABDADSeS6SEputIOi2mQhLeIEJnMAink+KcUv38HnaLak3nnLmUsYJ
nXYB5KZGxaxVtIjr59J8TndmwniZ+wc0rql6Dkif9CsTXgAjxrPiknZNQ7JQbgWU
r0pk4jx/K3zLD6i/XAS8QWySNJmY5aJWySbF/K687kUMJ5ql0BX4Tt0RiWL4pIwz
ZZlLzH4rRySy4z1kbiuOZf8htVRtlGoDGqGViJRpuybSKrmXbevRI7aWjiml2BVT
MktPekAPx+MA3t/8EM/uJxtWp7g3BsneHQdKIjR0WEKAITTmuDLEEtIXXEUbgBW0
WjbD62nRft/A6/iyWykPJmkLA4WnSLS03caeUxCKoEthZ1xfBPCRNw7xbysQF8CH
Jz8cAMjZGgBGlOin8EKDhmlma6FZ94cAB5Tr4G3R0h4ky77bPk2/6vvZtyU/AFnD
P2HfGaRCDNF+Q7+fR9YmKwcW/vCa2ItIEXgMmBjS+yl0p+4fVaY6Q7bCTbrd6znb
6gTGo7nD9Kj/CGUAEQEAAc0pcm9vdCAoSW1wb3J0ZWQgZnJvbSBTU0gpIDxyb290
QGxvY2FsaG9zdD7CwOIEEwEIABYFAgAAAAAJENlvbolIGMelAhsPAhkBAADdzgwA
BZ7vG2IjikqP/a9t1Ian4M58/zWIhM2z94xPvazP29J0OQ1x500G3fBgUhu6oOoZ
6qPxoyO/GKAbmDUocahbckyBmbbYFBYN+HjzwVnhpRPS0xOvW4b/tEmZIgqDaHPH
Y+bHS9r9znAhDQnP2YyAnB7VMcqPtp+X+28MR9cgTN6JdTBeJOHptRQRPAvv6I4m
2Hc9HnwyFN8jM1bcEDKasO+5YVX+0nniSJpk92h4JgyPe9xB7zdyXHAh5yLlXRVN
lGg+P51qIpFcNvhMiH2M8iRPj4NPSygpKq/S0Dxq2txU1GIZQWs6nSSX07UWoU9l
vkjUuv6IXAbRjQ5wz45w8AzQ92vQ3RdKOMTi0mIUb/0DNChMl/F39glNOjVCJ2p9
XryXibU0ClSg7fo7Irb5nn9VyGAH4qfMsu4jLpIvNaB6Ygt9dbq7LvPIe0PxPJ1B
pwy8JHtfl3C/J9AjwXf4haNt5FZJsQwd5KKacNsgczSmirdaebwgE9BQ5RUeW7I8
=xwBn
-----END PGP PUBLIC KEY BLOCK-----82ddc034d5ded2524f701114d96f6e894818c7a5

Output after:

./ssh-to-pgp -i test-assets/id_rsa
-----BEGIN PGP PUBLIC KEY BLOCK-----

xsDNBAAAAAABDADSeS6SEputIOi2mQhLeIEJnMAink+KcUv38HnaLak3nnLmUsYJ
nXYB5KZGxaxVtIjr59J8TndmwniZ+wc0rql6Dkif9CsTXgAjxrPiknZNQ7JQbgWU
r0pk4jx/K3zLD6i/XAS8QWySNJmY5aJWySbF/K687kUMJ5ql0BX4Tt0RiWL4pIwz
ZZlLzH4rRySy4z1kbiuOZf8htVRtlGoDGqGViJRpuybSKrmXbevRI7aWjiml2BVT
MktPekAPx+MA3t/8EM/uJxtWp7g3BsneHQdKIjR0WEKAITTmuDLEEtIXXEUbgBW0
WjbD62nRft/A6/iyWykPJmkLA4WnSLS03caeUxCKoEthZ1xfBPCRNw7xbysQF8CH
Jz8cAMjZGgBGlOin8EKDhmlma6FZ94cAB5Tr4G3R0h4ky77bPk2/6vvZtyU/AFnD
P2HfGaRCDNF+Q7+fR9YmKwcW/vCa2ItIEXgMmBjS+yl0p+4fVaY6Q7bCTbrd6znb
6gTGo7nD9Kj/CGUAEQEAAc0pcm9vdCAoSW1wb3J0ZWQgZnJvbSBTU0gpIDxyb290
QGxvY2FsaG9zdD4=
=uf61
-----END PGP PUBLIC KEY BLOCK-----82ddc034d5ded2524f701114d96f6e894818c7a5

Importing the latter key with gpg fails:

82ddc034d5ded2524f701114d96f6e894818c7a5
gpg: key 0xD96F6E894818C7A5: 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

Support configuring the user id

Hi, this is a feature request to support configuration of the fields hardcoded here:

ssh-to-pgp/convert.go

Line 44 in 1ce63fe

uid := packet.NewUserId("root", "Imported from SSH", "root@localhost")

The main idea is that, when managing multiple keys from different hosts, it's difficult to tell which key belongs to which host at a glance. For my use case it would be sufficient if localhost would default to the hostname of the current machine, but perhaps allowing some/all fields to be specified via command line arguments would be more extensible.

Any way to stop creating AEAD pgp certs from ssh at all please?

Hi

I wasn't sure if its here or in my gpg settings, but the pgp key created with ssh-to-pgp on newer versions of gpg include a seemingly non standard AEAD support.

Pass for android app uses PGPainless backend, which does not and will not support AEAD, as far as I understand it.

I wondered if it is possible to specify to create compatible pgp keys excluding AEAD?

Thanks in advance.