For those of us who do require / use PAM, will the expired password patch be ported to 3.7.1p2? If so, any kind of estimate on when? Thanks
lbecke at mchsi.com wrote:> > For those of us who do require / use PAM, will the expired password patch be > ported to 3.7.1p2? > > If so, any kind of estimate on when?I've just ported the patch to 3.7.1p2 and the new patch is at [1]. I haven't done any testing of it, however the parts that didn't apply were trivial. [1] http://www.zip.com.au/~dtucker/openssh/ -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
On Wed, 2003-09-24 at 06:25, lbecke at mchsi.com wrote:> For those of us who do require / use PAM, will the expired password patch be > ported to 3.7.1p2? > > If so, any kind of estimate on when?I see that Darren has already replied. We will probably be adding expired password changing support to the CVS version shortly (after we all catch up on our sleep). We'd appreciate help in testing it when it goes in. -d
I would also like to thank the group for this patch. The patch applied without error. The configure worked as expected. The make built the binaries properly. The sshd server worked properly, when tested with the UsePAM=yes and UsePAM=no on Solaris 5.8. I've built the packages, and currently await approval to distribute the package to the remainder of our servers. Job well done, and greatly appreciated. Let's hope this is the last round of emergency changes for a bit, so you all can get some sleep.