why I am still asked to input password after all the setup? - SSH

This is a discussion on why I am still asked to input password after all the setup? - SSH ; Hi, I have cygwin installed on my PC and trying to ssh to my linux machine. I follow the instructions to create DSA keys, copy id_dsa.pub to authorized_keys on linux machine ~/.ssh directory. Now I run ssh, I am still ...

+ Reply to Thread
Results 1 to 12 of 12

Thread: why I am still asked to input password after all the setup?

  1. why I am still asked to input password after all the setup?

    Hi,
    I have cygwin installed on my PC and trying to ssh to my linux
    machine.

    I follow the instructions to create DSA keys, copy id_dsa.pub to
    authorized_keys on linux machine ~/.ssh directory.

    Now I run ssh, I am still asked for password.

    Do you know what might be wrong?

    Thanks.

    One thing I am wondering, in the private key file which is on my
    windows machie, id_dsa, I do not see my user ID and host name. Is this
    correct?


  2. Re: why I am still asked to input password after all the setup?

    Try authorized_keys2.

    --
    jbeasley@sdf.lonestar.org
    SDF Public Access UNIX System - http://sdf.lonestar.org

  3. Re: why I am still asked to input password after all the setup?

    >>>>> "JB" == Joe Beasley writes:

    JB> Try authorized_keys2

    No point; that file has been deprecated and unnecessary for years.

    --
    Richard Silverman
    res@qoxp.net


  4. Re: why I am still asked to input password after all the setup?

    Joe Beasley writes:

    >Try authorized_keys2.


    While that used to be necessary after the change from ssh1 to ssh2, that
    has gone for about 5 years now. authorized_keys should be fine.

    (Of course if he is using openssh 2.0.0 then perhaps your suggestion will
    work)




  5. Re: why I am still asked to input password after all the setup?

    I tried both authorized_keys and authorized_keys2. Neither works for
    me.

    Any other suggestion?

    Joe Beasley wrote:
    > Try authorized_keys2.
    >
    > --
    > jbeasley@sdf.lonestar.org
    > SDF Public Access UNIX System - http://sdf.lonestar.org



  6. Re: why I am still asked to input password after all the setup?

    linq936@hotmail.com writes:
    > I have cygwin installed on my PC and trying to ssh to my linux
    > machine.
    >
    > I follow the instructions to create DSA keys, copy id_dsa.pub to
    > authorized_keys on linux machine ~/.ssh directory.
    >
    > Now I run ssh, I am still asked for password.
    >
    > Do you know what might be wrong?
    >
    > Thanks.
    >
    > One thing I am wondering, in the private key file which is on my
    > windows machie, id_dsa, I do not see my user ID and host name. Is this
    > correct?


    Have you checked the permissions on your ~/.ssh directory and
    ~/.ssh/authorized_keys file? ssh will refuse to use them if their
    premissions are too lax (particularly if anyone other than the owner
    can write to them).

    You can also try "ssh -v", "ssh -vv", or "ssh -vvv" for various levels
    of debugging output.

    --
    Keith Thompson (The_Other_Keith) kst-u@mib.org
    San Diego Supercomputer Center <*>
    We must do something. This is something. Therefore, we must do this.

  7. Re: why I am still asked to input password after all the setup?

    linq936@hotmail.com wrote:
    > Hi,
    > I have cygwin installed on my PC and trying to ssh to my linux
    > machine.
    >
    > I follow the instructions to create DSA keys, copy id_dsa.pub to
    > authorized_keys on linux machine ~/.ssh directory.
    >
    > Now I run ssh, I am still asked for password.
    >
    > Do you know what might be wrong?
    >
    > Thanks.
    >
    > One thing I am wondering, in the private key file which is on my
    > windows machie, id_dsa, I do not see my user ID and host name. Is this
    > correct?
    >


    You are probably being asked for a passphrase. Have you cached your
    private key with ssh-agent or keychain?

  8. Re: why I am still asked to input password after all the setup?


    Chuck wrote:
    > linq936@hotmail.com wrote:
    > > Hi,
    > > I have cygwin installed on my PC and trying to ssh to my linux
    > > machine.
    > >
    > > I follow the instructions to create DSA keys, copy id_dsa.pub to
    > > authorized_keys on linux machine ~/.ssh directory.
    > >
    > > Now I run ssh, I am still asked for password.
    > >
    > > Do you know what might be wrong?
    > >
    > > Thanks.
    > >
    > > One thing I am wondering, in the private key file which is on my
    > > windows machie, id_dsa, I do not see my user ID and host name. Is this
    > > correct?
    > >

    >
    > You are probably being asked for a passphrase. Have you cached your
    > private key with ssh-agent or keychain?

    Could you elabrate on this?

    When I ran ssh-keygen, I was asked about passphrase, I just press
    Enter, I do not input anything.

    I run ssh command with -vvv, and here is the log:


    OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005
    debug1: Reading configuration data /etc/ssh_config
    debug2: ssh_connect: needpriv 0
    debug1: Connecting to xaqtom40 [149.199.109.155] port 22.
    debug1: Connection established.
    debug1: identity file /cygdrive/c/home/tom/.ssh/identity type -1
    debug1: identity file /cygdrive/c/home/tom/.ssh/id_rsa type -1
    debug3: Not a RSA1 key file /cygdrive/c/home/tom/.ssh/id_dsa.
    debug2: key_type_from_name: unknown key type '-----BEGIN'
    debug3: key_read: missing keytype
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug3: key_read: missing whitespace
    debug2: key_type_from_name: unknown key type '-----END'
    debug3: key_read: missing keytype
    debug1: identity file /cygdrive/c/home/tom/.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_3.*
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_4.3
    debug2: fd 3 setting O_NONBLOCK
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug2: kex_parse_kexinit:
    diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
    debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,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:
    diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
    debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
    debug2: kex_parse_kexinit:
    aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit:
    hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit: none,zlib
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit:
    debug2: kex_parse_kexinit: first_kex_follows 0
    debug2: kex_parse_kexinit: reserved 0
    debug2: mac_init: found hmac-md5
    debug1: kex: server->client aes128-cbc hmac-md5 none
    debug2: mac_init: found hmac-md5
    debug1: kex: client->server aes128-cbc hmac-md5 none
    debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    debug2: dh_gen_key: priv key bits set: 125/256
    debug2: bits set: 523/1024
    debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    debug3: check_host_in_hostfile: filename
    /cygdrive/c/home/tom/.ssh/known_hosts
    debug3: check_host_in_hostfile: match line 17
    debug3: check_host_in_hostfile: filename
    /cygdrive/c/home/tom/.ssh/known_hosts
    debug3: check_host_in_hostfile: match line 17
    debug1: Host 'xaqtom40' is known and matches the RSA host key.
    debug1: Found key in /cygdrive/c/home/tom/.ssh/known_hosts:17
    debug2: bits set: 531/1024
    debug1: ssh_rsa_verify: signature correct
    debug2: kex_derive_keys
    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: SSH2_MSG_SERVICE_REQUEST sent
    debug2: service_accept: ssh-userauth
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug2: key: /cygdrive/c/home/tom/.ssh/identity (0x0)
    debug2: key: /cygdrive/c/home/tom/.ssh/id_rsa (0x0)
    debug2: key: /cygdrive/c/home/tom/.ssh/id_dsa (0x1002efb0)
    debug3: input_userauth_banner
    The use of this system is restricted to authorized persons only. All
    others will be prosecuted to the full extent of the law.
    debug1: Authentications that can continue:
    publickey,password,keyboard-interactive
    debug3: start over, passed a different list
    publickey,password,keyboard-interactive
    debug3: preferred publickey,keyboard-interactive,password
    debug3: authmethod_lookup publickey
    debug3: remaining preferred: keyboard-interactive,password
    debug3: authmethod_is_enabled publickey
    debug1: Next authentication method: publickey
    debug1: Trying private key: /cygdrive/c/home/tom/.ssh/identity
    debug3: no such identity: /cygdrive/c/home/tom/.ssh/identity
    debug1: Trying private key: /cygdrive/c/home/tom/.ssh/id_rsa
    debug3: no such identity: /cygdrive/c/home/tom/.ssh/id_rsa
    debug1: Offering public key: /cygdrive/c/home/tom/.ssh/id_dsa
    debug3: send_pubkey_test
    debug2: we sent a publickey packet, wait for reply
    debug1: Authentications that can continue:
    publickey,password,keyboard-interactive
    debug2: we did not send a packet, disable method
    debug3: authmethod_lookup keyboard-interactive
    debug3: remaining preferred: password
    debug3: authmethod_is_enabled keyboard-interactive
    debug1: Next authentication method: keyboard-interactive
    debug2: userauth_kbdint
    debug2: we sent a keyboard-interactive packet, wait for reply
    debug1: Authentications that can continue:
    publickey,password,keyboard-interactive
    debug3: userauth_kbdint: disable: no info_req_seen
    debug2: we did not send a packet, disable method
    debug3: authmethod_lookup password
    debug3: remaining preferred:
    debug3: authmethod_is_enabled password
    debug1: Next authentication method: password


    I do not see anything special except that it mentions this,
    key_type_from_name: unknown key type '-----BEGIN'
    I think that is about the first line in DSA file which is,
    -----BEGIN DSA PRIVATE KEY-----
    I do not know if this is right or wrong.

    Any suggestion?


  9. Re: why I am still asked to input password after all the setup?

    linq936@hotmail.com wrote:
    > Chuck wrote:
    >> linq936@hotmail.com wrote:
    >>> Hi,
    >>> I have cygwin installed on my PC and trying to ssh to my linux
    >>> machine.
    >>>
    >>> I follow the instructions to create DSA keys, copy id_dsa.pub to
    >>> authorized_keys on linux machine ~/.ssh directory.
    >>>
    >>> Now I run ssh, I am still asked for password.
    >>>
    >>> Do you know what might be wrong?
    >>>
    >>> Thanks.
    >>>
    >>> One thing I am wondering, in the private key file which is on my
    >>> windows machie, id_dsa, I do not see my user ID and host name. Is this
    >>> correct?
    >>>

    >> You are probably being asked for a passphrase. Have you cached your
    >> private key with ssh-agent or keychain?

    > Could you elabrate on this?
    >
    > When I ran ssh-keygen, I was asked about passphrase, I just press
    > Enter, I do not input anything.
    >
    > I run ssh command with -vvv, and here is the log:
    >
    >
    > OpenSSH_4.3p2, OpenSSL 0.9.8a 11 Oct 2005
    > debug1: Reading configuration data /etc/ssh_config
    > debug2: ssh_connect: needpriv 0
    > debug1: Connecting to xaqtom40 [149.199.109.155] port 22.
    > debug1: Connection established.
    > debug1: identity file /cygdrive/c/home/tom/.ssh/identity type -1
    > debug1: identity file /cygdrive/c/home/tom/.ssh/id_rsa type -1
    > debug3: Not a RSA1 key file /cygdrive/c/home/tom/.ssh/id_dsa.
    > debug2: key_type_from_name: unknown key type '-----BEGIN'
    > debug3: key_read: missing keytype
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug3: key_read: missing whitespace
    > debug2: key_type_from_name: unknown key type '-----END'
    > debug3: key_read: missing keytype
    > debug1: identity file /cygdrive/c/home/tom/.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_3.*
    > debug1: Enabling compatibility mode for protocol 2.0
    > debug1: Local version string SSH-2.0-OpenSSH_4.3
    > debug2: fd 3 setting O_NONBLOCK
    > debug1: SSH2_MSG_KEXINIT sent
    > debug1: SSH2_MSG_KEXINIT received
    > debug2: kex_parse_kexinit:
    > diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
    > debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    > debug2: kex_parse_kexinit:
    > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    > debug2: kex_parse_kexinit:
    > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,arcfour256,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se,aes128-ctr,aes192-ctr,aes256-ctr
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,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:
    > diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1
    > debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
    > debug2: kex_parse_kexinit:
    > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
    > debug2: kex_parse_kexinit:
    > aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc,rijndael-cbc@lysator.liu.se
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    > debug2: kex_parse_kexinit:
    > hmac-md5,hmac-sha1,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
    > debug2: kex_parse_kexinit: none,zlib
    > debug2: kex_parse_kexinit: none,zlib
    > debug2: kex_parse_kexinit:
    > debug2: kex_parse_kexinit:
    > debug2: kex_parse_kexinit: first_kex_follows 0
    > debug2: kex_parse_kexinit: reserved 0
    > debug2: mac_init: found hmac-md5
    > debug1: kex: server->client aes128-cbc hmac-md5 none
    > debug2: mac_init: found hmac-md5
    > debug1: kex: client->server aes128-cbc hmac-md5 none
    > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
    > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
    > debug2: dh_gen_key: priv key bits set: 125/256
    > debug2: bits set: 523/1024
    > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
    > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
    > debug3: check_host_in_hostfile: filename
    > /cygdrive/c/home/tom/.ssh/known_hosts
    > debug3: check_host_in_hostfile: match line 17
    > debug3: check_host_in_hostfile: filename
    > /cygdrive/c/home/tom/.ssh/known_hosts
    > debug3: check_host_in_hostfile: match line 17
    > debug1: Host 'xaqtom40' is known and matches the RSA host key.
    > debug1: Found key in /cygdrive/c/home/tom/.ssh/known_hosts:17
    > debug2: bits set: 531/1024
    > debug1: ssh_rsa_verify: signature correct
    > debug2: kex_derive_keys
    > 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: SSH2_MSG_SERVICE_REQUEST sent
    > debug2: service_accept: ssh-userauth
    > debug1: SSH2_MSG_SERVICE_ACCEPT received
    > debug2: key: /cygdrive/c/home/tom/.ssh/identity (0x0)
    > debug2: key: /cygdrive/c/home/tom/.ssh/id_rsa (0x0)
    > debug2: key: /cygdrive/c/home/tom/.ssh/id_dsa (0x1002efb0)
    > debug3: input_userauth_banner
    > The use of this system is restricted to authorized persons only. All
    > others will be prosecuted to the full extent of the law.
    > debug1: Authentications that can continue:
    > publickey,password,keyboard-interactive
    > debug3: start over, passed a different list
    > publickey,password,keyboard-interactive
    > debug3: preferred publickey,keyboard-interactive,password
    > debug3: authmethod_lookup publickey
    > debug3: remaining preferred: keyboard-interactive,password
    > debug3: authmethod_is_enabled publickey
    > debug1: Next authentication method: publickey
    > debug1: Trying private key: /cygdrive/c/home/tom/.ssh/identity
    > debug3: no such identity: /cygdrive/c/home/tom/.ssh/identity
    > debug1: Trying private key: /cygdrive/c/home/tom/.ssh/id_rsa
    > debug3: no such identity: /cygdrive/c/home/tom/.ssh/id_rsa
    > debug1: Offering public key: /cygdrive/c/home/tom/.ssh/id_dsa
    > debug3: send_pubkey_test
    > debug2: we sent a publickey packet, wait for reply
    > debug1: Authentications that can continue:
    > publickey,password,keyboard-interactive
    > debug2: we did not send a packet, disable method
    > debug3: authmethod_lookup keyboard-interactive
    > debug3: remaining preferred: password
    > debug3: authmethod_is_enabled keyboard-interactive
    > debug1: Next authentication method: keyboard-interactive
    > debug2: userauth_kbdint
    > debug2: we sent a keyboard-interactive packet, wait for reply
    > debug1: Authentications that can continue:
    > publickey,password,keyboard-interactive
    > debug3: userauth_kbdint: disable: no info_req_seen
    > debug2: we did not send a packet, disable method
    > debug3: authmethod_lookup password
    > debug3: remaining preferred:
    > debug3: authmethod_is_enabled password
    > debug1: Next authentication method: password
    >
    >
    > I do not see anything special except that it mentions this,
    > key_type_from_name: unknown key type '-----BEGIN'
    > I think that is about the first line in DSA file which is,
    > -----BEGIN DSA PRIVATE KEY-----
    > I do not know if this is right or wrong.
    >
    > Any suggestion?
    >


    At this point I'm only guessing.

    1) Make sure the permissions on the authorized_keys file is set to 600.
    2) Make sure it was the public key and not the private key that was
    added to the authorized_keys file. It should be a single line of text
    that may wrap around the window several times.
    2) If #1 or #2 doesn't solve the problem, try using an RSA key instead.

  10. Re: why I am still asked to input password after all the setup?

    Chuck wrote:
    > 1) Make sure the permissions on the authorized_keys file is set to 600.
    > 2) Make sure it was the public key and not the private key that was
    > added to the authorized_keys file. It should be a single line of text
    > that may wrap around the window several times.
    > 2) If #1 or #2 doesn't solve the problem, try using an RSA key

    instead.

    Also the client doesn't get told why the key doesn't work. It can be
    usefult to run the server in debug mode and try the connection.

    --
    Darren Dunham ddunham@taos.com
    Senior Technical Consultant TAOS http://www.taos.com/
    Got some Dr Pepper? San Francisco, CA bay area
    < This line left intentionally blank to confuse you. >

  11. Re: why I am still asked to input password after all the setup?

    This is a good suggestion, but I wonder how to turn on debug on server
    side?

    Another thing is, I do not have administrator access on the server side
    machine, can I turn on the debug?

    Thanks a lot.

    Looking forward to your reply.


    Darren Dunham wrote:
    > Chuck wrote:
    > > 1) Make sure the permissions on the authorized_keys file is set to 600.
    > > 2) Make sure it was the public key and not the private key that was
    > > added to the authorized_keys file. It should be a single line of text
    > > that may wrap around the window several times.
    > > 2) If #1 or #2 doesn't solve the problem, try using an RSA key

    > instead.
    >
    > Also the client doesn't get told why the key doesn't work. It can be
    > usefult to run the server in debug mode and try the connection.
    >
    > --
    > Darren Dunham ddunham@taos.com
    > Senior Technical Consultant TAOS http://www.taos.com/
    > Got some Dr Pepper? San Francisco, CA bay area
    > < This line left intentionally blank to confuse you. >



  12. Re: why I am still asked to input password after all the setup?

    linq936@hotmail.com wrote:
    > This is a good suggestion, but I wonder how to turn on debug on server
    > side?


    On Unix, you add some flags to sshd (-D).

    > Another thing is, I do not have administrator access on the server side
    > machine, can I turn on the debug?


    It depends on specifics. If you bind to a high numbered port (like
    8080) it's possible. Then again, you're not necessarily testing the
    exact same behavior if the servers aren't running as the same account.

    --
    Darren Dunham ddunham@taos.com
    Senior Technical Consultant TAOS http://www.taos.com/
    Got some Dr Pepper? San Francisco, CA bay area
    < This line left intentionally blank to confuse you. >

+ Reply to Thread