How can import private key and certificate to seahorse in Ubuntu 18.04
I'm trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, but the seahorse gui application won't let me, the 'import' button is greyed out:
Screenshot
As seen in the screenshot, mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers".
How can I fix it to be able to import certificates and keys to seahorse?
Because that problem, I'm currently unable to digitally sign documents with LibreOffice.
This problem doesn't occur on Ubuntu 16.04 LTS, as I've just tested on my wife's laptop, it happens only in my Laptop with Ubuntu 18.04 LTS.
Thanks.
18.04 gnome-keyring seahorse
edited May 17 '18 at 18:57
user68186
16.1k84969
asked May 17 '18 at 18:37
AngeloAngelo
2113
|
show 1 more comment
I'm trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, but the seahorse gui application won't let me, the 'import' button is greyed out:
Screenshot
As seen in the screenshot, mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers".
How can I fix it to be able to import certificates and keys to seahorse?
Because that problem, I'm currently unable to digitally sign documents with LibreOffice.
This problem doesn't occur on Ubuntu 16.04 LTS, as I've just tested on my wife's laptop, it happens only in my Laptop with Ubuntu 18.04 LTS.
Thanks.
18.04 gnome-keyring seahorse
edited May 17 '18 at 18:57
user68186
16.1k84969
asked May 17 '18 at 18:37
AngeloAngelo
2113
2
Sounds like a bug report.
– user68186
May 17 '18 at 18:58
2
Yes, it looks like a bug, so I reported it at Launchpad: bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880 . Anyway, I still look for a possible workaround.
– Angelo
May 17 '18 at 19:42
You did the right things. Bug reports are off-topic here.
– user68186
May 17 '18 at 19:44
I tried the import function in seahorse in Ubuntu 18.04 today, after an update of seahorse that came today. I don't know if it was the update or not, but the import of the gpg file went through without any problem.
– user68186
May 18 '18 at 15:27
Actually the files that I had problem to import were digital signature certificate .cer, .crt and .p12, all of them failed to import, though I haven't tried to import .gpg keys.
– Angelo
May 18 '18 at 17:08
|
show 1 more comment
I'm trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, but the seahorse gui application won't let me, the 'import' button is greyed out:
Screenshot
As seen in the screenshot, mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers".
How can I fix it to be able to import certificates and keys to seahorse?
Because that problem, I'm currently unable to digitally sign documents with LibreOffice.
This problem doesn't occur on Ubuntu 16.04 LTS, as I've just tested on my wife's laptop, it happens only in my Laptop with Ubuntu 18.04 LTS.
Thanks.
18.04 gnome-keyring seahorse
edited May 17 '18 at 18:57
user68186
16.1k84969
asked May 17 '18 at 18:37
AngeloAngelo
2113
I'm trying to import a certificate into seahorse/gnome-keyring on Ubuntu 18.04, but the seahorse gui application won't let me, the 'import' button is greyed out:
Screenshot
As seen in the screenshot, mouse hovering the "import" button shows the message "Cannot import because there are no compatible importers".
How can I fix it to be able to import certificates and keys to seahorse?
Because that problem, I'm currently unable to digitally sign documents with LibreOffice.
This problem doesn't occur on Ubuntu 16.04 LTS, as I've just tested on my wife's laptop, it happens only in my Laptop with Ubuntu 18.04 LTS.
Thanks.
18.04 gnome-keyring seahorse
18.04 gnome-keyring seahorse
edited May 17 '18 at 18:57
user68186
16.1k84969
asked May 17 '18 at 18:37
AngeloAngelo
2113
edited May 17 '18 at 18:57
user68186
16.1k84969
asked May 17 '18 at 18:37
AngeloAngelo
2113
edited May 17 '18 at 18:57
user68186
16.1k84969
edited May 17 '18 at 18:57
user68186
16.1k84969
edited May 17 '18 at 18:57
user68186
16.1k84969
16.1k84969
asked May 17 '18 at 18:37
AngeloAngelo
2113
asked May 17 '18 at 18:37
AngeloAngelo
2113
asked May 17 '18 at 18:37
AngeloAngelo
2113
2113
2
Sounds like a bug report.
– user68186
May 17 '18 at 18:58
2
Yes, it looks like a bug, so I reported it at Launchpad: bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880 . Anyway, I still look for a possible workaround.
– Angelo
May 17 '18 at 19:42
You did the right things. Bug reports are off-topic here.
– user68186
May 17 '18 at 19:44
I tried the import function in seahorse in Ubuntu 18.04 today, after an update of seahorse that came today. I don't know if it was the update or not, but the import of the gpg file went through without any problem.
– user68186
May 18 '18 at 15:27
Actually the files that I had problem to import were digital signature certificate .cer, .crt and .p12, all of them failed to import, though I haven't tried to import .gpg keys.
– Angelo
May 18 '18 at 17:08
|
show 1 more comment
2
Sounds like a bug report.
– user68186
May 17 '18 at 18:58
2
Yes, it looks like a bug, so I reported it at Launchpad: bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880 . Anyway, I still look for a possible workaround.
– Angelo
May 17 '18 at 19:42
You did the right things. Bug reports are off-topic here.
– user68186
May 17 '18 at 19:44
I tried the import function in seahorse in Ubuntu 18.04 today, after an update of seahorse that came today. I don't know if it was the update or not, but the import of the gpg file went through without any problem.
– user68186
May 18 '18 at 15:27
Actually the files that I had problem to import were digital signature certificate .cer, .crt and .p12, all of them failed to import, though I haven't tried to import .gpg keys.
– Angelo
May 18 '18 at 17:08
2
2
Sounds like a bug report.
– user68186
May 17 '18 at 18:58
Sounds like a bug report.
– user68186
May 17 '18 at 18:58
2
2
Yes, it looks like a bug, so I reported it at Launchpad: bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880 . Anyway, I still look for a possible workaround.
– Angelo
May 17 '18 at 19:42
Yes, it looks like a bug, so I reported it at Launchpad: bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880 . Anyway, I still look for a possible workaround.
– Angelo
May 17 '18 at 19:42
You did the right things. Bug reports are off-topic here.
– user68186
May 17 '18 at 19:44
You did the right things. Bug reports are off-topic here.
– user68186
May 17 '18 at 19:44
I tried the import function in seahorse in Ubuntu 18.04 today, after an update of seahorse that came today. I don't know if it was the update or not, but the import of the gpg file went through without any problem.
– user68186
May 18 '18 at 15:27
I tried the import function in seahorse in Ubuntu 18.04 today, after an update of seahorse that came today. I don't know if it was the update or not, but the import of the gpg file went through without any problem.
– user68186
May 18 '18 at 15:27
Actually the files that I had problem to import were digital signature certificate .cer, .crt and .p12, all of them failed to import, though I haven't tried to import .gpg keys.
– Angelo
May 18 '18 at 17:08
Actually the files that I had problem to import were digital signature certificate .cer, .crt and .p12, all of them failed to import, though I haven't tried to import .gpg keys.
– Angelo
May 18 '18 at 17:08
|
show 1 more comment
1 Answer
1
active
oldest
votes
I had exactly the same problem importing my SSH private key to Seahorse in Ubuntu 18.04.
Apparently it also needs the pubkey in the same directory. If you don't have it, you can generate it using your private key:
ssh-keygen -y -f ~/.ssh/id_rsa > ~/.ssh/id_rsa.pub
It will import it automatically the first time you use your key.
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2faskubuntu.com%2fquestions%2f1037524%2fhow-can-import-private-key-and-certificate-to-seahorse-in-ubuntu-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had exactly the same problem importing my SSH private key to Seahorse in Ubuntu 18.04.
Apparently it also needs the pubkey in the same directory. If you don't have it, you can generate it using your private key:
ssh-keygen -y -f ~/.ssh/id_rsa > ~/.ssh/id_rsa.pub
It will import it automatically the first time you use your key.
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
add a comment |
I had exactly the same problem importing my SSH private key to Seahorse in Ubuntu 18.04.
Apparently it also needs the pubkey in the same directory. If you don't have it, you can generate it using your private key:
ssh-keygen -y -f ~/.ssh/id_rsa > ~/.ssh/id_rsa.pub
It will import it automatically the first time you use your key.
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
add a comment |
I had exactly the same problem importing my SSH private key to Seahorse in Ubuntu 18.04.
Apparently it also needs the pubkey in the same directory. If you don't have it, you can generate it using your private key:
ssh-keygen -y -f ~/.ssh/id_rsa > ~/.ssh/id_rsa.pub
It will import it automatically the first time you use your key.
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
I had exactly the same problem importing my SSH private key to Seahorse in Ubuntu 18.04.
Apparently it also needs the pubkey in the same directory. If you don't have it, you can generate it using your private key:
ssh-keygen -y -f ~/.ssh/id_rsa > ~/.ssh/id_rsa.pub
It will import it automatically the first time you use your key.
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
edited Feb 1 at 9:11
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
answered Jun 28 '18 at 9:14
xezpeletaxezpeleta
714
714
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1037524%2fhow-can-import-private-key-and-certificate-to-seahorse-in-ubuntu-18-04%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
2
Sounds like a bug report.
– user68186
May 17 '18 at 18:58
2
Yes, it looks like a bug, so I reported it at Launchpad: bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1771880 . Anyway, I still look for a possible workaround.
– Angelo
May 17 '18 at 19:42
You did the right things. Bug reports are off-topic here.
– user68186
May 17 '18 at 19:44
I tried the import function in seahorse in Ubuntu 18.04 today, after an update of seahorse that came today. I don't know if it was the update or not, but the import of the gpg file went through without any problem.
– user68186
May 18 '18 at 15:27
Actually the files that I had problem to import were digital signature certificate .cer, .crt and .p12, all of them failed to import, though I haven't tried to import .gpg keys.
– Angelo
May 18 '18 at 17:08