Hello all,
So I finally got DOT 7 put into production so I can now use ssh without an addition license. My question is where do I put my authorized_keys file so I can use key based authentication on the netapp? (i.e. where is or where should I create the .ssh directory)
Thanks for any help,
SJM
/mnt/etc/sshd/root/.ssh/authorized_keys
On 11/8/06, Sheldon Mustard smustard@gmail.com wrote:
Hello all,
So I finally got DOT 7 put into production so I can now use ssh without an addition license. My question is where do I put my authorized_keys file so I can use key based authentication on the netapp? (i.e. where is or where should I create the .ssh directory)
Thanks for any help,
SJM
-- Sheldon Mustard smustard@gmail.com "There will be no order, only chaos." - Pi (1998) --
Hello all,
So I finally got DOT 7 put into production so I can now use ssh without an addition license. My question is where do I put my authorized_keys file so I can use key based authentication on the netapp? (i.e. where is or where should I create the .ssh directory)
Thanks for any help,
Put it in /vol/vol0/etc/sshd/root/.ssh assuming the key is for user "root". You probably have to make the root/.ssh directory.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
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.
Glenn (the other one)
-----Original Message-----
Hello all,
So I finally got DOT 7 put into production so I can now use ssh without an addition license. My question is where do I put my authorized_keys file so I can use key based authentication on the netapp? (i.e. where is or where should I create the .ssh directory)
Thanks for any help,
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.
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.
FWIW, on 7.0.5 I only have ssh2 enabled and authorized_keys worked.
SJM
On 11/8/06, Glenn Dekhayser gdekhayser@voyantinc.com wrote:
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. >
To setup authorized keys for a Netapp, put the keys in:
/<netapp>/root/etc/sshd/<user>/.ssh/authorized_keys
where <netapp> is just the name of the netapp, <user> is the name of the user account on the netapp. I suggest you make a seperate restricted account for stuff like this.
You can use the 'useradmin role ...' commands to create a user account and then limit which command(s) can be run. Very nice.
John
Thanks everyone for helping me find what I should have found myself in the docs :).
SJM
-
Darren Dunham -
Glenn Dekhayser -
John Stoffel -
Sheldon Mustard -
Stephen C. Losen -
tmac