Re: How to pass in a password to the ssh command line client?
Fraser,
thanks very much for your help.
It is still not working though ;-( I ran ssh in verbose mode... Maybe
that gives insights? Not to me.
Anyway, I can always fall back to start the eclipse ide in the
foreground and enter the password on the command line ;-(
Cheers,
Mariano
mkamp@hamlet:~$ ssh -v mkamp@ejbbuilder.sourceforge.net
OpenSSH_3.5p1 Debian 1:3.5p1-2, SSH protocols 1.5/2.0, OpenSSL
0x0090607f
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Rhosts Authentication disabled, originating port will not be
trusted.
debug1: ssh_connect: needpriv 0
debug1: Connecting to ejbbuilder.sourceforge.net [66.35.250.209] port
22.
debug1: Connection established.
debug1: identity file /home/mkamp/.ssh/identity type -1
debug1: identity file /home/mkamp/.ssh/id_rsa type 1
debug1: identity file /home/mkamp/.ssh/id_dsa type -1
debug1: Remote protocol version 1.99, remote software version
OpenSSH_3.1p1
debug1: match: OpenSSH_3.1p1 pat OpenSSH_2.*,OpenSSH_3.0*,OpenSSH_3.1*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_3.5p1 Debian 1:3.5p1-2
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: 137/256
debug1: bits set: 1623/3191
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'ejbbuilder.sourceforge.net' is known and matches the DSA
host key.
debug1: Found key in /home/mkamp/.ssh/known_hosts:1
debug1: bits set: 1652/3191
debug1: ssh_dss_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/mkamp/.ssh/identity
debug1: try pubkey: /home/mkamp/.ssh/id_rsa
debug1: authentications that can continue:
publickey,password,keyboard-interactive
debug1: try privkey: /home/mkamp/.ssh/id_dsa
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
mkamp@ejbbuilder.sourceforge.net's password:
n Wed, 2002-12-25 at 20:58, Fraser Campbell wrote:
> On December 25, 2002 02:36 pm, the fabulous Mariano Kamp wrote:
>
> > I am not too much into ssh. How would it be possible to use an ssh
> > key? I just have control over the client side. The server side is
> > sourceforge.net.
>
> Ah, well I don't know much about sourceforge but this should work:
>
> - create an ssh2 rsa key on your own computer ...
>
> ssh-keygen -t rsa -C sourgeforge
>
> - this should create two files for you, they will be ...
>
> ~/.ssh/id_rsa
> ~/.ssh/id_rsa.pub
>
> - copy the public key (id_rsa.pub) to ~/.ssh/authorized_keys on the
> sourceforge server. You can do this with scp ...
>
> scp ~/.ssh/id_rsa.pub username@sourceforge.server:.ssh/authorized_keys
>
> - make sure that ~/.ssh/ on the server is mode 755
>
> - make sure that ~/.ssh/authorized_keys on the server is mode 644 or 444
>
> If you've done all of the above correctly then you should be able to ssh in
> without a password or passphrase prompt. Look at the manpages for sshd, it
> documents the authorized_keys stuff. You can do neat things like
> automatically executing commands on login based on what you put in your
> authorized_keys file.
>
> Good luck.
>
> Fraser
>
Reply to: