From 510c0a8a20754d6643bd08f6078567873c25098b Mon Sep 17 00:00:00 2001
From: dtucker <dtucker>
Date: Tue, 24 Feb 2004 05:14:41 +0000
Subject: [PATCH]  - (dtucker) {README.platform] Add platform-specific notes.

---
 ChangeLog       |  1 +
 README.platform | 22 ++++++++++++++++++++++
 2 files changed, 23 insertions(+)
 create mode 100644 README.platform

diff --git a/ChangeLog b/ChangeLog
index 51799497..8ba0da6b 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -23,6 +23,7 @@
  - (tim) [openbsd-compat/getrrsetbyname.c] Make gcc 2.7.2.3 happy.  ok djm@
  - (djm) Crank RPM spec versions
  - (dtucker) [README] Add pointer to release notes.  ok djm@
+ - (dtucker) {README.platform] Add platform-specific notes.
 
 20040223
  - (dtucker) [session.c] Bug #789: Only make setcred call for !privsep in the
diff --git a/README.platform b/README.platform
new file mode 100644
index 00000000..f9318b78
--- /dev/null
+++ b/README.platform
@@ -0,0 +1,22 @@
+This file contains notes about OpenSSH on specific platforms.
+
+AIX
+---
+As of OpenSSH 3.8p1, sshd will now honour an accounts password expiry
+settings, where previously it did not.  Because of this, it's possible for
+sites that have used OpenSSH's sshd exclusively to have accounts which
+have passwords expired longer than the inactive time (ie the "Weeks between
+password EXPIRATION and LOCKOUT" setting in SMIT or the maxexpired
+chuser attribute).
+
+Accounts in this state must have their passwords reset manually by the
+administrator.  As a precaution, it is recommended that the administrative
+passwords be reset before upgrading from OpenSSH <3.8.
+
+Solaris
+-------
+Currently, sshd does not support BSM auditting.  This can show up as errors
+when editting cron entries via crontab.  See.
+http://bugzilla.mindrot.org/show_bug.cgi?id=125
+
+$Id$
-- 
2.45.1