Call for testing for 3.6: password expiry?

[alchemist at magestower.net]

While I understand these are 3.6 issues, I'd like to 
confirm that we're also pleased with Sun's BSM patch. 
 We're currently running it in conjunction with 
uncommenting the old pam password aging stuff and 
disabling privsep, so I can't speak to BSM in conjunction 
with privsep, but by itself, it's good.

We're running the BSM patch on Solaris 2.6, 7, and 8.

--Jason

On Fri, 21 Mar 2003 09:18:03 +1100
  Damien Miller <djm at mindrot.org> wrote:
>*This message was transferred with a trial version of 
>CommuniGate(tm) Pro*
>Jeff Koenig wrote:
>>I have tried this patch (against 3.5p1) and would very 
>>much like it to be in the OpenSSH 3.6p1 release, if 
>>possible:
>>http://bugzilla.mindrot.org/show_bug.cgi?id=14
>>
>>On that note, I'd like the Sun BSM patch to be included 
>>also, if possible.  I have it working applied to 3.5p1:
>>http://bugzilla.mindrot.org/show_bug.cgi?id=125
>>
>>In fact, both patches work together, apparently.
>
>These won't be in the 3.6p1 release. The password expiry 
>issue will be one of the foci of the next release cycle. 
>I haven't yet looked into the BSM patch.
>
>>Bugzilla Bug 463: PrintLastLog doesn't work in privsep 
>>mode
>>http://bugzilla.mindrot.org/attachment.cgi?id=235&action=view 
>
>This will be looked at too. This issue exists in the 
>OpenBSD version too, so it needs to be fixed at the 
>source.
>
>-d
>
>_______________________________________________
>openssh-unix-dev mailing list
>openssh-unix-dev at mindrot.org
>http://www.mindrot.org/mailman/listinfo/openssh-unix-dev