Skip to main content
added 18 characters in body
Source Link
Woodrow Barlow
  • 203
  • 1
  • 2
  • 18

I found my /etc/ssh/sshd_config file on the ftp-server. I won't post the whole thing, but it does have the following lines:

I found my /etc/ssh/sshd_config file. I won't post the whole thing, but it does have the following lines:

I found my /etc/ssh/sshd_config file on the ftp-server. I won't post the whole thing, but it does have the following lines:

added 2526 characters in body
Source Link
Woodrow Barlow
  • 203
  • 1
  • 2
  • 18
 

Below is the output of theI found my /etc/ssh -v/sshd_config commandfile. I won't post the whole thing, but it does have the following lines:

OpenSSH_5RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

As far as I can tell from the documentation, I think these lines are set correctly for what I want to do (s/key is something unrelated to ssh keypairs, right?).


Below is the verbose output while connecting.

[wbarlow@build-machine]:~$ ssh -v wbarlow@ftp-server
OpenSSH_6.1p1 Debian-4, OpenSSL 01.90.8g1c 1910 OctMay 20072012
usagedebug1: Reading configuration data /etc/ssh/ssh_config
debug1: [/etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ftp-1246AaCfgKkMNnqsTtVvXxY]server [-b(ip bind_address]hidden)] [-cport cipher_spec]22.
debug1: Connection established.
debug1: identity file /home/wbarlow/.ssh/id_rsa type 1
debug1: Checking blacklist file [/usr/share/ssh/blacklist.RSA-D [bind_address2048
debug1:]port] [Checking blacklist file /etc/ssh/blacklist.RSA-e2048
debug1: escape_char]identity [file /home/wbarlow/.ssh/id_rsa-Fcert configfile]type -1
debug1: identity file /home/wbarlow/.ssh/id_dsa type -1
debug1: identity file /home/wbarlow/.ssh/id_dsa-cert type -1
debug1: [identity file /home/wbarlow/.ssh/id_ecdsa type -i1
debug1: identity_file]identity [file /home/wbarlow/.ssh/id_ecdsa-Lcert [bind_addresstype -1
debug1:]port Remote protocol version 2.0, remote software version OpenSSH_5.1
debug1:host match:hostport] OpenSSH_5.1 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.1p1 [Debian-l4
debug1: login_name]SSH2_MSG_KEXINIT [sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server-m>client mac_spec]aes128-ctr [hmac-Omd5 ctl_cmd]none
debug1: [kex: client-o>server option]aes128-ctr [hmac-pmd5 port]none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host [key: RSA [SNIP]
debug1: Host 'ftp-Rserver' [bind_addressis known and matches the RSA host key.
debug1:]port Found key in /home/wbarlow/.ssh/known_hosts:host1
debug1:hostport] [-Sssh_rsa_verify: ctl_path]signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by [-wserver
debug1: local_tun[SSH2_MSG_SERVICE_REQUEST sent
debug1:remote_tun]] [user@]hostnameSSH2_MSG_SERVICE_ACCEPT [command]received

I found my /etc/ssh/sshd_config file. I won't post the whole thing, but it does have the following lines:

RSAAuthenticationdebug1: yesAuthentications that can continue: publickey,gssapi-with-mic,password
PubkeyAuthenticationdebug1: yesNext authentication method: gssapi-with-mic
AuthorizedKeysFiledebug1: Unspecified GSS failure.  Minor code may provide more information
Cannot determine realm for numeric host address

debug1: Unspecified GSS failure.ssh/authorized_keys  Minor code may provide more information
Cannot determine realm for numeric host address
#
debug1: ToUnspecified disableGSS tunneledfailure. clear textMinor passwords,code changemay toprovide nomore here!information
#PasswordAuthentication

debug1: yesUnspecified GSS failure.  Minor code may provide more information
#PermitEmptyPasswordsCannot nodetermine realm for numeric host address
PasswordAuthentication
debug1: yesNext authentication method: publickey
debug1: Offering RSA public key: /home/wbarlow/.ssh/id_rsa
#debug1: ChangeAuthentications tothat nocan tocontinue: disablepublickey,gssapi-with-mic,password
debug1: sTrying private key: /home/wbarlow/.ssh/id_dsa
debug1: Trying private key: passwords/home/wbarlow/.ssh/id_ecdsa
#ChallengeResponseAuthenticationdebug1: yesNext authentication method: password
ChallengeResponseAuthenticationwbarlow@ftp-server's nopassword: 

As far as I can tell from the documentation, I think these lines are set correctly for what I want to do (s/key is something unrelated to ssh keypairs, right?).

Below is the output of the ssh -v command.

OpenSSH_5.1p1, OpenSSL 0.9.8g 19 Oct 2007
usage: ssh [-1246AaCfgKkMNnqsTtVvXxY] [-b bind_address] [-c cipher_spec]
           [-D [bind_address:]port] [-e escape_char] [-F configfile]
           [-i identity_file] [-L [bind_address:]port:host:hostport]
           [-l login_name] [-m mac_spec] [-O ctl_cmd] [-o option] [-p port]
           [-R [bind_address:]port:host:hostport] [-S ctl_path]
           [-w local_tun[:remote_tun]] [user@]hostname [command]

I found my /etc/ssh/sshd_config file. I won't post the whole thing, but it does have the following lines:

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

As far as I can tell from the documentation, I think these lines are set correctly for what I want to do (s/key is something unrelated to ssh keypairs, right?).

 

I found my /etc/ssh/sshd_config file. I won't post the whole thing, but it does have the following lines:

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

As far as I can tell from the documentation, I think these lines are set correctly for what I want to do (s/key is something unrelated to ssh keypairs, right?).


Below is the verbose output while connecting.

[wbarlow@build-machine]:~$ ssh -v wbarlow@ftp-server
OpenSSH_6.1p1 Debian-4, OpenSSL 1.0.1c 10 May 2012
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug1: Connecting to ftp-server [(ip hidden)] port 22.
debug1: Connection established.
debug1: identity file /home/wbarlow/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: identity file /home/wbarlow/.ssh/id_rsa-cert type -1
debug1: identity file /home/wbarlow/.ssh/id_dsa type -1
debug1: identity file /home/wbarlow/.ssh/id_dsa-cert type -1
debug1: identity file /home/wbarlow/.ssh/id_ecdsa type -1
debug1: identity file /home/wbarlow/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.1
debug1: match: OpenSSH_5.1 pat OpenSSH_5*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.1p1 Debian-4
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA [SNIP]
debug1: Host 'ftp-server' is known and matches the RSA host key.
debug1: Found key in /home/wbarlow/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
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,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
Cannot determine realm for numeric host address

debug1: Unspecified GSS failure.  Minor code may provide more information
Cannot determine realm for numeric host address

debug1: Unspecified GSS failure.  Minor code may provide more information


debug1: Unspecified GSS failure.  Minor code may provide more information
Cannot determine realm for numeric host address

debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/wbarlow/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug1: Trying private key: /home/wbarlow/.ssh/id_dsa
debug1: Trying private key: /home/wbarlow/.ssh/id_ecdsa
debug1: Next authentication method: password
wbarlow@ftp-server's password: 
added 162 characters in body
Source Link
Woodrow Barlow
  • 203
  • 1
  • 2
  • 18

I am able to use the public key to authenticate with other machines (namely, my Git repository host), so I don't think that the problem is on the client-side.

So -- how can I check that the FTP server is configured to accept authorized keys, and what sort of keys is it configured to accept? How can I check that the keys are being stored in the expected place (my home directory on ftp-server is /var/ftp/wbarlow/, but I've also tried copying the .ssh folder from there to /home/wbarlow/.)?

So -- how can I check that the FTP server is configured to accept authorized keys, and what sort of keys is it configured to accept? How can I check that the keys are being stored in the expected place (my home directory on ftp-server is /var/ftp/wbarlow/, but I've also tried copying the .ssh folder from there to /home/wbarlow/.)?

I am able to use the public key to authenticate with other machines (namely, my Git repository host), so I don't think that the problem is on the client-side.

So -- how can I check that the FTP server is configured to accept authorized keys, and what sort of keys is it configured to accept? How can I check that the keys are being stored in the expected place (my home directory on ftp-server is /var/ftp/wbarlow/, but I've also tried copying the .ssh folder from there to /home/wbarlow/.)?

added 765 characters in body
Source Link
Woodrow Barlow
  • 203
  • 1
  • 2
  • 18
Loading
deleted 128 characters in body
Source Link
Woodrow Barlow
  • 203
  • 1
  • 2
  • 18
Loading
added 754 characters in body
Source Link
Woodrow Barlow
  • 203
  • 1
  • 2
  • 18
Loading
Source Link
Woodrow Barlow
  • 203
  • 1
  • 2
  • 18
Loading