diff options
| author | Damien Miller <djm@mindrot.org> | 2000-02-02 20:56:20 +1100 |
|---|---|---|
| committer | Damien Miller <djm@mindrot.org> | 2000-02-02 20:56:20 +1100 |
| commit | 17872527893e68ecab20cd75efab00dcea2b29ea (patch) | |
| tree | e8a8980071c2c2b8ba0db827eb5056654c336633 /UPGRADING | |
| parent | 6552758baeaeaf241a0a6c67e2e0a035d31bdf79 (diff) | |
- Documentation fixes from HARUYAMA Seigo <haruyama@nt.phys.s.u-tokyo.ac.jp>
- Added URLs to Japanese translations of documents by HARUYAMA Seigo
<haruyama@nt.phys.s.u-tokyo.ac.jp>
Diffstat (limited to 'UPGRADING')
| -rw-r--r-- | UPGRADING | 17 |
1 files changed, 8 insertions, 9 deletions
@@ -1,3 +1,7 @@ +[ A Japanese translation of this document is available at +[ http://www.unixuser.org/%7Eharuyama/security/openssh/index.html +[ Thanks to HARUYAMA Seigo <haruyama@nt.phys.s.u-tokyo.ac.jp> + OpenSSH is almost completely compatible with the commercial SSH 1.2.x. There are, however, a few exceptions that you will need to bear in mind while upgrading: @@ -21,7 +25,7 @@ key. Solution: You will need to run the *commercial* version of ssh-keygen on the host's private key: -ssh-keygen -u /etc/ssh/ssh_host_key +ssh-keygen -u -f /etc/ssh/ssh_host_key 3. Incompatible changes to sshd_config format. @@ -78,17 +82,12 @@ users access to the account regardless of the policy specified by not add the "nullok" directive to your PAM configuration file unless you specifically wish to allow empty passwords. -7. Rhosts authentication does not work - -Make sure that ssh is installed with the setuid bit set. Note that the -Makefile does not do this by default. - -8. X11 and/or agent forwarding does not work +7. X11 and/or agent forwarding does not work Check your ssh_config and sshd_config. The default configuration files disable authentication agent and X11 forwarding. -9. ssh takes a long time to connect with Linux/glibc 2.1 +8. ssh takes a long time to connect with Linux/glibc 2.1 The glibc shipped with Redhat 6.1 appears to take a long time to resolve "IPv6 or IPv4" addresses from domain names. This can be kludged around @@ -96,7 +95,7 @@ with the --with-ipv4-default configure option. This instructs OpenSSH to use IPv4-only address resolution. (IPv6 lookups may still be made by specifying the -6 option). -10. Logins from commercial ssh generate the error "Selected cipher type +9. Logins from commercial ssh generate the error "Selected cipher type idea not supported by server" This error is generated when a commercial ssh which has been configured to |