> I remembered you had, but I couldn't recall where it was.
>
> It took about two hours to get this module to do all that I wanted.
> Although my pam_test is limited in that it uses __pam_display_msg()
> instead of using the conversation function directly, which it really
> ought to do, to give good control over conversations/prompts.
The project private __pam_display_msg is insufficient to test
whether the applications conversation function is returning
information correctly to a service module. It is an output
to application function only. It must never be used for
*PROMPT* message types.
> But all I wanted/needed was to be able to test pam_eval() and
> depth/invocation limits so I could observe pam_eval()/include
> interactions.
>
> I should probably just merge the conversation code from your pam_sample
> into my pam_test and put that somewhere where search engines can find
> it.
>
> > It seems like something useful for a catch all OpenSolaris repo.
> > I'm not sure it's something to ship with the base OpenSolaris.
>
> Well, certainly not in the install CD.
>
> > How many of us actually change libpam and need to exercise our
> > specific changes?
>
> I was thinking this could help PAM *application* developers too.
> Alright, so there's not many of *those* either :/
IMO, there's little need, perhaps in a non Sun repo you could
stick things, like the banter about contrib repo.
or maybe even the nico.net/opensolaris/repo ;-)
Gary..
