[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Probably a newbie's question

I've been wondering about this for a while.  

Does it perhaps make sense to add a "code" field to the conversation function?  Right now, the prompt is provided as a string, and can vary significantly between PAM modules.  The problem is that application developers who want to interface PAM need to end up writing modules that know about all the possible prompts that can be provided by any PAM module. 

The current scheme works fine for console based applications, but makes writing GUI based applications quite difficult.  If there were a more uniform way of providing a prompt, which contains a code along with the text prompt, it would be both easier for applications to parse, and easier to localize (since this can be done by the application).



Quoting Jenn Vesperman <jenn@anthill.echidna.id.au>:

> On Sat, 2002-03-09 at 00:50, Fernando Orus wrote:
> > Thanks for your answer, Jenn, but I am afraid there's something I 
> > don't understand.
> > 
> > I guess I need to create a function with the same prototype that 
> > appears in the pam_conv struct definition and use that function 
> > instead of misc_conv in my program, is this correct?
> Pretty much, yes. The information is at:
> http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/pam_appl-3.html
> Look for the heading 
> 	3.2 What is expected of an application
> 	The conversation function
> > The problem is that I have no idea about the code that must be in 
> > that function. You say that there is information on that issue in 
> > the "pamdocs". 
> I was fairly vague.
> The relevent information - or at least, as much as I have - is in the 
> link above.
> The conversation function must be capable of displaying or retrieving
> text strings as requested by the PAM module that calls the function.
> Jenn V.
> -- 
>     "Do you ever wonder if there's a whole section of geek culture 
>         	you miss out on by being a geek?" - Dancer.
> jenn@anthill.echidna.id.au     http://anthill.echidna.id.au/~jenn/
> _______________________________________________
> Pam-list mailing list
> Pam-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/pam-list

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index] []