<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN"> <HTML> <HEAD> <META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9"> <TITLE>The Linux-PAM Module Writers' Guide: Notes</TITLE> <LINK HREF="pam_modules-10.html" REL=next> <LINK HREF="pam_modules-8.html" REL=previous> <LINK HREF="pam_modules.html#toc9" REL=contents> </HEAD> <BODY> <A HREF="pam_modules-10.html">Next</A> <A HREF="pam_modules-8.html">Previous</A> <A HREF="pam_modules.html#toc9">Contents</A> <HR> <H2><A NAME="s9">9. Notes</A></H2> <P>I intend to put development comments here... like ``at the moment this isn't actually supported''. At release time what ever is in this section will be placed in the Bugs section below! :) <P> <P> <UL> <LI>Perhaps we should keep a registry of data-names as used by <CODE>pam_[gs]et_data()</CODE> so there are no unintentional problems due to conflicts? </LI> <LI><CODE>pam_strerror()</CODE> should be internationalized.... </LI> <LI>There has been some debate about whether <CODE>initgroups()</CODE> should be in an application or in a module. It was settled by Sun who stated that initgroups is an action of the <EM>application</EM>. The modules are permitted to add additional groups, however. </LI> <LI>Refinements/futher suggestions to <CODE>syslog(3)</CODE> usage by modules are needed. </LI> </UL> <P> <HR> <A HREF="pam_modules-10.html">Next</A> <A HREF="pam_modules-8.html">Previous</A> <A HREF="pam_modules.html#toc9">Contents</A> </BODY> </HTML>
