How to pass in a password to the ssh command line client?
Mariano Kamp
I am using eclipse (http://eclipse.org) to access a cvs repository by
using ext:. The problem is that it asks for the ssh password on the
command line. Anything I can do to pass it in automatically?
The short help of ssh looks like this:
mkamp@hamlet:~$ ssh
Usage: ssh [options] host [command]
Options:
-l user Log in using this user name.
-n Redirect input from /dev/null.
-F config Config file (default: ~/.ssh/config).
-A Enable authentication agent forwarding.
-a Disable authentication agent forwarding (default).
-X Enable X11 connection forwarding.
-x Disable X11 connection forwarding (default).
-i file Identity for public key authentication (default:
~/.ssh/identity)
-t Tty; allocate a tty even if command is given.
-T Do not allocate a tty.
-v Verbose; display verbose debugging messages.
Multiple -v increases verbosity.
-V Display version number only.
-q Quiet; don't display any warning messages.
-f Fork into background after authentication.
-e char Set escape character; ``none'' = disable (default: ~).
-c cipher Select encryption algorithm
-m macs Specify MAC algorithms for protocol version 2.
-p port Connect to this port. Server must be on the same port.
-L listen-port:host:port Forward local port to remote address
-R listen-port:host:port Forward remote port to local address
These cause ssh to listen for connections on a port, and
forward them to the other side by connecting to host:port.
-D port Enable dynamic application-level port forwarding.
-C Enable compression.
-N Do not execute a shell or command.
-g Allow remote hosts to connect to forwarded ports.
-1 Force protocol version 1.
-2 Force protocol version 2.
-4 Use IPv4 only.
-6 Use IPv6 only.
-o 'option' Process the option as if it was read from a configuration
file.
-s Invoke command (mandatory) as SSH2 subsystem.
-b addr Local IP address.
I have also looked at the man page with not much of a success. I need
something like a parameter -pw xyz to customize eclipse.
Any ideas?
Cheers,
Mariano
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
David Goodenough
You can not do it directly, but if you use ssh-agent and ssh-add you can
add the ID file and open it with your password before you start eclipse.
If you are using KDE you may find that ssh-agent is already started, and
all you need is to call ssh-add.
David
Karsten M. Self
> On Wednesday 25 December 2002 17:38, Mariano Kamp wrote:
> > Hi,
> >
> > I am using eclipse (http://eclipse.org) to access a cvs repository by
> > using ext:. The problem is that it asks for the ssh password on the
> > command line. Anything I can do to pass it in automatically?
<...>
> You can not do it directly, but if you use ssh-agent and ssh-add you can
> add the ID file and open it with your password before you start eclipse.
>
> If you are using KDE you may find that ssh-agent is already started, and
> all you need is to call ssh-add.
ssh-agent is highly recommended, and as David notes, you'll likely find
you need only supply it with your passphrase.
If you need to run unattended sessions or operations, you might also
look into the forced command option of ssh.
Peace.
--
Karsten M. Self <kms...@ix.netcom.com> http://kmself.home.netcom.com/
What Part of "Gestalt" don't you understand?
Geek for hire: http://kmself.home.netcom.com/resume.html
Bill Moseley
> ssh-agent is highly recommended, and as David notes, you'll likely find
> you need only supply it with your passphrase.
>
> If you need to run unattended sessions or operations, you might also
> look into the forced command option of ssh.
Also check out the keychain package.
--
Bill Moseley mos...@hank.org
Mariano Kamp
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 mk...@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
mk...@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 user...@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
Mariano Kamp
I tried:
ssh-agent
ssh-add (entered passphrase)
ssh mk...@ejbbuilder.sourceforge.net
And Bang ... It is still asking for the passphrase ...
Ok, whatsoever ... I stick to entering the password by hand. The funny
thing is, that I created a key today for the first time, but was
accessing this repository for months without entering the password
manually. I wasn't working on that project for couple of weeks and now
it is not working anymore. What I changed is: SuSe 8.0 -> Debian
Stable/Testing/Unstable (same effect, no matter what version I use) and
upgrading from eclipse 2.0.1 to 2.1 M4. Any of this changes or some
change at sourceforge cut me off.
Mariano
On Wed, 2002-12-25 at 21:28, David Goodenough wrote:
> On Wednesday 25 December 2002 17:38, Mariano Kamp wrote:
> You can not do it directly, but if you use ssh-agent and ssh-add you can
> add the ID file and open it with your password before you start eclipse.
>
> If you are using KDE you may find that ssh-agent is already started, and
> all you need is to call ssh-add.
>
> David
Alan Chandler
Hash: SHA1
On Wednesday 25 December 2002 9:16 pm, Mariano Kamp wrote:
...
> 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
> mk...@ejbbuilder.sourceforge.net's password:
Here is your problem - ssh has failed to find your public rsa key on the
server (actually, although I am not sure, it may have failed to find your
local private key to even try and contact the server) and is falling back to
password authentication (ie is your password in the /etc/password file of the
server). So however much ssh-agent is setup with your password, its never
going to be called into action
- --
Alan Chandler
al...@chandlerfamily.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+Csr1uFHxcV2FFoIRAvimAJ9Jm6CpsNTOm4QK9m7jvdgtwvuKYwCgrgPr
iX4tt7FKt43aByNycKF/GSQ=
=F38o
-----END PGP SIGNATURE-----
Alan Chandler
Hash: SHA1
On Wednesday 25 December 2002 9:30 pm, Mariano Kamp wrote:
> Hi,
>
>
> I tried:
>
> ssh-agent
> ssh-add (entered passphrase)
> ssh mk...@ejbbuilder.sourceforge.net
> And Bang ... It is still asking for the passphrase ...
>
See my reply to your earlier post - its not using the ssh keys in the
authentication.
- --
Alan Chandler
al...@chandlerfamily.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+CsxmuFHxcV2FFoIRAlVAAKColzikmLfH6BnPAlDFfC0z3FUwEgCfV4DD
WmHMNEHZg3QqDxDH4EzZCtQ=
=ipQN
-----END PGP SIGNATURE-----
Colin Watson
> I tried:
>
> ssh-agent
> ssh-add (entered passphrase)
> ssh mk...@ejbbuilder.sourceforge.net
> And Bang ... It is still asking for the passphrase ...
You also need to tell the remote end that the key in question is
acceptable. Try using ssh-copy-id for this.
--
Colin Watson [cjwa...@flatline.org.uk]
PEZ
> I am using eclipse (http://eclipse.org) to access a cvs repository by
> using ext:. The problem is that it asks for the ssh password on the
> command line. Anything I can do to pass it in automatically?
For me it works if I use extssh in Eclipse and set my Debian host to
accept ssh protocol 1 sessions as well. The line in
/etc/ssh/sshd_config reading "Protocol 2" now reads "Protocol 1,2". I
then created a rsa1 key using:
$ ssh-keygen -t rsa1
And I then added that host key entry to sshd_condig and restarted
sshd.
Hope this helps!
/PEZ