
|
|
[Return to the System Notices Directory]
August 13th, 2003 - Migration to OpenSSH
On August 13th, 2003, the CS department Unix systems (Sun, Linux, and
SGI) moved from using ssh.com SSH2 to OpenSSH in order to be
compatible with the rest of the IU systems. Unfortunately, there are
some incompatibilities between the two packages. If you used SSH2 previously,
you should take the following actions in order to configure your account
to use OpenSSH.
- OpenSSH uses the ~/.ssh directory for your configuration files
and keys while SSH2 used ~/.ssh2. However, earlier versions of
SSH from ssh.com that were installed on the CS systems also
used the ~/.ssh directory so it is quite possible you have
an old ~/.ssh directory. In order to prevent conflicts with
OpenSSH, you are strongly encouraged to move the old
.sshd directory out of the way. You can do this by running:
mv ~/.ssh ~/.ssh.old
- You will need to recreate your keypair and authorized_keys files
using OpenSSH. In order to do this, you should follow the procedure
outlined in the
OpenSSH FAQ Entry
- If you access group and class accounts using ssh, this authorization
will have to be reinitialized. Unfortunately, this reauthorization
cannot be done until you recreate your ssh keys. So, once you complete
step 2 above you will need to submit a request to the
CSG Helpdesk
to have your access reestablished.
- If you have a console/GUI login from before August 13th, your login session
is probably running under the old ssh-agent. As a result, if you had your
ssh keys loaded (via ssh-add) you will have to logout and back in again
to get the new ssh-agent before you will be able to ssh to remote systems
without being prompted for a password.
You may also want to check out the OpenSSH to SSH2 FAQ Entry for information about how to get
OpenSSH and SSH2 to interoperate.
If you have problems related to this change, please submit a
request for help using the
CSG Help Desk.
[Return to the System Notices Directory]
|