openssh 3.6.1_p2 problem with pam (fwd)

Frank Cusack fcusack at
Sat May 3 08:44:41 EST 2003

On Sat, May 03, 2003 at 12:24:44AM +0200, Andrea Barisani wrote:
> On Fri, May 02, 2003 at 02:27:06PM -0700, Frank Cusack wrote:
> > On Fri, May 02, 2003 at 02:03:52PM +0200, Andrea Barisani wrote:
> > > I don't suppose that this is a correct beahviour, what do you think?
> > 
> > Yes, it's not correct behavior.  However, this isn't new to 3.6.1.
> > Not sure why you're only seeing it now.
> Because I've upgraded from 3.5_p1, sorry for not having mentioned that.
> The patch seems to work, thanks a lot. I'll try to understand it and fully test 
> pam behaviour tomorrow, now is too late :).

Yes, I am pretty sure the behavior you're seeing has been there since 3.0.2.
I might be mistaken (probably am).

> I suppose that we'll be seeing this patch in the next version, am I right?

I don't think so.  The openssh team has been generally resistant[1] to most
of my pam suggestions.  I have stopped submitting them at this point.

[1] Not that I fault them for it.  PAM is hard to wedge into openssh
nicely.  Esp. now with privsep.

More information about the openssh-unix-dev mailing list