Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
problems getting fcp not to ask for password
#1

I followed the instructions here on how to set everything up:

[/url][url=http://www.siliconvalleyccie.com/linux-hn/...tm#_Toc91603056]http://www.siliconvalleyccie.com/linux-hn/...tm#_Toc91603056

 

However, whenever I fcp I'm still prompted for a password. Here is the debug log file for fcp, I can't see anything obviously wrong in it:

 

[deployer@stage3 rob_test]$ scp -r -v rules/40/*

buildscript@xxx.yyy.com:rules/40

Executing: program /usr/bin/ssh host xxx.yyy.com, user buildscript, command

scp -v -r -d -t rules/40

OpenSSH_3.5p1, SSH protocols 1.5/2.0, OpenSSL 0x0090701f

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: Applying options for *

debug1: Rhosts Authentication disabled, originating port will not be

trusted.

debug1: ssh_connect: needpriv 0

debug1: Connecting to xxx.yyy.com [10.1.1.153] port 22.

debug1: Connection established.

debug1: identity file /home/deployer/.ssh/identity type -1

debug1: identity file /home/deployer/.ssh/id_rsa type 1

debug1: identity file /home/deployer/.ssh/id_dsa type 2

debug1: Remote protocol version 1.99, remote software version

OpenSSH_3.6.1p2

debug1: match: OpenSSH_3.6.1p2 pat OpenSSH*

debug1: Enabling compatibility mode for protocol 2.0

debug1: Local version string SSH-2.0-OpenSSH_3.5p1

debug1: SSH2_MSG_KEXINIT sent

debug1: SSH2_MSG_KEXINIT received

debug1: kex: server->client aes128-cbc hmac-md5 none

debug1: kex: client->server aes128-cbc hmac-md5 none

debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP

debug1: dh_gen_key: priv key bits set: 108/256

debug1: bits set: 1631/3191

debug1: SSH2_MSG_KEX_DH_GEX_INIT sent

debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY

debug1: Host 'xxx.yyy.com' is known and matches the RSA host key.

debug1: Found key in /home/deployer/.ssh/known_hosts:2

debug1: bits set: 1562/3191

debug1: ssh_rsa_verify: signature correct

debug1: kex_derive_keys

debug1: newkeys: mode 1

debug1: SSH2_MSG_NEWKEYS sent

debug1: waiting for SSH2_MSG_NEWKEYS

debug1: newkeys: mode 0

debug1: SSH2_MSG_NEWKEYS received

debug1: done: ssh_kex2.

debug1: send SSH2_MSG_SERVICE_REQUEST

debug1: service_accept: ssh-userauth

debug1: got SSH2_MSG_SERVICE_ACCEPT

debug1: authentications that can continue:

publickey,password,keyboard-interactive

debug1: next auth method to try is publickey

debug1: try privkey: /home/deployer/.ssh/identity

debug1: try pubkey: /home/deployer/.ssh/id_rsa

debug1: authentications that can continue:

publickey,password,keyboard-interactive

debug1: try pubkey: /home/deployer/.ssh/id_dsa

debug1: authentications that can continue:

publickey,password,keyboard-interactive

debug1: next auth method to try is keyboard-interactive

debug1: authentications that can continue:

publickey,password,keyboard-interactive

debug1: next auth method to try is password

buildscript@xxx.yyy.com's password:

Reply
#2

on the server try this

 

chmod 700 ~/.ssh

chmod 600 ~/.ssh/authorized_keys

 

If the permissions are off it won't allow connections

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)