how can I use ssh ver 1 for a device?

[Hopper, Faron W.]

Paul,
   Thank you for your response.  I didn't think of trying the ssh config.  I figured that since RANCID was able to pass the hostname and the cipher type to the ssh executable when it called it, that it would be just a matter of specifying the protocol.  I looked at the /etc/ssh_config and it appears to be using the default of 2,1.  There was no ~/.ssh/config so I am inclined to beleive that it should drop down to version 1 automagically. 
    I created an ~/.ssh/config file and put this in it

hosts x.x.x.x
protocol 1

and that allowed me to ssh to those devices. 

Thanks,
Faron

-----Original Message-----
From: Paul Frommeyer [mailto:paul at palas.com]
Sent: Mon 9/12/2005 1:02 PM
To: Hopper, Faron  W.
Subject: Re: how can I use ssh ver 1 for a device?

In reply to your message of Mon, 12 Sep 2005 11:51:08 -0400:

| I have been reading the list archives and the man page for cloginrc trying=
|  to determine how to set the =2Ecloginrc file to allow connectivity to a=
|  device that requires ssh version 1=2E  The only thing that looks like it=
|  would do this is the add sshcmd <> command=2E =0D

Of course, I'm sure There's More Than One Way To Do It, but IMO, you're
swimming upstream. Were I you, I would pry over at your SSH client
setup rather than the RANCID scripts. Specifically, IIRC, both SSH2 and
OpenSSH allow the specification of which protocol to use as part of a
host profile in the ssh_config file (for OpenSSH, it's done with the option
keyword "Protocol"; see ssh_config(5) ). So, simply create a profile
(either in the global server config or for the user RANCID is running as)
for the host you need to reach via V1, specifying that only the V1 protocol
should be used.  That should take care of everthing, without having to
"explain" anything to RANCID, or specify any command line opts to ssh.

FWIW,
	Paul

P.S. As with most things, I've found the O'Reilly book on SSH to be
indispensable when wrassling with that particular software, and it has
in-depth sections for client configuration.

Paul Frommeyer         Senior Networking Consultant             paul at palas.com