Why can't I authenticate to GitHub?
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/c/Users/my_username/.ssh/id_dsa):Enter
Enter passphrase (empty for no passphrase):Enter
Enter same passphrase again: Enter
Your identification has been saved in /c/Users/my_username/.ssh/id_dsa.
Your public key has been saved in /c/Users/my_username/.ssh/id_dsa.pub.
The key fingerprint is: Enter
SHA256:KMLyesG1eWkXq1iI4y7i+4bmVKgZBdCnReukvJgrtP0 my_username@my_username-laptop
The key's randomart image is: Enter
+---[DSA 1024]----+
|+. .. |
| .. o. |
| .+o |
| +o+. .. |
|oo=+o+..So |
|.O*o+.= o |
|*o*o = o |
|=*oo. . |
|OB=..E |
+----[SHA256]-----+
my_username@my_username-laptop MINGW64 ~ (master)
$ cd .ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cd ~/.ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls
github_rsa id_dsa known_hosts rsa_key_pair.pub
github_rsa.pub id_dsa.pub rsa_key_pair
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls -la
total 45
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:43 ./
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:08 ../
-rw-r--r-- 1 my_username 197121 668 Nov 17 23:43 id_dsa
-rw-r--r-- 1 my_username 197121 614 Nov 17 23:43 id_dsa.pub
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cat id_dsa.pub
ssh-dss AAAAB3NzaC1kc3MAAACBAOrkqv9wt7WcngRfKSaMrCSXn8BfJZN7wEJWvpuqpTYWBzCAylqUSVA+GpMuXGhaDdwHJFftmoxi81PnASpIoZZrIRgqRHRnQph9DnQikB1Bkf4B+EpzD3EwKYWRUOFrHwnjPU1ByRgFOTADXn/O9SIj+9APKer9xFNHaBvv9AvDAAAAFQCYK15hX9llcyIPsHedNTpE0BhgaQAAAIAZ3xOjbu1Vs0yposrwfHdc1+WoUdt89Y8a2YEvmeToR7/M7SM6IPPgbxLTz6l32pbmFFUDknMpX0rL/VaP/ygLifKJDxtWlE2doQR+2FwsvQKnk1wyXlYGXPCaI6flxqJRVV8/VJapQBRAC/cC6g6MNPbTs9GyV/z/SYBE/f4EhgAAAIEAlVinwInGC2gfWL5y7iPmv4gHWuJx0bmGq8Dc5UGdB99uxGRkdOlPFQ8BP6dZ1T8+DlikwPE2CH7RNIb+08KEvtdRJCy++6x0wnvL6ApPM1szNL+gUdL8X2/Mt9r2bj3LvjIrz21u4lXgOa+OsCanu4yUfHhPcj5YgQrrrn3P0Gs= my_username@my_username-laptop
my_username@my_username-laptop MINGW64 ~/.ssh (master)
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh -vT git@github.com
OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to github.com [192.30.252.129] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.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 /c/Users/my_username/.ssh/known_hosts:1
Warning: Permanently added the RSA host key for IP address '192.30.252.129' to the list of known hosts.
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: Trying private key: /c/Users/my_username/.ssh/id_rsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_dsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ecdsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-agent -s
SSH_AUTH_SOCK=/tmp/ssh-8kgSDhweA5gl/agent.11684; export SSH_AUTH_SOCK;
SSH_AGENT_PID=13892; export SSH_AGENT_PID;
echo Agent pid 13892;
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-add -l
Could not open a connection to your authentication agent.
my_username@my_username-laptop MINGW64 ~ (master)
$
ssh ssh-agent github
add a comment |
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/c/Users/my_username/.ssh/id_dsa):Enter
Enter passphrase (empty for no passphrase):Enter
Enter same passphrase again: Enter
Your identification has been saved in /c/Users/my_username/.ssh/id_dsa.
Your public key has been saved in /c/Users/my_username/.ssh/id_dsa.pub.
The key fingerprint is: Enter
SHA256:KMLyesG1eWkXq1iI4y7i+4bmVKgZBdCnReukvJgrtP0 my_username@my_username-laptop
The key's randomart image is: Enter
+---[DSA 1024]----+
|+. .. |
| .. o. |
| .+o |
| +o+. .. |
|oo=+o+..So |
|.O*o+.= o |
|*o*o = o |
|=*oo. . |
|OB=..E |
+----[SHA256]-----+
my_username@my_username-laptop MINGW64 ~ (master)
$ cd .ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cd ~/.ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls
github_rsa id_dsa known_hosts rsa_key_pair.pub
github_rsa.pub id_dsa.pub rsa_key_pair
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls -la
total 45
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:43 ./
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:08 ../
-rw-r--r-- 1 my_username 197121 668 Nov 17 23:43 id_dsa
-rw-r--r-- 1 my_username 197121 614 Nov 17 23:43 id_dsa.pub
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cat id_dsa.pub
ssh-dss AAAAB3NzaC1kc3MAAACBAOrkqv9wt7WcngRfKSaMrCSXn8BfJZN7wEJWvpuqpTYWBzCAylqUSVA+GpMuXGhaDdwHJFftmoxi81PnASpIoZZrIRgqRHRnQph9DnQikB1Bkf4B+EpzD3EwKYWRUOFrHwnjPU1ByRgFOTADXn/O9SIj+9APKer9xFNHaBvv9AvDAAAAFQCYK15hX9llcyIPsHedNTpE0BhgaQAAAIAZ3xOjbu1Vs0yposrwfHdc1+WoUdt89Y8a2YEvmeToR7/M7SM6IPPgbxLTz6l32pbmFFUDknMpX0rL/VaP/ygLifKJDxtWlE2doQR+2FwsvQKnk1wyXlYGXPCaI6flxqJRVV8/VJapQBRAC/cC6g6MNPbTs9GyV/z/SYBE/f4EhgAAAIEAlVinwInGC2gfWL5y7iPmv4gHWuJx0bmGq8Dc5UGdB99uxGRkdOlPFQ8BP6dZ1T8+DlikwPE2CH7RNIb+08KEvtdRJCy++6x0wnvL6ApPM1szNL+gUdL8X2/Mt9r2bj3LvjIrz21u4lXgOa+OsCanu4yUfHhPcj5YgQrrrn3P0Gs= my_username@my_username-laptop
my_username@my_username-laptop MINGW64 ~/.ssh (master)
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh -vT git@github.com
OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to github.com [192.30.252.129] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.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 /c/Users/my_username/.ssh/known_hosts:1
Warning: Permanently added the RSA host key for IP address '192.30.252.129' to the list of known hosts.
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: Trying private key: /c/Users/my_username/.ssh/id_rsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_dsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ecdsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-agent -s
SSH_AUTH_SOCK=/tmp/ssh-8kgSDhweA5gl/agent.11684; export SSH_AUTH_SOCK;
SSH_AGENT_PID=13892; export SSH_AGENT_PID;
echo Agent pid 13892;
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-add -l
Could not open a connection to your authentication agent.
my_username@my_username-laptop MINGW64 ~ (master)
$
ssh ssh-agent github
2
I can't see a question here. Did you upload your public key to github via their webinterface?
– sebix
Nov 22 '15 at 18:06
@sebix, yes. It didn't work.
– user109285
Nov 22 '15 at 18:14
add a comment |
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/c/Users/my_username/.ssh/id_dsa):Enter
Enter passphrase (empty for no passphrase):Enter
Enter same passphrase again: Enter
Your identification has been saved in /c/Users/my_username/.ssh/id_dsa.
Your public key has been saved in /c/Users/my_username/.ssh/id_dsa.pub.
The key fingerprint is: Enter
SHA256:KMLyesG1eWkXq1iI4y7i+4bmVKgZBdCnReukvJgrtP0 my_username@my_username-laptop
The key's randomart image is: Enter
+---[DSA 1024]----+
|+. .. |
| .. o. |
| .+o |
| +o+. .. |
|oo=+o+..So |
|.O*o+.= o |
|*o*o = o |
|=*oo. . |
|OB=..E |
+----[SHA256]-----+
my_username@my_username-laptop MINGW64 ~ (master)
$ cd .ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cd ~/.ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls
github_rsa id_dsa known_hosts rsa_key_pair.pub
github_rsa.pub id_dsa.pub rsa_key_pair
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls -la
total 45
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:43 ./
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:08 ../
-rw-r--r-- 1 my_username 197121 668 Nov 17 23:43 id_dsa
-rw-r--r-- 1 my_username 197121 614 Nov 17 23:43 id_dsa.pub
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cat id_dsa.pub
ssh-dss AAAAB3NzaC1kc3MAAACBAOrkqv9wt7WcngRfKSaMrCSXn8BfJZN7wEJWvpuqpTYWBzCAylqUSVA+GpMuXGhaDdwHJFftmoxi81PnASpIoZZrIRgqRHRnQph9DnQikB1Bkf4B+EpzD3EwKYWRUOFrHwnjPU1ByRgFOTADXn/O9SIj+9APKer9xFNHaBvv9AvDAAAAFQCYK15hX9llcyIPsHedNTpE0BhgaQAAAIAZ3xOjbu1Vs0yposrwfHdc1+WoUdt89Y8a2YEvmeToR7/M7SM6IPPgbxLTz6l32pbmFFUDknMpX0rL/VaP/ygLifKJDxtWlE2doQR+2FwsvQKnk1wyXlYGXPCaI6flxqJRVV8/VJapQBRAC/cC6g6MNPbTs9GyV/z/SYBE/f4EhgAAAIEAlVinwInGC2gfWL5y7iPmv4gHWuJx0bmGq8Dc5UGdB99uxGRkdOlPFQ8BP6dZ1T8+DlikwPE2CH7RNIb+08KEvtdRJCy++6x0wnvL6ApPM1szNL+gUdL8X2/Mt9r2bj3LvjIrz21u4lXgOa+OsCanu4yUfHhPcj5YgQrrrn3P0Gs= my_username@my_username-laptop
my_username@my_username-laptop MINGW64 ~/.ssh (master)
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh -vT git@github.com
OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to github.com [192.30.252.129] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.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 /c/Users/my_username/.ssh/known_hosts:1
Warning: Permanently added the RSA host key for IP address '192.30.252.129' to the list of known hosts.
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: Trying private key: /c/Users/my_username/.ssh/id_rsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_dsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ecdsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-agent -s
SSH_AUTH_SOCK=/tmp/ssh-8kgSDhweA5gl/agent.11684; export SSH_AUTH_SOCK;
SSH_AGENT_PID=13892; export SSH_AGENT_PID;
echo Agent pid 13892;
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-add -l
Could not open a connection to your authentication agent.
my_username@my_username-laptop MINGW64 ~ (master)
$
ssh ssh-agent github
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-keygen -t dsa
Generating public/private dsa key pair.
Enter file in which to save the key (/c/Users/my_username/.ssh/id_dsa):Enter
Enter passphrase (empty for no passphrase):Enter
Enter same passphrase again: Enter
Your identification has been saved in /c/Users/my_username/.ssh/id_dsa.
Your public key has been saved in /c/Users/my_username/.ssh/id_dsa.pub.
The key fingerprint is: Enter
SHA256:KMLyesG1eWkXq1iI4y7i+4bmVKgZBdCnReukvJgrtP0 my_username@my_username-laptop
The key's randomart image is: Enter
+---[DSA 1024]----+
|+. .. |
| .. o. |
| .+o |
| +o+. .. |
|oo=+o+..So |
|.O*o+.= o |
|*o*o = o |
|=*oo. . |
|OB=..E |
+----[SHA256]-----+
my_username@my_username-laptop MINGW64 ~ (master)
$ cd .ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cd ~/.ssh
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls
github_rsa id_dsa known_hosts rsa_key_pair.pub
github_rsa.pub id_dsa.pub rsa_key_pair
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ ls -la
total 45
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:43 ./
drwxr-xr-x 1 my_username 197121 0 Nov 17 23:08 ../
-rw-r--r-- 1 my_username 197121 668 Nov 17 23:43 id_dsa
-rw-r--r-- 1 my_username 197121 614 Nov 17 23:43 id_dsa.pub
my_username@my_username-laptop MINGW64 ~/.ssh (master)
$ cat id_dsa.pub
ssh-dss AAAAB3NzaC1kc3MAAACBAOrkqv9wt7WcngRfKSaMrCSXn8BfJZN7wEJWvpuqpTYWBzCAylqUSVA+GpMuXGhaDdwHJFftmoxi81PnASpIoZZrIRgqRHRnQph9DnQikB1Bkf4B+EpzD3EwKYWRUOFrHwnjPU1ByRgFOTADXn/O9SIj+9APKer9xFNHaBvv9AvDAAAAFQCYK15hX9llcyIPsHedNTpE0BhgaQAAAIAZ3xOjbu1Vs0yposrwfHdc1+WoUdt89Y8a2YEvmeToR7/M7SM6IPPgbxLTz6l32pbmFFUDknMpX0rL/VaP/ygLifKJDxtWlE2doQR+2FwsvQKnk1wyXlYGXPCaI6flxqJRVV8/VJapQBRAC/cC6g6MNPbTs9GyV/z/SYBE/f4EhgAAAIEAlVinwInGC2gfWL5y7iPmv4gHWuJx0bmGq8Dc5UGdB99uxGRkdOlPFQ8BP6dZ1T8+DlikwPE2CH7RNIb+08KEvtdRJCy++6x0wnvL6ApPM1szNL+gUdL8X2/Mt9r2bj3LvjIrz21u4lXgOa+OsCanu4yUfHhPcj5YgQrrrn3P0Gs= my_username@my_username-laptop
my_username@my_username-laptop MINGW64 ~/.ssh (master)
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh -vT git@github.com
OpenSSH_7.1p1, OpenSSL 1.0.2d 9 Jul 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to github.com [192.30.252.129] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/my_username/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.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 /c/Users/my_username/.ssh/known_hosts:1
Warning: Permanently added the RSA host key for IP address '192.30.252.129' to the list of known hosts.
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: Trying private key: /c/Users/my_username/.ssh/id_rsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_dsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ecdsa
debug1: Trying private key: /c/Users/my_username/.ssh/id_ed25519
debug1: No more authentication methods to try.
Permission denied (publickey).
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-agent -s
SSH_AUTH_SOCK=/tmp/ssh-8kgSDhweA5gl/agent.11684; export SSH_AUTH_SOCK;
SSH_AGENT_PID=13892; export SSH_AGENT_PID;
echo Agent pid 13892;
my_username@my_username-laptop MINGW64 ~ (master)
$ ssh-add -l
Could not open a connection to your authentication agent.
my_username@my_username-laptop MINGW64 ~ (master)
$
ssh ssh-agent github
ssh ssh-agent github
edited Nov 18 '15 at 5:20
dave_thompson_085
2,14711111
2,14711111
asked Nov 17 '15 at 23:34
user109285
2
I can't see a question here. Did you upload your public key to github via their webinterface?
– sebix
Nov 22 '15 at 18:06
@sebix, yes. It didn't work.
– user109285
Nov 22 '15 at 18:14
add a comment |
2
I can't see a question here. Did you upload your public key to github via their webinterface?
– sebix
Nov 22 '15 at 18:06
@sebix, yes. It didn't work.
– user109285
Nov 22 '15 at 18:14
2
2
I can't see a question here. Did you upload your public key to github via their webinterface?
– sebix
Nov 22 '15 at 18:06
I can't see a question here. Did you upload your public key to github via their webinterface?
– sebix
Nov 22 '15 at 18:06
@sebix, yes. It didn't work.
– user109285
Nov 22 '15 at 18:14
@sebix, yes. It didn't work.
– user109285
Nov 22 '15 at 18:14
add a comment |
2 Answers
2
active
oldest
votes
I notice you're using a DSA key. OpenSSH 7.0 and higher disabled support for DSA keys by default. You might check whether that is causing problems. See SSH keeps skipping my pubkey and asking for a password and https://superuser.com/q/1016989/93541.
add a comment |
To authenticate an ssh client to a server using publickey, you generate a keypair on the client, keep the privatekey on the client, and copy the publickey to your
authorized_keys
file on the server which must be in~/.ssh
owned by you and have permissions only for owner (usually 600 akarw-------
). You did not do the second part. If it's too complicated for you, many systems have a scriptssh-copy-id
which does it for you with a good deal of handholding and error checking.You don't need
ssh-agent
because your keyfile is in the default location and has no password.To use
ssh-agent
you must either run a new process underssh-agent
, such as new shell or a new terminal (inherently with a new shell) that has environment variables set to access the agent process or have your shelleval
the output fromssh-agent
so those environment variables are set in your shell. You did not do either. From the man page:
There are two main ways to get an agent set up: The first is that the
agent starts a new subcommand into which some environment variables are
exported, eg ssh-agent xterm &. The second is that the agent prints the
needed shell commands (either sh(1) or csh(1) syntax can be generated)
which can be evaluated in the calling shell, eg eval 'ssh-agent -s' for
Bourne-type shells such as sh(1) or ksh(1) and eval 'ssh-agent -c' for
csh(1) and derivatives.
Later ssh(1) looks at these variables and uses them to establish a con-
nection to the agent.
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%2f243728%2fwhy-cant-i-authenticate-to-github%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
I notice you're using a DSA key. OpenSSH 7.0 and higher disabled support for DSA keys by default. You might check whether that is causing problems. See SSH keeps skipping my pubkey and asking for a password and https://superuser.com/q/1016989/93541.
add a comment |
I notice you're using a DSA key. OpenSSH 7.0 and higher disabled support for DSA keys by default. You might check whether that is causing problems. See SSH keeps skipping my pubkey and asking for a password and https://superuser.com/q/1016989/93541.
add a comment |
I notice you're using a DSA key. OpenSSH 7.0 and higher disabled support for DSA keys by default. You might check whether that is causing problems. See SSH keeps skipping my pubkey and asking for a password and https://superuser.com/q/1016989/93541.
I notice you're using a DSA key. OpenSSH 7.0 and higher disabled support for DSA keys by default. You might check whether that is causing problems. See SSH keeps skipping my pubkey and asking for a password and https://superuser.com/q/1016989/93541.
edited Apr 13 '17 at 12:36
Community♦
1
1
answered Dec 23 '15 at 6:29
D.W.D.W.
1,16741736
1,16741736
add a comment |
add a comment |
To authenticate an ssh client to a server using publickey, you generate a keypair on the client, keep the privatekey on the client, and copy the publickey to your
authorized_keys
file on the server which must be in~/.ssh
owned by you and have permissions only for owner (usually 600 akarw-------
). You did not do the second part. If it's too complicated for you, many systems have a scriptssh-copy-id
which does it for you with a good deal of handholding and error checking.You don't need
ssh-agent
because your keyfile is in the default location and has no password.To use
ssh-agent
you must either run a new process underssh-agent
, such as new shell or a new terminal (inherently with a new shell) that has environment variables set to access the agent process or have your shelleval
the output fromssh-agent
so those environment variables are set in your shell. You did not do either. From the man page:
There are two main ways to get an agent set up: The first is that the
agent starts a new subcommand into which some environment variables are
exported, eg ssh-agent xterm &. The second is that the agent prints the
needed shell commands (either sh(1) or csh(1) syntax can be generated)
which can be evaluated in the calling shell, eg eval 'ssh-agent -s' for
Bourne-type shells such as sh(1) or ksh(1) and eval 'ssh-agent -c' for
csh(1) and derivatives.
Later ssh(1) looks at these variables and uses them to establish a con-
nection to the agent.
add a comment |
To authenticate an ssh client to a server using publickey, you generate a keypair on the client, keep the privatekey on the client, and copy the publickey to your
authorized_keys
file on the server which must be in~/.ssh
owned by you and have permissions only for owner (usually 600 akarw-------
). You did not do the second part. If it's too complicated for you, many systems have a scriptssh-copy-id
which does it for you with a good deal of handholding and error checking.You don't need
ssh-agent
because your keyfile is in the default location and has no password.To use
ssh-agent
you must either run a new process underssh-agent
, such as new shell or a new terminal (inherently with a new shell) that has environment variables set to access the agent process or have your shelleval
the output fromssh-agent
so those environment variables are set in your shell. You did not do either. From the man page:
There are two main ways to get an agent set up: The first is that the
agent starts a new subcommand into which some environment variables are
exported, eg ssh-agent xterm &. The second is that the agent prints the
needed shell commands (either sh(1) or csh(1) syntax can be generated)
which can be evaluated in the calling shell, eg eval 'ssh-agent -s' for
Bourne-type shells such as sh(1) or ksh(1) and eval 'ssh-agent -c' for
csh(1) and derivatives.
Later ssh(1) looks at these variables and uses them to establish a con-
nection to the agent.
add a comment |
To authenticate an ssh client to a server using publickey, you generate a keypair on the client, keep the privatekey on the client, and copy the publickey to your
authorized_keys
file on the server which must be in~/.ssh
owned by you and have permissions only for owner (usually 600 akarw-------
). You did not do the second part. If it's too complicated for you, many systems have a scriptssh-copy-id
which does it for you with a good deal of handholding and error checking.You don't need
ssh-agent
because your keyfile is in the default location and has no password.To use
ssh-agent
you must either run a new process underssh-agent
, such as new shell or a new terminal (inherently with a new shell) that has environment variables set to access the agent process or have your shelleval
the output fromssh-agent
so those environment variables are set in your shell. You did not do either. From the man page:
There are two main ways to get an agent set up: The first is that the
agent starts a new subcommand into which some environment variables are
exported, eg ssh-agent xterm &. The second is that the agent prints the
needed shell commands (either sh(1) or csh(1) syntax can be generated)
which can be evaluated in the calling shell, eg eval 'ssh-agent -s' for
Bourne-type shells such as sh(1) or ksh(1) and eval 'ssh-agent -c' for
csh(1) and derivatives.
Later ssh(1) looks at these variables and uses them to establish a con-
nection to the agent.
To authenticate an ssh client to a server using publickey, you generate a keypair on the client, keep the privatekey on the client, and copy the publickey to your
authorized_keys
file on the server which must be in~/.ssh
owned by you and have permissions only for owner (usually 600 akarw-------
). You did not do the second part. If it's too complicated for you, many systems have a scriptssh-copy-id
which does it for you with a good deal of handholding and error checking.You don't need
ssh-agent
because your keyfile is in the default location and has no password.To use
ssh-agent
you must either run a new process underssh-agent
, such as new shell or a new terminal (inherently with a new shell) that has environment variables set to access the agent process or have your shelleval
the output fromssh-agent
so those environment variables are set in your shell. You did not do either. From the man page:
There are two main ways to get an agent set up: The first is that the
agent starts a new subcommand into which some environment variables are
exported, eg ssh-agent xterm &. The second is that the agent prints the
needed shell commands (either sh(1) or csh(1) syntax can be generated)
which can be evaluated in the calling shell, eg eval 'ssh-agent -s' for
Bourne-type shells such as sh(1) or ksh(1) and eval 'ssh-agent -c' for
csh(1) and derivatives.
Later ssh(1) looks at these variables and uses them to establish a con-
nection to the agent.
edited Nov 21 '17 at 14:34
Iulian Onofrei
1034
1034
answered Nov 18 '15 at 4:58
dave_thompson_085dave_thompson_085
2,14711111
2,14711111
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%2f243728%2fwhy-cant-i-authenticate-to-github%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
I can't see a question here. Did you upload your public key to github via their webinterface?
– sebix
Nov 22 '15 at 18:06
@sebix, yes. It didn't work.
– user109285
Nov 22 '15 at 18:14