ssh-agent running with i3wm keeps promting for password at each git push The Next CEO of Stack...

How long to clear the 'suck zone' of a turbofan after start is initiated?

How do scammers retract money, while you can’t?

Why didn't Khan get resurrected in the Genesis Explosion?

Should I tutor a student who I know has cheated on their homework?

To not tell, not take, and not want

Is "for causing autism in X" grammatical?

Rotate a column

Example of a Mathematician/Physicist whose Other Publications during their PhD eclipsed their PhD Thesis

Preparing Indesign booklet with .psd graphics for print

WOW air has ceased operation, can I get my tickets refunded?

Solidity! Invalid implicit conversion from string memory to bytes memory requested

Unreliable Magic - Is it worth it?

How to count occurrences of text in a file?

Novel about a guy who is possessed by the divine essence and the world ends?

Is 'diverse range' a pleonastic phrase?

Why do variable in an inner function return nan when there is the same variable name at the inner function declared after log

If the heap is zero-initialized for security, then why is the stack merely uninitialized?

Multiple labels for a single equation

What does convergence in distribution "in the Gromov–Hausdorff" sense mean?

Received an invoice from my ex-employer billing me for training; how to handle?

Can you replace a racial trait cantrip when leveling up?

"In the right combination" vs "with the right combination"?

Which tube will fit a -(700 x 25c) wheel?

What happened in Rome, when the western empire "fell"?



ssh-agent running with i3wm keeps promting for password at each git push



The Next CEO of Stack OverflowBypassing workplace HTTP proxy (using SSH, or other)SSH passwordless authentication failureSSH 'Host key verification failed' errorgit clone extremely slow using sshSSH error ssh_exchange_identification: read: Connection reset by peerDid I just send my private ssh key?unable to ssh after generated public and private keys in windows 7Unable to connect to SSH after generated public key and private keyssh does not work when called from systemdRsync via SSH doesn't work












2















I have installed Debian testing with i3wm, using SDDM (Simple Desktop Display Manager) to start it. In the i3 workspace, I could find the ssh-agent process already started. However, I still am being prompted to input my key passphrase everytime I do a git push to github (the remote is git@github.com:user/repo.git). See below for the details. Any way to prevent this from happening?



I have already added my id_rsa to my ssh-agent.



$ cat /proc/version 
(Linux version 4.1.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-3) ) #1 SMP Debian 4.1.6-1 (2015-08-23))

$ i3 --version
i3 version 4.10.3 (2015-07-30, branch "4.10.3") © 2009-2014 Michael Stapelberg and contributors

$ ssh -V
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015

$ apt-cache info sddm
Package: sddm
Version: 0.11.0-3


I successfully tested this SSH connection with ssh -v -T git@github.com and it looks fine:



ssh -v -T git@github.com
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /home/user/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to github.com [192.30.252.130] port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9p1 Debian-1
debug1: Remote protocol version 2.0, remote software version libssh-0.7.0
debug1: no match: libssh-0.7.0
debug1: Authenticating to github.com:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/user/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/user/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
Enter passphrase for key '/home/user/.ssh/id_rsa':
debug1: Authentication succeeded (publickey).
Authenticated to github.com ([192.30.252.130]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Hi user! You've successfully authenticated, but GitHub does not provide shell access.
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3252, received 1776 bytes, in 0.1 seconds
Bytes per second: sent 59136.9, received 32296.2
debug1: Exit status 1


And here is the output of git remote show origin:



Enter passphrase for key '/home/user/.ssh/id_rsa': 
* remote origin
Fetch URL: git@github.com:user/repo.git
Push URL: git@github.com:user/repo.git
HEAD branch: master
Remote branch:
master tracked
Local branch configured for 'git pull':
master merges with remote master
Local ref configured for 'git push':
master pushes to master (up to date)









share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Problem still persists.

    – hyiltiz
    Sep 13 '15 at 20:12
















2















I have installed Debian testing with i3wm, using SDDM (Simple Desktop Display Manager) to start it. In the i3 workspace, I could find the ssh-agent process already started. However, I still am being prompted to input my key passphrase everytime I do a git push to github (the remote is git@github.com:user/repo.git). See below for the details. Any way to prevent this from happening?



I have already added my id_rsa to my ssh-agent.



$ cat /proc/version 
(Linux version 4.1.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-3) ) #1 SMP Debian 4.1.6-1 (2015-08-23))

$ i3 --version
i3 version 4.10.3 (2015-07-30, branch "4.10.3") © 2009-2014 Michael Stapelberg and contributors

$ ssh -V
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015

$ apt-cache info sddm
Package: sddm
Version: 0.11.0-3


I successfully tested this SSH connection with ssh -v -T git@github.com and it looks fine:



ssh -v -T git@github.com
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /home/user/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to github.com [192.30.252.130] port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9p1 Debian-1
debug1: Remote protocol version 2.0, remote software version libssh-0.7.0
debug1: no match: libssh-0.7.0
debug1: Authenticating to github.com:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/user/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/user/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
Enter passphrase for key '/home/user/.ssh/id_rsa':
debug1: Authentication succeeded (publickey).
Authenticated to github.com ([192.30.252.130]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Hi user! You've successfully authenticated, but GitHub does not provide shell access.
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3252, received 1776 bytes, in 0.1 seconds
Bytes per second: sent 59136.9, received 32296.2
debug1: Exit status 1


And here is the output of git remote show origin:



Enter passphrase for key '/home/user/.ssh/id_rsa': 
* remote origin
Fetch URL: git@github.com:user/repo.git
Push URL: git@github.com:user/repo.git
HEAD branch: master
Remote branch:
master tracked
Local branch configured for 'git pull':
master merges with remote master
Local ref configured for 'git push':
master pushes to master (up to date)









share|improve this question
















bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Problem still persists.

    – hyiltiz
    Sep 13 '15 at 20:12














2












2








2








I have installed Debian testing with i3wm, using SDDM (Simple Desktop Display Manager) to start it. In the i3 workspace, I could find the ssh-agent process already started. However, I still am being prompted to input my key passphrase everytime I do a git push to github (the remote is git@github.com:user/repo.git). See below for the details. Any way to prevent this from happening?



I have already added my id_rsa to my ssh-agent.



$ cat /proc/version 
(Linux version 4.1.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-3) ) #1 SMP Debian 4.1.6-1 (2015-08-23))

$ i3 --version
i3 version 4.10.3 (2015-07-30, branch "4.10.3") © 2009-2014 Michael Stapelberg and contributors

$ ssh -V
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015

$ apt-cache info sddm
Package: sddm
Version: 0.11.0-3


I successfully tested this SSH connection with ssh -v -T git@github.com and it looks fine:



ssh -v -T git@github.com
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /home/user/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to github.com [192.30.252.130] port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9p1 Debian-1
debug1: Remote protocol version 2.0, remote software version libssh-0.7.0
debug1: no match: libssh-0.7.0
debug1: Authenticating to github.com:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/user/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/user/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
Enter passphrase for key '/home/user/.ssh/id_rsa':
debug1: Authentication succeeded (publickey).
Authenticated to github.com ([192.30.252.130]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Hi user! You've successfully authenticated, but GitHub does not provide shell access.
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3252, received 1776 bytes, in 0.1 seconds
Bytes per second: sent 59136.9, received 32296.2
debug1: Exit status 1


And here is the output of git remote show origin:



Enter passphrase for key '/home/user/.ssh/id_rsa': 
* remote origin
Fetch URL: git@github.com:user/repo.git
Push URL: git@github.com:user/repo.git
HEAD branch: master
Remote branch:
master tracked
Local branch configured for 'git pull':
master merges with remote master
Local ref configured for 'git push':
master pushes to master (up to date)









share|improve this question
















I have installed Debian testing with i3wm, using SDDM (Simple Desktop Display Manager) to start it. In the i3 workspace, I could find the ssh-agent process already started. However, I still am being prompted to input my key passphrase everytime I do a git push to github (the remote is git@github.com:user/repo.git). See below for the details. Any way to prevent this from happening?



I have already added my id_rsa to my ssh-agent.



$ cat /proc/version 
(Linux version 4.1.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-3) ) #1 SMP Debian 4.1.6-1 (2015-08-23))

$ i3 --version
i3 version 4.10.3 (2015-07-30, branch "4.10.3") © 2009-2014 Michael Stapelberg and contributors

$ ssh -V
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015

$ apt-cache info sddm
Package: sddm
Version: 0.11.0-3


I successfully tested this SSH connection with ssh -v -T git@github.com and it looks fine:



ssh -v -T git@github.com
OpenSSH_6.9p1 Debian-1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /home/user/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to github.com [192.30.252.130] port 22.
debug1: Connection established.
debug1: identity file /home/user/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/user/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9p1 Debian-1
debug1: Remote protocol version 2.0, remote software version libssh-0.7.0
debug1: no match: libssh-0.7.0
debug1: Authenticating to github.com:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:nThbg6kXUpJWGl7E1IGOCspRomTxdCARLviKw6E5SY8
debug1: Host 'github.com' is known and matches the RSA host key.
debug1: Found key in /home/user/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/user/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
Enter passphrase for key '/home/user/.ssh/id_rsa':
debug1: Authentication succeeded (publickey).
Authenticated to github.com ([192.30.252.130]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Hi user! You've successfully authenticated, but GitHub does not provide shell access.
debug1: channel 0: free: client-session, nchannels 1
Transferred: sent 3252, received 1776 bytes, in 0.1 seconds
Bytes per second: sent 59136.9, received 32296.2
debug1: Exit status 1


And here is the output of git remote show origin:



Enter passphrase for key '/home/user/.ssh/id_rsa': 
* remote origin
Fetch URL: git@github.com:user/repo.git
Push URL: git@github.com:user/repo.git
HEAD branch: master
Remote branch:
master tracked
Local branch configured for 'git pull':
master merges with remote master
Local ref configured for 'git push':
master pushes to master (up to date)






linux ssh git ssh-agent i3-window-manager






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Sep 10 '15 at 5:16









JakeGould

32.2k1098141




32.2k1098141










asked Sep 9 '15 at 1:58









hyiltizhyiltiz

191114




191114





bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 14 mins ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Problem still persists.

    – hyiltiz
    Sep 13 '15 at 20:12



















  • Problem still persists.

    – hyiltiz
    Sep 13 '15 at 20:12

















Problem still persists.

– hyiltiz
Sep 13 '15 at 20:12





Problem still persists.

– hyiltiz
Sep 13 '15 at 20:12










1 Answer
1






active

oldest

votes


















0














I execute ssh-add in my i3 config file. This way, I am prompted for my passphrase on startup, after which I can use the key without being prompted again.



Don't know what your setup is (how you add your key to the agent or if you use gnome keyring or something), but this may be an option for you, too.






share|improve this answer



















  • 1





    Okay, I can imagine that way of solving it. But I have logged in to i3 by entering my user password from the SSDM login manager (provided by KDE5). Any way to add those keys WITHOUT entering the key passwords? I recall that some keychain programs can use the user login password as a master password then automatically add all keys.

    – hyiltiz
    Dec 10 '15 at 5:29












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f970233%2fssh-agent-running-with-i3wm-keeps-promting-for-password-at-each-git-push%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









0














I execute ssh-add in my i3 config file. This way, I am prompted for my passphrase on startup, after which I can use the key without being prompted again.



Don't know what your setup is (how you add your key to the agent or if you use gnome keyring or something), but this may be an option for you, too.






share|improve this answer



















  • 1





    Okay, I can imagine that way of solving it. But I have logged in to i3 by entering my user password from the SSDM login manager (provided by KDE5). Any way to add those keys WITHOUT entering the key passwords? I recall that some keychain programs can use the user login password as a master password then automatically add all keys.

    – hyiltiz
    Dec 10 '15 at 5:29
















0














I execute ssh-add in my i3 config file. This way, I am prompted for my passphrase on startup, after which I can use the key without being prompted again.



Don't know what your setup is (how you add your key to the agent or if you use gnome keyring or something), but this may be an option for you, too.






share|improve this answer



















  • 1





    Okay, I can imagine that way of solving it. But I have logged in to i3 by entering my user password from the SSDM login manager (provided by KDE5). Any way to add those keys WITHOUT entering the key passwords? I recall that some keychain programs can use the user login password as a master password then automatically add all keys.

    – hyiltiz
    Dec 10 '15 at 5:29














0












0








0







I execute ssh-add in my i3 config file. This way, I am prompted for my passphrase on startup, after which I can use the key without being prompted again.



Don't know what your setup is (how you add your key to the agent or if you use gnome keyring or something), but this may be an option for you, too.






share|improve this answer













I execute ssh-add in my i3 config file. This way, I am prompted for my passphrase on startup, after which I can use the key without being prompted again.



Don't know what your setup is (how you add your key to the agent or if you use gnome keyring or something), but this may be an option for you, too.







share|improve this answer












share|improve this answer



share|improve this answer










answered Sep 23 '15 at 12:08









Philipp MoersPhilipp Moers

22319




22319








  • 1





    Okay, I can imagine that way of solving it. But I have logged in to i3 by entering my user password from the SSDM login manager (provided by KDE5). Any way to add those keys WITHOUT entering the key passwords? I recall that some keychain programs can use the user login password as a master password then automatically add all keys.

    – hyiltiz
    Dec 10 '15 at 5:29














  • 1





    Okay, I can imagine that way of solving it. But I have logged in to i3 by entering my user password from the SSDM login manager (provided by KDE5). Any way to add those keys WITHOUT entering the key passwords? I recall that some keychain programs can use the user login password as a master password then automatically add all keys.

    – hyiltiz
    Dec 10 '15 at 5:29








1




1





Okay, I can imagine that way of solving it. But I have logged in to i3 by entering my user password from the SSDM login manager (provided by KDE5). Any way to add those keys WITHOUT entering the key passwords? I recall that some keychain programs can use the user login password as a master password then automatically add all keys.

– hyiltiz
Dec 10 '15 at 5:29





Okay, I can imagine that way of solving it. But I have logged in to i3 by entering my user password from the SSDM login manager (provided by KDE5). Any way to add those keys WITHOUT entering the key passwords? I recall that some keychain programs can use the user login password as a master password then automatically add all keys.

– hyiltiz
Dec 10 '15 at 5:29


















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • 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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f970233%2fssh-agent-running-with-i3wm-keeps-promting-for-password-at-each-git-push%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

looking for continuous Screen Capture for retroactivly reproducing errors, timeback machineRolling desktop...