Re: libpam segfault when passwd passes NULL pamh (was Re: gcc -O2 produces invalid object code (x86_64, netbsd-5 branch))

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Tue, Mar 09, 2010 at 01:05:19AM -0500, Richard Hansen wrote:
> >Anything more than a plain number and fixed error message is not
> >possible with the constraints of the interface.
> 
> I'm sorry, I'm still not following.  Are you arguing that
> pam_strerror() isn't needed for pam_start() failures because there's
> no useful information to convey to the user?

No, just that the help it can give is very limited.

> >So Sun at least documents that pam_strerror(3) can be called
> >explicitly with NULL as handle if pam_start(3) failed.  XSSO is
> >silent on the topic, but it is the most sensible behavior.
> 
> Agreed.

I'll talk with DES about the issue, so that it can be adressed
upstream.

Joerg