[DragonFlyBSD - Bug #2407] openpam won't look for pkgsrc pam module path

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #2407 has been updated by srussell.


I finally had time to upgrade my station to DF 3.8.2. PAM's behavior didn't change compared to DF 3.6.

PAM is working fine only when so modules installed or symlinked in /usr/lib/security, or referred from their complete path (ex: /usr/local/lib/pam_krb5.so). This is because the directory is hard linked in BSDs.

Regards,

SR

tuxillo wrote:
> Hi,
> 
> I might not be entirely but I think we needed dynamic binaries in /bin and /sbin for PAM to work correctly on DragonFly BSD.
> It was recently done so I was wondering if one could have a working PAM setup in 3.8 RELEASE or latest master.
> 
> Can you please retry it?
> 
> Best regards,
> Antonio Huete



----------------------------------------
Bug #2407: openpam won't look for pkgsrc pam module path
http://bugs.dragonflybsd.org/issues/2407#change-12229

* Author: srussell
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: Userland
* Target version: 3.9.x
----------------------------------------
When I try to load pam modules that where installed from pkgsrc, they're installed in /usr/pkg/lib/security, which is not included in the openpam's search paths defined at compile time. I'm getting this error:

Aug 18 12:45:38 yyy login: in openpam_dynamic(): No such file or directory
Aug 18 12:45:38 yyy login: in openpam_load_module(): no pam_xxx.so found
Aug 18 12:45:38 yyy login: pam_start(): system error

The complete path is not specified in the default pam.d service files that comes with DragonFly.




-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account