- (stevesk) [README.privsep] PAM+privsep works with Solaris 8.

2 files changed, 8 insertions, 4 deletions

diff --git a/ChangeLog b/ChangeLog
index df1e6bddd..0c59cec0d 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,6 @@
+20020514
+ - (stevesk) [README.privsep] PAM+privsep works with Solaris 8.
+
 20020513
  - (stevesk) add initial README.privsep
  - (stevesk) [configure.ac] nicer message: --with-privsep-user=user
@@ -579,4 +582,4 @@
  - (stevesk) entropy.c: typo in debug message
  - (djm) ssh-keygen -i needs seeded RNG; report from markus@
 
-$Id: ChangeLog,v 1.2114 2002/05/13 05:22:21 djm Exp $
+$Id: ChangeLog,v 1.2115 2002/05/13 23:31:09 stevesk Exp $
diff --git a/README.privsep b/README.privsep
index 4f15cf433..51a4e3f6b 100644
--- a/README.privsep
+++ b/README.privsep
@@ -31,8 +31,9 @@ privsep user and chroot directory:
 Privsep requires operating system support for file descriptor passing
 and mmap(MAP_ANON).
 
-PAM currently only works with privsep on Linux.  It does not function
-on Solaris or HP-UX.  PAMAuthenticationViaKbdInt does not function with
+PAM-enabled OpenSSH is known to function with privsep on Linux and
+Solaris 8.  It does not function on HP-UX with a trusted system
+configuration.  PAMAuthenticationViaKbdInt does not function with
 privsep.
 
 Note that for a normal interactive login with a shell, enabling privsep
@@ -50,4 +51,4 @@ process 1005 is the sshd process listening for new connections.
 process 6917 is the privileged monitor process, 6919 is the user owned
 sshd process and 6921 is the shell process.
 
-$Id: README.privsep,v 1.1 2002/05/13 03:57:04 stevesk Exp $
+$Id: README.privsep,v 1.2 2002/05/13 23:31:10 stevesk Exp $