pgp2ssh/README.md

63 lines
2.2 KiB
Markdown
Raw Normal View History

2024-03-27 18:38:02 +01:00
# pgp2ssh
2024-03-26 14:48:45 +01:00
2024-03-27 17:45:12 +01:00
Derive private ed25519 SSH key from private PGP key.
GPG itself only supports exporting _public_ SSH keys and other tools don't work for ed25519 keys.
2024-03-26 14:48:45 +01:00
##### Notes:
- A tool exists to do this for RSA keys: [openpgp2ssh](https://manpages.ubuntu.com/manpages/xenial/man1/openpgp2ssh.1.html) but it does not seem to support `ed25519` keys
- Work on `gnupg` was started for this feature, but never finished see this
issue and commit: https://dev.gnupg.org/T6647
2024-03-27 17:45:12 +01:00
## Instructions
2024-03-25 17:22:47 +01:00
2024-03-27 17:45:12 +01:00
First you need to export your PGP key from GPG:
2024-03-25 17:25:08 +01:00
```sh
2024-03-27 17:45:12 +01:00
gpg2 --export-secret-keys --armor test@test.test >priv-gpg
2024-03-25 17:22:47 +01:00
```
2024-03-27 17:45:12 +01:00
Then identify the public SSH key that was used to encrypt your secret.
You can search for your GitHub username in: https://fluence-dao.s3.eu-west-1.amazonaws.com/metadata.json
2024-03-25 17:22:47 +01:00
2024-03-27 17:45:12 +01:00
If you have multiple subkeys, usually it is the authenticate key highlighted with `[A]` in the output of:
2024-03-25 17:22:47 +01:00
```sh
2024-03-27 17:45:12 +01:00
gpg --list-secret-keys --with-keygrip
2024-03-25 17:22:47 +01:00
```
2024-03-27 17:45:12 +01:00
### Derive private SSH key
2024-03-25 17:22:47 +01:00
```sh
2024-03-27 21:32:12 +01:00
go build
./pgp2ssh
2024-03-25 17:22:47 +01:00
```
2024-03-28 11:04:10 +01:00
**Nix/NixOS Users**
A flake is provided for Nix users. Just use `nix run` instead of building and
running manually.
2024-03-27 17:45:12 +01:00
It'll ask you for the path to your private PGP key, followed by choosing the key/subkey and if your PGP key is encrypted it'll ask for the passphrase.
2024-03-25 17:22:47 +01:00
2024-03-27 17:45:12 +01:00
In the output, verify that the public SSH key printed matches the one in `metadata.json`.
If it matches, the last part of the output it will print the matching private SSH key.
You can save the key to a file and use how you want.
2024-03-26 14:48:45 +01:00
2024-03-27 17:45:12 +01:00
### Example: Decrypt age files
2024-03-25 17:22:47 +01:00
2024-03-27 17:45:12 +01:00
If you want to decrypt a file that was encryptd by `age` with your public SSH key, you can just use `age` as normal to decrypt the file using the SSH private key that we've got in the previous step:
```sh
age --decrypt --identity ./ssh-secret-key --output decrypted ./testfile.txt.age
```
### Support & Donations
This project was built with lots of headaches by [pinpox](https://github.com/pinpox/) & [felschr](https://github.com/felschr/). If you need help, feel free to contact us.
And if you want to thank us, you can send us any crypto or token to our Ethereum / Polygon wallets 😊:
pinpox: `0x3d479e19ae8d1a67becdaeaf8d2d37c8e425bd03`
2024-03-27 18:38:02 +01:00
felschr: `0xD66753D737603E18018281E298Df86DE402d313E`