The format OpenSSH is looking for is (note, this is all on one line: Oki/Ccd8KOgYaAYMe7gwJknkfQshBb/1MQ90nUgb 5PwbHVgskHo9rQKCTZl45NVJpaH7bT PBML4VfqZgJ0xALX元gjHV8SPkHFi3LrccMTl5ok 0ksWOUCBW0Z+OFt4Eqxs5BdTv7iqm8 RYX6ptqSg9M0wfrCa6H/kLDZq+pqGLf9Aoj6G2jb r6q3GulNbIZUAAAACBAJAcFS8JQWRF Obx5pVAUa/mqFBXwAAAIEAwspDclkK0D24HBXEJI 5PXLKAA2NnOAvmRPyEaiS19rzepJIPģ/MkuUeTJ37rOkD8us9WRuqQygWOEb4By/0pAqxy jleWaGS4Oo/Z7t7HzXSWT2Qi/nXvRy Q7ILQULPCA7nEYGl01cUm8Renwjp7fJP5k4dCVUF 9my5Ak+Xd2T3AAAAFQD2SpiKb0XWYm The key as generated by Windows looks like:Ĭomment: 'SFK DSA from windows 'ĪAAAB3NzaC1kc3MAAACBANUnwcm2SB3Sv9T+WttX V374jaavhO6Y7NbLg9iTK3tEwmuufnĦYetiNSXIcTSfiWtK+oznc3T+U7LQQivpszdGPoF g6RAvvyaEE+uqSyR+ogQq0+ePvegxN Now you need to reformat the text a little. You'll want to insert the text from your public key (mytestkey.pub) into authorized_keys2.ħ. On the server running OpenSSH (squirrel, euclid, groucho, etc.), edit the file in your home directory ~/.ssh/authorized_keys2. In any event, we're going to have to edit this file, so all you really need to do is copy the publickey file up to the server and put it somewhere convenient.Ħ. For OpenSSH, the folder to use is '.ssh' and the authorization file is 'authorized_keys2'. Otherwise, enter a nice, long, secure passphrase.ĥ. This is dangerous, protect that file well. If you really want to automate this, then you might want to leave the passphrase blank. Secure Shell for Workstations creates 2 files, one named mytestkey (the private half, which you need to keep safe) and mytestkey.pub (the public half, which you can safely give away).

Name your key - for this example, let's call it mytestkey. Under settings, choose Generate New Keypair.ģ. Install SSH for Workstations 3.1 if you don't have it yet.

Ssh secure shell for workstations 3