- Securecrt home end keys install#
- Securecrt home end keys software#
- Securecrt home end keys password#
Alternately, you may wish to simply print it out on paper and OCR it back if you lose the key files.You're using SecureCRT to connect to an HP Aruba network device (or similar) and you have logging enabled. One option would be to burn them to CD-R (multiple copies on the disk), write the passphrase on the CD-R, then put it all into a sealed envelope in a secure offsite location (safe-deposit box). This will look something like:ĩ) Make a backup of your private key and public key files. For even more security, you may wish to place the key files on a removable USB key that you carry around.Ĩ) Send the contents of the "something.pub" key to the server admin so that they can add it to the authorized key file on the servers. A location like "C:\SSHKeys" or placing the key files in your "My Documents" folder, or somewhere under your user profile directories is best.
It should also be somewhere safe and part of your regular backups. Given recent developments in the world of encryption, it may be better to use 2048 bit RSA keys.ħ) Choose a directory for the private key. On more modern hardware, key length of 2048 bits can be used. The comment should probably be of the form although there are no strict requirements for what you place in the comment.Ħ) A key length of 1024 bits is fine.
It will be used to encrypt your private key. Your "My Documents" folder is probably a good place.Ĥ) Key type can be either RSA or DSA (doesn't matter except for older systems like Solaris).ĥ) The passphrase should be something you can remember. It should be placed somewhere secure and backed up frequently.
This file is the central storage location for all of your public/private SSH2 keys. Steps to create a public key pair in SecureCRTĪlternately, to create a session specific key (a better method).Ī) Click on the Connect button, highlight the Session for which you want to create a session key and choose Properties.ī) Connection -> Authentication -> Primary -> PublicKey -> PropertiesĢ) Under "Public Key", choose "Use Identify File". The super-secure key should be used with critical servers and the less-secure key can be used for other servers. My recommendation for users is that they create a "super-secure" key and a "less-secure" key. You should do this as little as possible, because if an attacker swipes your private keyfile and passphrase, they can impersonate you on those servers. Note #2: You can use a particular key file for multiple servers. This will allow you somewhat seamless movement between the 4 Solaris servers. So for additional connections to the same server, you will not be re-prompted for a password. Note #1: One advantage of public keys is that SecureCRT runs a key-agent in the background.
Securecrt home end keys install#
(Or you have an admin install the public key for you.)
Securecrt home end keys software#
Because of the way things work in SSH2-land, you typically create the SSH2 keys using the client software in Windows, then copy the public key up to your user directory on the server that it will be used for. The process is similar for PuTTY, but SecureCRT offers a much cleaner interface then PuTTY. As long as the user's keep their SSH private key files safe (along with protecting them with a decent passphrase), you're less likely to encounter a break-in of your Unix/Linux servers.
Securecrt home end keys password#
For optimal security, it's better to require public keys for logging into a server rather then allowing password authentication.