ATE enhancement: public/private key authentication now supported. For security-conscious environments, this is a much more secure login method, particularly if you disable the traditional name/password login.
To configure this type of authentication:
| • | Generate an OpenSSH-style public and private key, preferably on the PC. See the CRYPTO.SBR update below for one option. |
| • | Transfer the public key file to the server and append it to the file $HOME/.ssh/authorized_keys. Obviously you'll need some alternate way of connecting to the target system to set this up. |
| • | Save the private key file somewhere in your user directory tree (specific to the user). |
| • | In the ATE login configuration dialog, specify the private key file. If a private, key file is specified and the server supports that method, it will be used in preference to any other authentication method. As with the login password, you can store the private key passphrase in the ATE configuration to avoid having to type it each time you connect, although if someone gains access to your PC, they'll be able to connect to the server using your credentials. |
Note that if you connect using private key authentication, that method will be used for authenticating any file transfers invoked directly by or through ATE. And even if you were forced to enter the passphrase to connect, it will be remembered and not required for file transfers.
