Timeline for How to export a GPG private key and public key to a file
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2024 at 15:31 | comment | added | cliff.meyers | Note that name can be either the 40-char keypair fingerprint or the long format keyid which is the last 16 chars of the fingerprint. | |
| S Feb 10, 2023 at 13:55 | history | suggested | A T | CC BY-SA 4.0 | Use `-o` to prevent console issues finding there way into the output file |
| Feb 9, 2023 at 3:51 | review | Suggested edits | |||
| S Feb 10, 2023 at 13:55 | |||||
| Dec 14, 2021 at 4:22 | comment | added | Y00 | simply use -a option will export it in ASCII format, gpg -a --export-secret-keys name | |
| Dec 4, 2020 at 14:45 | comment | added | Jeter-work | It would be a good idea to remove the key file after it is imported and tests successfully. If the file is sitting there it could be used maliciously. | |
| Dec 4, 2020 at 14:44 | comment | added | Jeter-work | Actually, .asc is for ASCII armored and the output is enciphered text. You can safely cat it and see for yourself. Also, like most linux files, the file extension is also arbitrary, doesn't technically have to be asc. @WeihangJian | |
| Jun 2, 2020 at 15:49 | comment | added | Weihang Jian | Note that .asc stands for ASCII, but the output of gpg --list-secret-keys is binary. | |
| Nov 19, 2019 at 13:25 | review | Late answers | |||
| Nov 19, 2019 at 14:08 | |||||
| Nov 19, 2019 at 13:10 | review | First posts | |||
| Nov 19, 2019 at 13:35 | |||||
| Nov 19, 2019 at 13:08 | history | answered | Serj Sp | CC BY-SA 4.0 |