SSH Access: Difference between revisions
m (Created page with "Access to LSDF consoles and administrative interfaces is via SSH only. All administrative access is tunneled through a jumphost. Currently the jumphost is named '''scc-cn-r164.sc…") |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Access to LSDF consoles and administrative interfaces is via SSH only. All administrative access is tunneled through a jumphost. Currently the jumphost is named '''scc-cn-r164.scc.kit.edu'''. The jumphost has physical interfaces to the different consoles in the LSDF. Check with the admin of the jumphost to receive a login. He will ask you for your key (either private with password or public) that will be copied in your home directory of the 'jumphost'. |
Access to LSDF consoles and administrative interfaces is via SSH only. All administrative access is tunneled through a jumphost. Currently the jumphost is named '''scc-cn-r164.scc.kit.edu'''. The jumphost has physical interfaces to the different consoles in the LSDF. Check with the admin of the jumphost to receive a login. He will ask you for your key (either private with password or public) that will be copied in your home directory of the 'jumphost'. |
||
=== Common SSH problems === |
|||
Most people have already access to different machines using SSH. Here are some things that may be less known but help if you have trouble accessing machines via ssh: |
|||
1) there are 2 different public (!) key file formats: OpenSSH and SSH2. Both formats use the same key encryption and you could use an editor to convert one format to the other. Per default ssh-keygen on UNIX/Linux generates a |
|||
SSH protocol 2 format public key. |
|||
2) As said above, the private key is the same in both OpenSSH and SSH protocol 2 |
|||
3) Your permissions must be set very strict. .ssh must have 700, the private key file must have 600. SSH refuses (silently ) otherwise. |
|||
Revision as of 17:01, 30 August 2013
Access to LSDF consoles and administrative interfaces is via SSH only. All administrative access is tunneled through a jumphost. Currently the jumphost is named scc-cn-r164.scc.kit.edu. The jumphost has physical interfaces to the different consoles in the LSDF. Check with the admin of the jumphost to receive a login. He will ask you for your key (either private with password or public) that will be copied in your home directory of the 'jumphost'.
Common SSH problems
Most people have already access to different machines using SSH. Here are some things that may be less known but help if you have trouble accessing machines via ssh:
1) there are 2 different public (!) key file formats: OpenSSH and SSH2. Both formats use the same key encryption and you could use an editor to convert one format to the other. Per default ssh-keygen on UNIX/Linux generates a SSH protocol 2 format public key.
2) As said above, the private key is the same in both OpenSSH and SSH protocol 2
3) Your permissions must be set very strict. .ssh must have 700, the private key file must have 600. SSH refuses (silently ) otherwise.
