Bugzilla Bug 23789

I want to use pam_pwdfile[1]. This is a pam module which provides
authentification against a file with contains username:crypted_password
pairs.
I wanted to make an own ebuild for this, but I had some problems with this.

This module compiles just fine when I do:
<code>
ebuild /usr/portage/sys-libs/pam/pam-0.75-r11.ebuild unpack
cd /var/tmp/portage/pam-0.75-r11/work/Linux-PAM-0.75/modules/
tar xzf /usr/portage/distfiles/pam_pwdfile-0.98.tar.gz #[2]
ebuild /usr/portage/sys-libs/pam/pam-0.75-r11.ebuild merge
</code>

I.e. you just need to unpack in the modules directory in the pam-sources
tree and then compile as normal. Is it possible to add a local useflag to
future pam ebuild so that this step will be done?
If this is not possible for security or whatever reason please give me a hint
how an own ebuild could be made.

TIA and bye
Frank Benkstein. benkstein _AT_ gmx.de

PS: The module is published under terms of GPL-2.

[1] http://cpbotha.net/pam_pwdfile.html
[2] http://cpbotha.net/files/pam_pwdfile/pam_pwdfile-0.98.tar.gz

Its not much overhead - Ill rather just add it and get done with in the
next few days.

Hi.

Is there anything going on with this bug?

Greetings
Frank Benkstein.

pam_dotfile is in portage, which i think sounded familiar.

might want to see if it gives you thr functionality you need.

just a thought.

Thank you. But no it doesnt. I want to use pam_pwdfile with checkpassword-pam
an the authenticated users do not even need to exist in the system database
this way.
With pam_dotfile they need an account and a home directory which is not what
I want.

In CVS as a seperate ebuild, sys-libs/pam_pwdfile.