Re: Allways prompted for a password

From: Alexander von Alkier (alexander.von-alkier@dregis.com)
Date: 08/26/02


From: "Alexander von Alkier" <alexander.von-alkier@dregis.com>
Date: Mon, 26 Aug 2002 10:27:12 +0200


"David Pollard" <headly81@hotmail.com> schrieb im Newsbeitrag
news:70ee45fd.0208252218.60c2eccc@posting.google.com...
> Hi There,
> I'm trying to automate my ssh connection eventually for use with cvs
> but I can't even get command line stuff to work. My server is Red Hat
> Linux 7.3
>
> I have followed all manner of readme's and found lots of posts with
> similar problems but have not been able to sort it out.
>
> Here is the output from a ssh -v -l username servername from my cygwin
> copy of ssh. I have also tried the windows client from ssh.com and
> they all do pretty much the same thing. I am a little confused by all
> the different versions of servers and clients around and all the
> different encryptions methods available.
>
> My goal is to make secure cvs connections from windows(2000), linux
> and Mac osx to my linux server.
>
> C:\cygwin\home\Administrator>ssh -v -l pollardd linuxdev
> OpenSSH_2.9p2, SSH protocols 1.5/2.0, OpenSSL 0x0090600f
> debug1: Seeding random number generator
> debug1: Rhosts Authentication disabled, originating port will not be
> trusted.
> debug1: restore_uid
> debug1: ssh_connect: getuid 500 geteuid 500 anon 1
> debug1: Connecting to linuxdev [10.0.0.6] port 22.
> debug1: temporarily_use_uid: 500/513 (e=500)
> debug1: restore_uid
> debug1: temporarily_use_uid: 500/513 (e=500)
> debug1: restore_uid
> debug1: Connection established.
> debug1: identity file /home/Administrator/.ssh/identity type 0
> debug1: identity file /home/Administrator/.ssh/id_rsa type 1
> debug1: identity file /home/Administrator/.ssh/id_dsa type -1
> debug1: Remote protocol version 1.99, remote software version
> OpenSSH_3.1p1
> debug1: match: OpenSSH_3.1p1 pat ^OpenSSH
> Enabling compatibility mode for protocol 2.0
> debug1: Local version string SSH-2.0-OpenSSH_2.9p2
> 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: 124/256
> debug1: bits set: 1558/3191
> debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
> debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
> debug1: Host 'linuxdev' is known and matches the RSA host key.
> debug1: Found key in /home/Administrator/.ssh/known_hosts2:2
> debug1: bits set: 1638/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-interacti
> ve
> debug1: next auth method to try is publickey
> debug1: try pubkey: /home/Administrator/.ssh/id_rsa
> debug1: authentications that can continue:
> publickey,password,keyboard-interacti
> ve
> debug1: try privkey: /home/Administrator/.ssh/id_dsa
> debug1: next auth method to try is password
> pollardd@linuxdev's password:

on the machine running SSH server you have to allow publickey authorization
in /etc/ssh2/sshd_config (???).
further you have to save the public key on this server in the home directory
of user "poollardd" and create a file called "authorization".
on client side tell the client to use public key authorization. create a
file called "identity" or "identification" that refers to your private key.
check if the public is the correct one. (it must be the one, created on your
client)

use "man ssh" to get correct syntax of your ssh version.

alexander



Relevant Pages

  • RE: RE : RE : X11Forwarding problem on Solaris.
    ... The program is using the display environment variable. ... First i use ssh to connect from node2 to node4 and then I start the PROGRAM ... debug1: Connection established. ... Subject: RE: RE: X11Forwarding problem on Solaris. ...
    (SSH)
  • ssh connect problems (ubuntu feisty client, ubuntu dapper server)
    ... After feisty-upgrade the ssh connect to a dapper server is becoming ... Connection to server closed. ... debug1: Connecting to server port 22. ... debug2: fd 3 setting O_NONBLOCK ...
    (SSH)
  • Re: Using/Configuring SSH on Solaris 9 08/03
    ... >>Is there someplace where I can find info on getting SSH to work on a Solaris ... debug1: sshd version Sun_SSH_1.0 ... debug1: load_private_key_autodetect: type 2 DSA ... Server listening on:: port 22. ...
    (comp.unix.solaris)
  • Login and ssh hang after password, before logging
    ... I have a nice new server, ... I was able to log in through the console and ssh fine ... results for password authentication and public-key authentication: ... debug1: read PEM private key done: type DSA ...
    (alt.linux)
  • Update: Unable to login without password using ssh
    ... The permission on the .ssh directory was following ... I have other servers which are working. ... debug1: Rhosts Authentication disabled, originating port will not be trusted. ... debug1: sent kexinit: none ...
    (SunManagers)