Hey, I'm sending here libpam-storepw-0.1.ebuild. libpam-storepw is a pam module to help Linux clients access smb/cifs shares. The problem with cifs or smbfs/smb/samba is that mounting a cifs filesystems requires a password. This module creates a credentials file which can be used by, for example, automount to provide the proper shares for each user. I suggest app-admin/libpam-storepw. Rodrigo
Created attachment 42681 [details] libpam-storepw-0.1.ebuild
Created attachment 42682 [details] A README file with needed explanations. The original package lacks in documentation so I created (copied) this info from the original home page.
I think the package described in bug #67060 has the same functionality, can you check it out ?
I've just looked at bug #67060. During my LDAP/cifs errant I tried smbpwman. It works on solving exactly the same problem as libpam-storepw. But they both take two rather different approachs to this same problem: 1. smbpwman uses a much more sophisticated/complex approach with an outside daemon getting the password from a pam module and eventually passing it to some third component. 2. libpam-storepw is much simplier as it is a pam module itself which saves a credential file for latter use by whoever needs it. The simplicity of libpam-storepw attracted me as it seems much more robust. The idea being: why have two softwares doing the work that can be done greatly by one? I think that both packages should be included in portage as each one will probably fit better in different setups.
Created attachment 42879 [details] libpam-storepw-0.1.ebuild (Patched) I had to include a small patch to make it compatible both with cifs and smbfs and not only with smbfs.
Created attachment 42880 [details, diff] 0.1-cifs.patch The patch itself.
You probably want to clean this up using pam eclass (and remove the epatch comment above).
I'm afraid I didn't understand exactly what do you mean. Could you please elaborate a little longer? What exactly is pam eclass? Where can I find it?
pam eclass - /usr/portage/eclass/pam.eclass Take a look at other pam ebuilds for usage. Look for inherit pam at the top of the ebuild.
Let it be validated before.
1/ This needs to use pam eclass and be rewritten accordingly. 2/ Did you really test this on all those ARCHs in KEYWORDS? If not, remove those untested. 3/ ${A}, ${S}, ${FILESDIR} should be quoted. 4/ Remove the redundant eclass-related comments. Please, fix the above problems and reopen then.
