the name of a popular SSH and Telnet client.
PuTTY the Telnet, rlogin, and SSH client itself, which can also connect to a serial port PSCP an SCP client, i.e.
PuTTY development began late in 1998, and was a usable SSH-2 client by October 2000. PuTTY does not support session tabs directly, but many wrappers are available that do. PuTTY comes bundled with command-line SCP and SFTP clients, called "pscp" and "psftp" respectively, and plink, a command-line connection tool, used for non-interactive sessions. It can also be used with local serial port connections. The network communication layer supports IPv6, and the SSH protocol supports the delayed compression scheme. It also can emulate control sequences from xterm, VT220, VT102 or ECMA-48 terminal emulation, and allows local, remote, or dynamic port forwarding with SSH (including X11 forwarding). PuTTY supports SSO through GSSAPI, including user provided GSSAPI DLLs. PuTTY uses its own format of key files – PPK (protected by Message Authentication Code). One last thing, I've checked and double-checked the file and foler permissions and they're all ok.PuTTY supports many variations on the secure remote terminal, and provides user control over the SSH encryption key and protocol version, alternate ciphers such as AES, 3DES, RC4, Blowfish, DES, and Public-key authentication. It seems like the program is trying to open the authorized_keys file with permissions from the owner, but then there is no more information on what is generating the problem.
Connection from 192.168.0.101 port 4288ĭebug1: Client protocol version 2.0 client software version OpenSSH_4.5ĭebug1: Enabling compatibility mode for protocol 2.0ĭebug1: Local version string SSH-2.0-OpenSSH_4.5ĭebug1: list_hostkey_types: ssh-rsa,ssh-dssĭebug1: kex: client->server aes128-cbc hmac-md5 noneĭebug1: kex: server->client aes128-cbc hmac-md5 noneĭebug1: SSH2_MSG_KEX_DH_GEX_REQUEST receivedĭebug1: expecting SSH2_MSG_KEX_DH_GEX_INITĭebug1: userauth-request for user dcowsill service ssh-connection method noneĭebug1: userauth-request for user dcowsill service ssh-connection method publickeyĭebug1: test whether pkalg/pkblob are acceptableĭebug1: PAM: setting PAM_RHOST to "192.168.0.101"ĭebug1: temporarily_use_uid: 1052/105 (e=0/0)ĭebug1: trying public key file /testuser/.ssh/authorized_keysįailed publickey for dcowsill from 192.168.0.101 port 4288 ssh2 I've done some teting with the ssh server's LogLevel set o VERBOSE but I could'nt retrieve the information (liability issues), so instead here goes an output/debug log from another source which seems to be displaying the same error.
ssh directory ( /user/.ssh/) besides having it in root's folder (doesn't make much sense because of the value of AuthorizedKeysFile in sshd_config). I was also considering the possibility that I need to have the public key inserted in the authorized_keys file inside the user's.
It seems like this might actually be a problem related to ssh versions or something of the sorts. I'm planning to do more testing and setting the logLevel value to VERBOSE or DEBUG2 or 3 but considering the urgency of the matter and the fact that in order to actually test it on the machine I have to go through a lot of hassle considering the machine is in a place that is quite distant from my actual workplace. The logs don't show any authentication problems. The error "Server refused our key" keeps showing up, no matter what I do. The config file ( sshd_config) has the AuthorizedKeysFile set to ~/.sshd/authorized_keys. There are no connectivity issues AFAICS and the same goes for ssh, considering I'm able to log in as root to the Linux machine.
This seems pretty straightforward considering that it worked in 2 other windows machines to a different Linux machine, with the same configuration. I was trying to set up a simple backup script to run automatically that would copy a file from a Windows machine to a Linux one through SSH.Īs a lot of simple online tutorials suggest I used pscp with a private key generated with puttygen and placed the corresponding public key (presented in copy/paste form by putty itself) in the authorized_keys file in Linux.