Seahorse / GNOME Keyring does not recognize my new ed25519 SSH key, is there another way to have the key...
I am unsure if I did the whole procedure right, so let's start with what I've done:
$ ssh-keygen -vvv -o -a 1000 -t ed25519 -f ~/.ssh/id_ed25519 -C "$(whoami)@$(hostname)--$(date -I)"
with some real strong password.
I successfully logged into my Debian machine using that key (-i /path/to/private/key
).
I thought that's a success, so I've rebooted both machines and now my GNOME Keyring is empty on both Mint and Debian with me being unable to manually import the private key, I tried it:
I have found that Seahorse (GNOME Keyring) currently does not handle Ed25519 on ArchWiki:
The following citation was edited to be more up-to-date and to have various links to the Wikipedia and to be more readable.
As of January 2018,
seahorse
(GNOME Keyring) doesn't handle ECDSA {Bugzilla (RESOLVED FIXED), Wiki}, nor Ed25519 {Bugzilla (NEW), Wiki} keys. You can turn to other SSH agents if you need support for those.
(Source - look at the bottom).
Do I need to wait for a bug fix / enhancement, or is there an alternative approach for me not to have to enter the complex password or enter it maybe once upon login? I don't honestly know, what my choices are at the moment.
EDIT #1
I don't want to switch back to the ECDSA or RSA keys.
EDIT #2
I have installed Linux Mint 19.1 (clean install, no upgrade), which is based on Ubuntu 18.04, but the issue in the same manner persists.
The ed25519
does not show up in the Seahorse 3.20.0:
Listing keys:
for key in ~/.ssh/id_*; do ssh-keygen -l -f "${key}"; done | uniq
Server:
256 SHA256:SMeBXPSluFwGBub/brKUy4/m8/DLim8Aw7zMmcdyEPs root@backup-server--2019-02-22 (ED25519)
8192 SHA256:JKKvLs+LXOdgv5nr00YFGjywqGANEFwCjXnzcjJ87og root@backup-server (RSA)
Client:
256 SHA256:WOj0Nl4svbiSxayTOCUC9LlI5nPQDyls9qV65u/0WwE vlastimil@dell-7577--2019-02-22 (ED25519)
8192 SHA256:GWPe50O7U0xq3DsRaQewz4WhOLrZ64Vf4x5bKnelrX4 vlastimil@dell-7577 (RSA)
ssh key-authentication gnome-keyring seahorse
add a comment |
I am unsure if I did the whole procedure right, so let's start with what I've done:
$ ssh-keygen -vvv -o -a 1000 -t ed25519 -f ~/.ssh/id_ed25519 -C "$(whoami)@$(hostname)--$(date -I)"
with some real strong password.
I successfully logged into my Debian machine using that key (-i /path/to/private/key
).
I thought that's a success, so I've rebooted both machines and now my GNOME Keyring is empty on both Mint and Debian with me being unable to manually import the private key, I tried it:
I have found that Seahorse (GNOME Keyring) currently does not handle Ed25519 on ArchWiki:
The following citation was edited to be more up-to-date and to have various links to the Wikipedia and to be more readable.
As of January 2018,
seahorse
(GNOME Keyring) doesn't handle ECDSA {Bugzilla (RESOLVED FIXED), Wiki}, nor Ed25519 {Bugzilla (NEW), Wiki} keys. You can turn to other SSH agents if you need support for those.
(Source - look at the bottom).
Do I need to wait for a bug fix / enhancement, or is there an alternative approach for me not to have to enter the complex password or enter it maybe once upon login? I don't honestly know, what my choices are at the moment.
EDIT #1
I don't want to switch back to the ECDSA or RSA keys.
EDIT #2
I have installed Linux Mint 19.1 (clean install, no upgrade), which is based on Ubuntu 18.04, but the issue in the same manner persists.
The ed25519
does not show up in the Seahorse 3.20.0:
Listing keys:
for key in ~/.ssh/id_*; do ssh-keygen -l -f "${key}"; done | uniq
Server:
256 SHA256:SMeBXPSluFwGBub/brKUy4/m8/DLim8Aw7zMmcdyEPs root@backup-server--2019-02-22 (ED25519)
8192 SHA256:JKKvLs+LXOdgv5nr00YFGjywqGANEFwCjXnzcjJ87og root@backup-server (RSA)
Client:
256 SHA256:WOj0Nl4svbiSxayTOCUC9LlI5nPQDyls9qV65u/0WwE vlastimil@dell-7577--2019-02-22 (ED25519)
8192 SHA256:GWPe50O7U0xq3DsRaQewz4WhOLrZ64Vf4x5bKnelrX4 vlastimil@dell-7577 (RSA)
ssh key-authentication gnome-keyring seahorse
add a comment |
I am unsure if I did the whole procedure right, so let's start with what I've done:
$ ssh-keygen -vvv -o -a 1000 -t ed25519 -f ~/.ssh/id_ed25519 -C "$(whoami)@$(hostname)--$(date -I)"
with some real strong password.
I successfully logged into my Debian machine using that key (-i /path/to/private/key
).
I thought that's a success, so I've rebooted both machines and now my GNOME Keyring is empty on both Mint and Debian with me being unable to manually import the private key, I tried it:
I have found that Seahorse (GNOME Keyring) currently does not handle Ed25519 on ArchWiki:
The following citation was edited to be more up-to-date and to have various links to the Wikipedia and to be more readable.
As of January 2018,
seahorse
(GNOME Keyring) doesn't handle ECDSA {Bugzilla (RESOLVED FIXED), Wiki}, nor Ed25519 {Bugzilla (NEW), Wiki} keys. You can turn to other SSH agents if you need support for those.
(Source - look at the bottom).
Do I need to wait for a bug fix / enhancement, or is there an alternative approach for me not to have to enter the complex password or enter it maybe once upon login? I don't honestly know, what my choices are at the moment.
EDIT #1
I don't want to switch back to the ECDSA or RSA keys.
EDIT #2
I have installed Linux Mint 19.1 (clean install, no upgrade), which is based on Ubuntu 18.04, but the issue in the same manner persists.
The ed25519
does not show up in the Seahorse 3.20.0:
Listing keys:
for key in ~/.ssh/id_*; do ssh-keygen -l -f "${key}"; done | uniq
Server:
256 SHA256:SMeBXPSluFwGBub/brKUy4/m8/DLim8Aw7zMmcdyEPs root@backup-server--2019-02-22 (ED25519)
8192 SHA256:JKKvLs+LXOdgv5nr00YFGjywqGANEFwCjXnzcjJ87og root@backup-server (RSA)
Client:
256 SHA256:WOj0Nl4svbiSxayTOCUC9LlI5nPQDyls9qV65u/0WwE vlastimil@dell-7577--2019-02-22 (ED25519)
8192 SHA256:GWPe50O7U0xq3DsRaQewz4WhOLrZ64Vf4x5bKnelrX4 vlastimil@dell-7577 (RSA)
ssh key-authentication gnome-keyring seahorse
I am unsure if I did the whole procedure right, so let's start with what I've done:
$ ssh-keygen -vvv -o -a 1000 -t ed25519 -f ~/.ssh/id_ed25519 -C "$(whoami)@$(hostname)--$(date -I)"
with some real strong password.
I successfully logged into my Debian machine using that key (-i /path/to/private/key
).
I thought that's a success, so I've rebooted both machines and now my GNOME Keyring is empty on both Mint and Debian with me being unable to manually import the private key, I tried it:
I have found that Seahorse (GNOME Keyring) currently does not handle Ed25519 on ArchWiki:
The following citation was edited to be more up-to-date and to have various links to the Wikipedia and to be more readable.
As of January 2018,
seahorse
(GNOME Keyring) doesn't handle ECDSA {Bugzilla (RESOLVED FIXED), Wiki}, nor Ed25519 {Bugzilla (NEW), Wiki} keys. You can turn to other SSH agents if you need support for those.
(Source - look at the bottom).
Do I need to wait for a bug fix / enhancement, or is there an alternative approach for me not to have to enter the complex password or enter it maybe once upon login? I don't honestly know, what my choices are at the moment.
EDIT #1
I don't want to switch back to the ECDSA or RSA keys.
EDIT #2
I have installed Linux Mint 19.1 (clean install, no upgrade), which is based on Ubuntu 18.04, but the issue in the same manner persists.
The ed25519
does not show up in the Seahorse 3.20.0:
Listing keys:
for key in ~/.ssh/id_*; do ssh-keygen -l -f "${key}"; done | uniq
Server:
256 SHA256:SMeBXPSluFwGBub/brKUy4/m8/DLim8Aw7zMmcdyEPs root@backup-server--2019-02-22 (ED25519)
8192 SHA256:JKKvLs+LXOdgv5nr00YFGjywqGANEFwCjXnzcjJ87og root@backup-server (RSA)
Client:
256 SHA256:WOj0Nl4svbiSxayTOCUC9LlI5nPQDyls9qV65u/0WwE vlastimil@dell-7577--2019-02-22 (ED25519)
8192 SHA256:GWPe50O7U0xq3DsRaQewz4WhOLrZ64Vf4x5bKnelrX4 vlastimil@dell-7577 (RSA)
ssh key-authentication gnome-keyring seahorse
ssh key-authentication gnome-keyring seahorse
edited 20 mins ago
Vlastimil
asked Feb 6 '18 at 13:07
VlastimilVlastimil
8,0891464139
8,0891464139
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The fix for this issue is included in Gnome Keyring 3.28 and seems unlikely to be backported to earlier versions.
If you want to go ahead with Ed25519, then you will need to wait for a release of your favorite distribution that includes this version.
I see that the next release of Linux Mint, Tara, will be based on Ubuntu 18.04, which includes this version, so perhaps you will not have too long to wait.
I am using vanilla Arch Linux with Gnome 3.30, and it's still not working here.
– Richard Neumann
Sep 24 '18 at 12:42
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%2f422276%2fseahorse-gnome-keyring-does-not-recognize-my-new-ed25519-ssh-key-is-there-ano%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
The fix for this issue is included in Gnome Keyring 3.28 and seems unlikely to be backported to earlier versions.
If you want to go ahead with Ed25519, then you will need to wait for a release of your favorite distribution that includes this version.
I see that the next release of Linux Mint, Tara, will be based on Ubuntu 18.04, which includes this version, so perhaps you will not have too long to wait.
I am using vanilla Arch Linux with Gnome 3.30, and it's still not working here.
– Richard Neumann
Sep 24 '18 at 12:42
add a comment |
The fix for this issue is included in Gnome Keyring 3.28 and seems unlikely to be backported to earlier versions.
If you want to go ahead with Ed25519, then you will need to wait for a release of your favorite distribution that includes this version.
I see that the next release of Linux Mint, Tara, will be based on Ubuntu 18.04, which includes this version, so perhaps you will not have too long to wait.
I am using vanilla Arch Linux with Gnome 3.30, and it's still not working here.
– Richard Neumann
Sep 24 '18 at 12:42
add a comment |
The fix for this issue is included in Gnome Keyring 3.28 and seems unlikely to be backported to earlier versions.
If you want to go ahead with Ed25519, then you will need to wait for a release of your favorite distribution that includes this version.
I see that the next release of Linux Mint, Tara, will be based on Ubuntu 18.04, which includes this version, so perhaps you will not have too long to wait.
The fix for this issue is included in Gnome Keyring 3.28 and seems unlikely to be backported to earlier versions.
If you want to go ahead with Ed25519, then you will need to wait for a release of your favorite distribution that includes this version.
I see that the next release of Linux Mint, Tara, will be based on Ubuntu 18.04, which includes this version, so perhaps you will not have too long to wait.
edited 35 mins ago
Vlastimil
8,0891464139
8,0891464139
answered May 22 '18 at 11:18
mavitmavit
1273
1273
I am using vanilla Arch Linux with Gnome 3.30, and it's still not working here.
– Richard Neumann
Sep 24 '18 at 12:42
add a comment |
I am using vanilla Arch Linux with Gnome 3.30, and it's still not working here.
– Richard Neumann
Sep 24 '18 at 12:42
I am using vanilla Arch Linux with Gnome 3.30, and it's still not working here.
– Richard Neumann
Sep 24 '18 at 12:42
I am using vanilla Arch Linux with Gnome 3.30, and it's still not working here.
– Richard Neumann
Sep 24 '18 at 12:42
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%2f422276%2fseahorse-gnome-keyring-does-not-recognize-my-new-ed25519-ssh-key-is-there-ano%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