Is it possible to reuse a GnuPG key in another installation?
I have a GPG key which I use to sign and submit packages to Launchpad.
Is it possible to reuse that key in another installation, or do I always have to create a new key for the new installation of a GNU/Linux operating system?
gpg-agent pgp openpgp
add a comment |
I have a GPG key which I use to sign and submit packages to Launchpad.
Is it possible to reuse that key in another installation, or do I always have to create a new key for the new installation of a GNU/Linux operating system?
gpg-agent pgp openpgp
add a comment |
I have a GPG key which I use to sign and submit packages to Launchpad.
Is it possible to reuse that key in another installation, or do I always have to create a new key for the new installation of a GNU/Linux operating system?
gpg-agent pgp openpgp
I have a GPG key which I use to sign and submit packages to Launchpad.
Is it possible to reuse that key in another installation, or do I always have to create a new key for the new installation of a GNU/Linux operating system?
gpg-agent pgp openpgp
gpg-agent pgp openpgp
asked Feb 8 at 9:05
Archisman PanigrahiArchisman Panigrahi
1187
1187
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Rather than copying the ~/.gnupg
folder, you can create an export of your secret keys and then import on the new install, e.g.
$ gpg --export-secret-keys --output mykeys
Then on the new system:
$ gpg --import mykeys
(note: you will need to know the password associated with the keys to import them)
By exporting and importing, you allow gpg
to handle any version/format differences between differing versions of gpg
on the different installs.
You can use the --export
option for your stored public keys in the same manner. (though I have found not including the public keys as a good way to purge all the old, non-used keys that have been collected over the years if you don't explicitly need them)
add a comment |
Copy ~/.gnupg to the new system
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499431%2fis-it-possible-to-reuse-a-gnupg-key-in-another-installation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Rather than copying the ~/.gnupg
folder, you can create an export of your secret keys and then import on the new install, e.g.
$ gpg --export-secret-keys --output mykeys
Then on the new system:
$ gpg --import mykeys
(note: you will need to know the password associated with the keys to import them)
By exporting and importing, you allow gpg
to handle any version/format differences between differing versions of gpg
on the different installs.
You can use the --export
option for your stored public keys in the same manner. (though I have found not including the public keys as a good way to purge all the old, non-used keys that have been collected over the years if you don't explicitly need them)
add a comment |
Rather than copying the ~/.gnupg
folder, you can create an export of your secret keys and then import on the new install, e.g.
$ gpg --export-secret-keys --output mykeys
Then on the new system:
$ gpg --import mykeys
(note: you will need to know the password associated with the keys to import them)
By exporting and importing, you allow gpg
to handle any version/format differences between differing versions of gpg
on the different installs.
You can use the --export
option for your stored public keys in the same manner. (though I have found not including the public keys as a good way to purge all the old, non-used keys that have been collected over the years if you don't explicitly need them)
add a comment |
Rather than copying the ~/.gnupg
folder, you can create an export of your secret keys and then import on the new install, e.g.
$ gpg --export-secret-keys --output mykeys
Then on the new system:
$ gpg --import mykeys
(note: you will need to know the password associated with the keys to import them)
By exporting and importing, you allow gpg
to handle any version/format differences between differing versions of gpg
on the different installs.
You can use the --export
option for your stored public keys in the same manner. (though I have found not including the public keys as a good way to purge all the old, non-used keys that have been collected over the years if you don't explicitly need them)
Rather than copying the ~/.gnupg
folder, you can create an export of your secret keys and then import on the new install, e.g.
$ gpg --export-secret-keys --output mykeys
Then on the new system:
$ gpg --import mykeys
(note: you will need to know the password associated with the keys to import them)
By exporting and importing, you allow gpg
to handle any version/format differences between differing versions of gpg
on the different installs.
You can use the --export
option for your stored public keys in the same manner. (though I have found not including the public keys as a good way to purge all the old, non-used keys that have been collected over the years if you don't explicitly need them)
answered Feb 8 at 9:13
David C. RankinDavid C. Rankin
1414
1414
add a comment |
add a comment |
Copy ~/.gnupg to the new system
add a comment |
Copy ~/.gnupg to the new system
add a comment |
Copy ~/.gnupg to the new system
Copy ~/.gnupg to the new system
answered Feb 8 at 9:07
Ole TangeOle Tange
12.6k1455105
12.6k1455105
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499431%2fis-it-possible-to-reuse-a-gnupg-key-in-another-installation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown