README.platform 4.0 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697
  1. This file contains notes about OpenSSH on specific platforms.
  2. AIX
  3. Beginning with OpenSSH 3.8p1, sshd will honour an account's password
  4. expiry settings, where prior to that it did not. Because of this,
  5. it's possible for sites that have used OpenSSH's sshd exclusively to
  6. have accounts which have passwords expired longer than the inactive time
  7. (ie the "Weeks between password EXPIRATION and LOCKOUT" setting in SMIT
  8. or the maxexpired chuser attribute).
  9. Accounts in this state must have their passwords reset manually by the
  10. administrator. As a precaution, it is recommended that the administrative
  11. passwords be reset before upgrading from OpenSSH <3.8.
  12. As of OpenSSH 4.0p1, configure will attempt to detect if your version
  13. and maintenance level of AIX has a working getaddrinfo, and will use it
  14. if found. This will enable IPv6 support. If for some reason configure
  15. gets it wrong, or if you want to build binaries to work on earlier MLs
  16. than the build host then you can add "-DBROKEN_GETADDRINFO" to CFLAGS
  17. to force the previous IPv4-only behaviour.
  18. IPv6 known to work: 5.1ML7 5.2ML2 5.2ML5
  19. IPv6 known broken: 4.3.3ML11 5.1ML4
  20. If you wish to use dynamic libraries that aren't in the normal system
  21. locations (eg IBM's OpenSSL and zlib packages) then you will need to
  22. define the environment variable blibpath before running configure, eg
  23. blibpath=/lib:/usr/lib:/opt/freeware/lib ./configure \
  24. --with-ssl-dir=/opt/freeware --with-zlib=/opt/freeware
  25. If sshd is built with the WITH_AIXAUTHENTICATE option (which is enabled
  26. by default) then sshd checks that users are permitted via the
  27. loginrestrictions() function, in particular that the user has the
  28. "rlogin" attribute set. This check is not done for the root account,
  29. instead the PermitRootLogin setting in sshd_config is used.
  30. If you are using the IBM compiler you probably want to use CC=xlc rather
  31. than the default of cc.
  32. Cygwin
  33. ------
  34. To build on Cygwin, OpenSSH requires the following packages:
  35. gcc, gcc-mingw-core, mingw-runtime, binutils, make, openssl,
  36. openssl-devel, zlib, minres, minires-devel.
  37. Darwin and MacOS X
  38. ------------------
  39. Darwin does not provide a tun(4) driver required for OpenSSH-based
  40. virtual private networks. The BSD manpage still exists, but the driver
  41. has been removed in recent releases of Darwin and MacOS X.
  42. Nevertheless, tunnel support is known to work with Darwin 8 and
  43. MacOS X 10.4 in Point-to-Point (Layer 3) and Ethernet (Layer 2) mode
  44. using a third party driver. More information is available at:
  45. http://www-user.rhrk.uni-kl.de/~nissler/tuntap/
  46. Linux
  47. -----
  48. Some Linux distributions (including Red Hat/Fedora/CentOS) include
  49. headers and library links in the -devel RPMs rather than the main
  50. binary RPMs. If you get an error about headers, or complaining about a
  51. missing prerequisite then you may need to install the equivalent
  52. development packages. On Redhat based distros these may be openssl-devel,
  53. zlib-devel and pam-devel, on Debian based distros these may be
  54. libssl-dev, libz-dev and libpam-dev.
  55. Solaris
  56. -------
  57. If you enable BSM auditing on Solaris, you need to update audit_event(4)
  58. for praudit(1m) to give sensible output. The following line needs to be
  59. added to /etc/security/audit_event:
  60. 32800:AUE_openssh:OpenSSH login:lo
  61. The BSM audit event range available for third party TCB applications is
  62. 32768 - 65535. Event number 32800 has been chosen for AUE_openssh.
  63. There is no official registry of 3rd party event numbers, so if this
  64. number is already in use on your system, you may change it at build time
  65. by configure'ing --with-cflags=-DAUE_openssh=32801 then rebuilding.
  66. Platforms using PAM
  67. -------------------
  68. As of OpenSSH 4.3p1, sshd will no longer check /etc/nologin itself when
  69. PAM is enabled. To maintain existing behaviour, pam_nologin should be
  70. added to sshd's session stack which will prevent users from starting shell
  71. sessions. Alternatively, pam_nologin can be added to either the auth or
  72. account stacks which will prevent authentication entirely, but will still
  73. return the output from pam_nologin to the client.