Vmware's client doesn't have 3des-cbc in its list of available ciphers, although it is compiled in. Add "3des-cbc" to the end of the Ciphers line in the /etc/ssh.conf and it'll work fine. That's the only cipher the NetApp implements.
Toby
-----Original Message----- From: Glenn Dekhayser [mailto:gdekhayser@voyantinc.com] Sent: Wednesday, November 08, 2006 3:20 PM To: Darren Dunham; toasters@mathworks.com Subject: RE: ssh config on DOT 7
Well, we had the problem when trying to get SSH scripting working with VMWare ESX 3 and the Netapp, and we did in fact need authorized_keys2 on both the VMWare and the Netapp box in order to get RSA/SSHv2 working. We tried for a long time to get that working, perhaps we were missing something. When we mentioned this to Netapp they confirmed that our assessment was correct and they edited the docs.
Be CAREFUL here: the filename is "authorized_keys2" for the SSH version2 file, the docs didn't say that, I actually told
netapp about
that Doc bug. Authorized_keys is for version 1, which you shouldn't
be
using anymore. Netapp's SSH client is based on OpenSSH so you can follow any docs on that to see how it really works.
Then that would be a difference from the standard OpenSSH releases. OpenSSH does not require the use of "authorized_keys2" (or hasn't for years). Both v1 and v2 keys happily live together in the default location of ".ssh/authorized_keys".
I haven't used this feature in OnTAP, so I don't know if it is required for setup there.
-- 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. >