Bug#578650: RFP: libpam-python -- a PAM Module that runs the Python interpreter to w$

[Petter Reinholdtsen <pere@hungry.com>]

Package: wnpp
Severity: wishlist

* Package name    : libpam-python
  Version         : 0.1.1
  Upstream Author : Russell Stuart <russell-pampython@stuart.id.au>
* URL             : http://www.stuart.id.au/russell/files/pam_python
* License         : Eclipse Public License v1.0
  Programming Lang: C, Python, etc.)
  Description     : a PAM Module that runs the Python interpreter to write pam mo$

Perhaps the long package description can be based on this text from
the web page:

  The pam_python PAM module runs the Python source file (aka Python
  PAM module) it is given in the Python interpreter, making the PAM
  module API available to it. This document describes the how the PAM
  Module API is exposed to the Python PAM module. It does not describe
  how to use the API. You must read the PAM module writers guide to
  learn how to do that. To re-iterate: this document does not tell you
  how to write PAM modules, it only tells you how to access that the
  PAM module API from Python.

  Writing PAM modules from Python incurs a large performance penalty
  and requires Python to be installed, so it is not the best option
  for writing modules that will be used widely. On the other hand
  memory allocation / corruption problems can not be caused by bad
  Python code, and a Python module is generally shorter and easier to
  write than its C equivalent. This makes it ideal for the system
  administrator who just wants to make use of the the PAM API for his
  own ends while minimising the risk of introducing memory corruption
  problems into every program using PAM.

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)