[Solved] SSH public key not accepted, by any server

blackout23 · 2015-12-16 15:20:08

Hello,

I have two PCs A and B and a small homeserver C, which is running sshd. I configured sshd on C in a way that it only allows access with the right publickey.
On A I created a key pair and transferred the ID with ssh-copy-id (before disallowing password based auth). On A I can now just ssh into C without getting prompted for A password.
I also created a key pair on B and transferred the Public ID to C, via password based authentication. When I try to ssh from B to C (now only checking publickey) the permission is denied.
ssh from A to C still works and when I check "~/.ssh/authorized_key" on C the keys are the same that I find in ~/.ssh/id_rsa.pub on A and B.

On my Github Account I also added the publickey of A and B, but when I clone a repo on B via ssh I also get "Permission denied (publickey)." I deleted ~/.ssh on B a number of times and
regenerated the key pair and reinstalled openssh altogether, but nothing is working.

Is there some other directory where B could be holding an old public key?

Regards,

blackout24

Last edited by blackout23 (2015-12-16 16:54:04)

ayekat · 2015-12-16 15:25:53

What are the file permissions on ~/.ssh/id_rsa?

ewaller · 2015-12-16 15:32:57

What type of key are you generating on B? sshd has recently dropped default support for some less secure algorithms.
Are A and B the same OS?

What is the output when you try to connect from B to C using ssh -vv yourUserName@hostNameOfMachineC ?

blackout23 · 2015-12-16 15:54:15

ewaller wrote:

What type of key are you generating on B? sshd has recently dropped default support for some less secure algorithms.
Are A and B the same OS?
What is the output when you try to connect from B to C using ssh -vv yourUserName@hostNameOfMachineC ?

A and B are both running Arch Linux which is up-to-date. C is running Arch Linux ARM, but the problem seems to be B anyway otherwise Github would work.

Keys on A and B were created with the default settings of openssh that currently ships with Arch.

OpenSSH_7.1p1, OpenSSL 1.0.2e 3 Dec 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to <IP> [<IP>] port <portnumber>.
debug1: Connection established.
debug1: identity file /home/tim/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.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 OpenSSH_7.1
debug1: match: OpenSSH_7.1 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to <IP>:<Port> as '<username>'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
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: ecdsa-sha2-nistp256 SHA256:ufzWb0sXaffDpeDiG+57e161H9ipAwAXTxPhZitWvOg
debug1: checking without port identifier
debug1: Host '192.168.0.104' is known and matches the ECDSA host key.
debug1: Found key in /home/tim/.ssh/known_hosts:1
debug1: found matching key w/out port
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/tim/.ssh/id_rsa (0x5579394aa170),
debug2: key: /home/tim/.ssh/id_dsa ((nil)),
debug2: key: /home/tim/.ssh/id_ecdsa ((nil)),
debug2: key: /home/tim/.ssh/id_ed25519 ((nil)),
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/tim/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug2: input_userauth_pk_ok: fp SHA256:X50X6HHhsymmKUGPH3UgR1KAAGd0hNvmjnsaXmwYi3o
debug1: Trying private key: /home/tim/.ssh/id_dsa
debug1: Trying private key: /home/tim/.ssh/id_ecdsa
debug1: Trying private key: /home/tim/.ssh/id_ed25519
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).

This line seems strange;
debug1: identity file /home/tim/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory

The file is there and owned by me.
-rw------- 1 tim tim 1766 16. Dez 15:20 /home/tim/.ssh/id_rsa
Same as the public key.
-rw-r--r-- 1 tim tim 395 16. Dez 15:20 /home/tim/.ssh/id_rsa.pub

On A I'm running MATE with LXDM on B I'm running GNOME with GDM doing autologin. I unlock the keyring manually when B boots to the desktop and prompts me for the keyring password.
When I set the password for the SSH key pair on B I told it not to remember it. So if it needed the passphrase to unlock my private key on B it would ask me for it, right? On A it might be saved in the keyring.

I tried deleting the known_hosts file on B and C so that everything sould be like new but that also didn't work.

Last edited by blackout23 (2015-12-16 16:01:30)

ewaller · 2015-12-16 16:15:30

That it cannot see the file is, I think, the root of your problem.
As a sanity check, you are tim on both systems, right?
Are the UIDs for tim the same on both systems? How about A?

blackout23 · 2015-12-16 16:20:20

ewaller wrote:

That it cannot see the file is, I think, the root of your problem.
As a sanity check, you are tim on both systems, right?
Are the UIDs for tim the same on both systems? How about A?

Yes "tim" is the only user on A and B that I created myself and login. The UID on both is 1000.
On C I disabled root login and only have one user called "odroid" with UID 1000 that I login as via SSH.

So the situation on A and B should be exactly the same and the permission of id_rsa and id_rsa in ~/.ssh are the same on A and B.
The hostname of A and B is different.

Here is the verbose output of loggin in from A to C. It also has the file not found message at the top of the log so it can't be that.

OpenSSH_7.1p1, OpenSSL 1.0.2e 3 Dec 2015
debug1: Reading configuration data /etc/ssh/ssh_config
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.0.104 [192.168.0.104] port 2242.
debug1: Connection established.
debug1: identity file /home/tim/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/tim/.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 OpenSSH_7.1
debug1: match: OpenSSH_7.1 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 192.168.0.104:2242 as 'odroid'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519,ssh-rsa
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1,hmac-md5-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
debug2: kex_parse_kexinit: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: kex_parse_kexinit: ssh-rsa,ecdsa-sha2-nistp256,ssh-ed25519
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: kex_parse_kexinit: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: none,zlib@openssh.com
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: 
debug2: kex_parse_kexinit: first_kex_follows 0 
debug2: kex_parse_kexinit: reserved 0 
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: ecdsa-sha2-nistp256 SHA256:ufzWb0sXaffDpeDiG+57e161H9ipAwAXTxPhZitWvOg
debug1: checking without port identifier
debug1: Host '192.168.0.104' is known and matches the ECDSA host key.
debug1: Found key in /home/tim/.ssh/known_hosts:3
debug1: found matching key w/out port
debug2: set_newkeys: mode 1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /home/tim/.ssh/id_rsa (0x559eb81e3bb0),
debug2: key: /home/tim/.ssh/id_dsa ((nil)),
debug2: key: /home/tim/.ssh/id_ecdsa ((nil)),
debug2: key: /home/tim/.ssh/id_ed25519 ((nil)),
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/tim/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug2: input_userauth_pk_ok: fp SHA256:RPimYV5aVxjfomSWa16kITroP0PqjzWaNxAgWKMLgpo
debug1: Authentication succeeded (publickey).
Authenticated to 192.168.0.104 ([192.168.0.104]:2242).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug2: callback start
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Last login: Wed Dec 16 16:57:20 2015 from 192.168.0.101

It even sends the RSA Public key when logging in from A and B and accepts it, but only A somehow gets authorized in the end.

debug1: Offering RSA public key: /home/tim/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg ssh-rsa blen 279

This is the same in both logs.

Last edited by blackout23 (2015-12-16 16:29:38)

ewaller · 2015-12-16 16:39:58

In the first output from B, had you obfuscated this line?

debug1: Authenticating to <IP>:<Port> as '<username>'

Because that same line in the output from A authenticated with a real user name and a local IP address.

I also see that both A and B are actually picking up an rsa key

debug2: key: /home/tim/.ssh/id_rsa (0x5579394aa170),

debug2: key: /home/tim/.ssh/id_rsa (0x559eb81e3bb0),

I think the missing file message was a red herring

blackout23 · 2015-12-16 16:42:17

ewaller wrote:

In the first output from B, had you obfuscated this line?
debug1: Authenticating to <IP>:<Port> as '<username>'
Because that same line in the output from A authenticated with a real user name and a local IP address.
I also see that both A and B are actually picking up an rsa key
debug2: key: /home/tim/.ssh/id_rsa (0x5579394aa170),
debug2: key: /home/tim/.ssh/id_rsa (0x559eb81e3bb0),
I think the missing file message was a red herring

Yes I obfuscated it in the first log, but the server should only be reachable from my local LAN anyway.

ewaller · 2015-12-16 16:48:26

I am running out of ideas. What if you try it from both machines when logged in from a console without Xorg/Gnome/MATE/LXDM ?

blackout23 · 2015-12-16 16:51:57

Well I just made a new key pair on B, again, set GDM to not autologin, renabled password login on C temporarily so I could transfer the ID, rebooted B and tried to ssh from B to C. Now I was prompted to unlock tim@<hostenameOfB>. I entered the passphrase I set and tada!. It works! Why didn't it ask me for my passphrase for the private key on B before, if it needed it, or if I entered it wrong at some point (which I doubt).

Last edited by blackout23 (2015-12-16 16:58:31)

frostschutz · 2015-12-16 16:52:17

ssh is very peculiar about permissions and ownerships, not only of the id_* files but also .ssh dir itself, both server and client side.

Last edited by frostschutz (2015-12-16 16:52:35)

Arch Linux

#1 2015-12-16 15:20:08

[Solved] SSH public key not accepted, by any server

#2 2015-12-16 15:25:53

Re: [Solved] SSH public key not accepted, by any server

#3 2015-12-16 15:32:57

Re: [Solved] SSH public key not accepted, by any server

#4 2015-12-16 15:54:15

Re: [Solved] SSH public key not accepted, by any server

#5 2015-12-16 16:15:30

Re: [Solved] SSH public key not accepted, by any server

#6 2015-12-16 16:20:20

Re: [Solved] SSH public key not accepted, by any server

#7 2015-12-16 16:39:58

Re: [Solved] SSH public key not accepted, by any server

#8 2015-12-16 16:42:17

Re: [Solved] SSH public key not accepted, by any server

#9 2015-12-16 16:48:26

Re: [Solved] SSH public key not accepted, by any server

#10 2015-12-16 16:51:57

Re: [Solved] SSH public key not accepted, by any server

#11 2015-12-16 16:52:17

Re: [Solved] SSH public key not accepted, by any server

Board footer