summaryrefslogtreecommitdiff
path: root/UPGRADING
diff options
context:
space:
mode:
authorDamien Miller <djm@mindrot.org>2000-02-02 20:56:20 +1100
committerDamien Miller <djm@mindrot.org>2000-02-02 20:56:20 +1100
commit17872527893e68ecab20cd75efab00dcea2b29ea (patch)
treee8a8980071c2c2b8ba0db827eb5056654c336633 /UPGRADING
parent6552758baeaeaf241a0a6c67e2e0a035d31bdf79 (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--UPGRADING17
1 files changed, 8 insertions, 9 deletions
diff --git a/UPGRADING b/UPGRADING
index 5c6715ce2..8f661cdbb 100644
--- a/UPGRADING
+++ b/UPGRADING
@@ -1,3 +1,7 @@
1[ A Japanese translation of this document is available at
2[ http://www.unixuser.org/%7Eharuyama/security/openssh/index.html
3[ Thanks to HARUYAMA Seigo <haruyama@nt.phys.s.u-tokyo.ac.jp>
4
1OpenSSH is almost completely compatible with the commercial SSH 1.2.x. 5OpenSSH is almost completely compatible with the commercial SSH 1.2.x.
2There are, however, a few exceptions that you will need to bear in 6There are, however, a few exceptions that you will need to bear in
3mind while upgrading: 7mind while upgrading:
@@ -21,7 +25,7 @@ key.
21Solution: You will need to run the *commercial* version of ssh-keygen 25Solution: You will need to run the *commercial* version of ssh-keygen
22on the host's private key: 26on the host's private key:
23 27
24ssh-keygen -u /etc/ssh/ssh_host_key 28ssh-keygen -u -f /etc/ssh/ssh_host_key
25 29
263. Incompatible changes to sshd_config format. 303. Incompatible changes to sshd_config format.
27 31
@@ -78,17 +82,12 @@ users access to the account regardless of the policy specified by
78not add the "nullok" directive to your PAM configuration file unless 82not add the "nullok" directive to your PAM configuration file unless
79you specifically wish to allow empty passwords. 83you specifically wish to allow empty passwords.
80 84
817. Rhosts authentication does not work 857. X11 and/or agent forwarding does not work
82
83Make sure that ssh is installed with the setuid bit set. Note that the
84Makefile does not do this by default.
85
868. X11 and/or agent forwarding does not work
87 86
88Check your ssh_config and sshd_config. The default configuration files 87Check your ssh_config and sshd_config. The default configuration files
89disable authentication agent and X11 forwarding. 88disable authentication agent and X11 forwarding.
90 89
919. ssh takes a long time to connect with Linux/glibc 2.1 908. ssh takes a long time to connect with Linux/glibc 2.1
92 91
93The glibc shipped with Redhat 6.1 appears to take a long time to resolve 92The glibc shipped with Redhat 6.1 appears to take a long time to resolve
94"IPv6 or IPv4" addresses from domain names. This can be kludged around 93"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
96use IPv4-only address resolution. (IPv6 lookups may still be made by 95use IPv4-only address resolution. (IPv6 lookups may still be made by
97specifying the -6 option). 96specifying the -6 option).
98 97
9910. Logins from commercial ssh generate the error "Selected cipher type 989. Logins from commercial ssh generate the error "Selected cipher type
100 idea not supported by server" 99 idea not supported by server"
101 100
102This error is generated when a commercial ssh which has been configured to 101This error is generated when a commercial ssh which has been configured to