The following module was proposed for inclusion in the Module List:

  modid:       Authen::PAM::Module
  DSLIP:       bdcOp
  description: Base Class for writing PAM modules in Perl
  userid:      BHILDRED (Ben Hildred)
  chapterid:   14 (Security_and_Encryption)
  communities:
    pam-l...@redhat.com perl...@perl.org

  similar:
    PAM Authen::PAM

  rationale:

    The Pam APIs were written in c. This translates the module api into
    perl.

    The rationale for the module:

    Excerpts from some emails I sent:

    So the problem began with browsing my Linux distro's repository
    looking for a pam module to create home directories on demand. I
    found one that works almost like I want. Almost, not quite, so onto
    the source code. It is written in python. I have a severe
    Pathological and Eclectic aversion to python. It reminds me of the
    Rubbish Lists i turned in in my hi-school COBOL programing class.
    I'd rather try to transcend dental medication.

    so... I've been looking for a project to brush up my c skills,
    maybe embed a interpreter for practice... so announcing version
    0.0001. Write your own device driver days here. It is about 75% to
    theoretically functional level.

    About The namespace:

    On 1/2/2012 12:34 AM, Steffen Mueller wrote: <snip> > On 12/29/2011
    01:21 AM, ben wrote: <<snip>> >> I have not yet registered the
    namespace and I'm still >> tweaking the handling of constants but it
    appears to >> work. > Superficial comment: It's customary not to use
    underscores > in Perl module names. In modules, you
    CamelCase::Or::Colons, > in corresponding distribution names, use
    dashes instead of > the double-colons. > I was aware of this, which
    was my reason for doing so. I have not run this by the folks pause
    yet, but my thoughts on the namespace would be as follows: my main
    module would be PAM::Module or Authen::PAM::Module, Internal (not
    intended for public use sub modules would be ...::Module::_foo,
    framework modules such as test cases and pragmas which would change
    the behavior of the main module would be ...::Module::foo and actual
    authentication modules would be ...::Module::Foo. I would welcome
    any comments or criticism of this thought.

  enteredby:   BHILDRED (Ben Hildred)
  enteredon:   Wed Jan  4 00:44:36 2012 GMT

The resulting entry would be:

Authen::PAM::
::Module          bdcOp Base Class for writing PAM modules in Perl   BHILDRED


Thanks for registering,
-- 
The PAUSE

PS: The following links are only valid for module list maintainers:

Registration form with editing capabilities:
  
https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=d6600000_8552a4b58b827952&SUBMIT_pause99_add_mod_preview=1
Immediate (one click) registration:
  
https://pause.perl.org/pause/authenquery?ACTION=add_mod&USERID=d6600000_8552a4b58b827952&SUBMIT_pause99_add_mod_insertit=1
Peek at the current permissions:
  
https://pause.perl.org/pause/authenquery?pause99_peek_perms_by=me&pause99_peek_perms_query=Authen%3A%3APAM%3A%3AModule

Reply via email to