Problems with conversation functions PAM + OpenSSH

Frank Cusack fcusack at
Sat Jun 21 09:51:32 EST 2003

On Sat, Jun 21, 2003 at 12:47:21AM +1000, Damien Miller wrote:
> Jakub Jurkiewicz wrote:
> > Hello
> >  sorry, for bothering you with this problem, but I ca't find solutions. 
> > I write small PAM module, and I've got the problem with conversation 
> > function with OpenSSH 3.5p1.
> > When the message style is PAM_PROMPT_ECHO_ON, or PAM_PROMPT_ECHO_OFF 
> > everything is allright. But when I use PAM_TEXT_INFO, or PAM_ERROR_MSG,
> > ssh prints nothing on the client side. Does anyone know the reason of 
> > this, and how can I print messages to the user.
> Please try CVS -current. The PAM support has changed substantially.

PAM_TEXT_INFO and PAM_ERROR_MSG are even more broken in -current than
they are in 3.5/3.6.

Jakub: it's a bug in openssh.

Damien, openssh team: see my previous email where I sketched out what
PAM should do (IMHO) and what openssh actually does.


More information about the openssh-unix-dev mailing list