Yet another `sign_and_send_pubkey: signing failed: agent refused operation`
Here’s a Yet Another Question about the clash between ssh and gnome-keyring-daemon, since after spending hours and hours on the Internet I finally gave up.
Environment
- OS: openSUSE 15.0
- DE: XFCE
- gnome-keyring-daemon version: 3.20.1
- seahorse version: 3.20.0
- git version: 2.16.4
- ssh version: OpenSSH_7.6p1, OpenSSL 1.1.0i-fips 14 Aug 2018
Situation
Trying to git pull a repo leads to a message
sign_and_send_pubkey: signing failed: agent refused operation
, even though for years I was getting a neat GUI prompt which remembered the typed password throughout the current session. (AFAIU, this prompt was shown by Seahorse?).
After doing a killall gnome-keyring-daemon, successive attempts to do a git pull lead to a terminal prompt
Enter passphrase for key '/home/user/.ssh/id_rsa':
which does not store the password anywhere (AFAIU, this means that ssh-agent is not working?).
The same effect can be achieved by adding SSH_AUTH_SOCK=0 in front of git pull.
What I want
- Doing a
git pullcaches my SSH password over the course of my current login session (like it was before). Neat GUI prompt is optional. - Ed25519 keys are supported. (Apparently GNOME Keyring has (had?) some problems with them).
What I tried
- Disabling “SSH Key Agent” in
XFCE settings → Startup Applications
- Copying
/etc/xdg/autostart/gnome-keyring-ssh.desktopto~/.config/autostartand then appending the lineHidden=trueto the copied file
Neither of the above prevented gnome-keyring-daemon from starting up on boot, since I still can see it in ps.
- Creating
~/.pam_environmentthen addingGSM_SKIP_SSH_AGENT_WORKAROUND DEFAULT=1there - Reverting back to RSA
- Playing with
ssh-add
- Installing
git-credential-libsecretthen doinggit config --global credential.helper /usr/lib/git/git-credential-libsecret
- Toying with the thought of obliterating the
gnome-keyringpackage altogether, which was abandoned because apparently several important packages depend on it
ssh git gnome-keyring seahorse
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
add a comment |
Here’s a Yet Another Question about the clash between ssh and gnome-keyring-daemon, since after spending hours and hours on the Internet I finally gave up.
Environment
- OS: openSUSE 15.0
- DE: XFCE
- gnome-keyring-daemon version: 3.20.1
- seahorse version: 3.20.0
- git version: 2.16.4
- ssh version: OpenSSH_7.6p1, OpenSSL 1.1.0i-fips 14 Aug 2018
Situation
Trying to git pull a repo leads to a message
sign_and_send_pubkey: signing failed: agent refused operation
, even though for years I was getting a neat GUI prompt which remembered the typed password throughout the current session. (AFAIU, this prompt was shown by Seahorse?).
After doing a killall gnome-keyring-daemon, successive attempts to do a git pull lead to a terminal prompt
Enter passphrase for key '/home/user/.ssh/id_rsa':
which does not store the password anywhere (AFAIU, this means that ssh-agent is not working?).
The same effect can be achieved by adding SSH_AUTH_SOCK=0 in front of git pull.
What I want
- Doing a
git pullcaches my SSH password over the course of my current login session (like it was before). Neat GUI prompt is optional. - Ed25519 keys are supported. (Apparently GNOME Keyring has (had?) some problems with them).
What I tried
- Disabling “SSH Key Agent” in
XFCE settings → Startup Applications
- Copying
/etc/xdg/autostart/gnome-keyring-ssh.desktopto~/.config/autostartand then appending the lineHidden=trueto the copied file
Neither of the above prevented gnome-keyring-daemon from starting up on boot, since I still can see it in ps.
- Creating
~/.pam_environmentthen addingGSM_SKIP_SSH_AGENT_WORKAROUND DEFAULT=1there - Reverting back to RSA
- Playing with
ssh-add
- Installing
git-credential-libsecretthen doinggit config --global credential.helper /usr/lib/git/git-credential-libsecret
- Toying with the thought of obliterating the
gnome-keyringpackage altogether, which was abandoned because apparently several important packages depend on it
ssh git gnome-keyring seahorse
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
add a comment |
Here’s a Yet Another Question about the clash between ssh and gnome-keyring-daemon, since after spending hours and hours on the Internet I finally gave up.
Environment
- OS: openSUSE 15.0
- DE: XFCE
- gnome-keyring-daemon version: 3.20.1
- seahorse version: 3.20.0
- git version: 2.16.4
- ssh version: OpenSSH_7.6p1, OpenSSL 1.1.0i-fips 14 Aug 2018
Situation
Trying to git pull a repo leads to a message
sign_and_send_pubkey: signing failed: agent refused operation
, even though for years I was getting a neat GUI prompt which remembered the typed password throughout the current session. (AFAIU, this prompt was shown by Seahorse?).
After doing a killall gnome-keyring-daemon, successive attempts to do a git pull lead to a terminal prompt
Enter passphrase for key '/home/user/.ssh/id_rsa':
which does not store the password anywhere (AFAIU, this means that ssh-agent is not working?).
The same effect can be achieved by adding SSH_AUTH_SOCK=0 in front of git pull.
What I want
- Doing a
git pullcaches my SSH password over the course of my current login session (like it was before). Neat GUI prompt is optional. - Ed25519 keys are supported. (Apparently GNOME Keyring has (had?) some problems with them).
What I tried
- Disabling “SSH Key Agent” in
XFCE settings → Startup Applications
- Copying
/etc/xdg/autostart/gnome-keyring-ssh.desktopto~/.config/autostartand then appending the lineHidden=trueto the copied file
Neither of the above prevented gnome-keyring-daemon from starting up on boot, since I still can see it in ps.
- Creating
~/.pam_environmentthen addingGSM_SKIP_SSH_AGENT_WORKAROUND DEFAULT=1there - Reverting back to RSA
- Playing with
ssh-add
- Installing
git-credential-libsecretthen doinggit config --global credential.helper /usr/lib/git/git-credential-libsecret
- Toying with the thought of obliterating the
gnome-keyringpackage altogether, which was abandoned because apparently several important packages depend on it
ssh git gnome-keyring seahorse
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
Here’s a Yet Another Question about the clash between ssh and gnome-keyring-daemon, since after spending hours and hours on the Internet I finally gave up.
Environment
- OS: openSUSE 15.0
- DE: XFCE
- gnome-keyring-daemon version: 3.20.1
- seahorse version: 3.20.0
- git version: 2.16.4
- ssh version: OpenSSH_7.6p1, OpenSSL 1.1.0i-fips 14 Aug 2018
Situation
Trying to git pull a repo leads to a message
sign_and_send_pubkey: signing failed: agent refused operation
, even though for years I was getting a neat GUI prompt which remembered the typed password throughout the current session. (AFAIU, this prompt was shown by Seahorse?).
After doing a killall gnome-keyring-daemon, successive attempts to do a git pull lead to a terminal prompt
Enter passphrase for key '/home/user/.ssh/id_rsa':
which does not store the password anywhere (AFAIU, this means that ssh-agent is not working?).
The same effect can be achieved by adding SSH_AUTH_SOCK=0 in front of git pull.
What I want
- Doing a
git pullcaches my SSH password over the course of my current login session (like it was before). Neat GUI prompt is optional. - Ed25519 keys are supported. (Apparently GNOME Keyring has (had?) some problems with them).
What I tried
- Disabling “SSH Key Agent” in
XFCE settings → Startup Applications
- Copying
/etc/xdg/autostart/gnome-keyring-ssh.desktopto~/.config/autostartand then appending the lineHidden=trueto the copied file
Neither of the above prevented gnome-keyring-daemon from starting up on boot, since I still can see it in ps.
- Creating
~/.pam_environmentthen addingGSM_SKIP_SSH_AGENT_WORKAROUND DEFAULT=1there - Reverting back to RSA
- Playing with
ssh-add
- Installing
git-credential-libsecretthen doinggit config --global credential.helper /usr/lib/git/git-credential-libsecret
- Toying with the thought of obliterating the
gnome-keyringpackage altogether, which was abandoned because apparently several important packages depend on it
ssh git gnome-keyring seahorse
ssh git gnome-keyring seahorse
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
asked Jan 28 at 4:05
ScumCoderScumCoder
1115
1115
add a comment |
add a comment |
0
active
oldest
votes
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%2f497119%2fyet-another-sign-and-send-pubkey-signing-failed-agent-refused-operation%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f497119%2fyet-another-sign-and-send-pubkey-signing-failed-agent-refused-operation%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
