The pam service used by the auth-pam plugin is too generic

Bug #499973 reported by Diego Elio Pettenò
This bug report is a duplicate of:  Bug #484069: auth_pam not working. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Invalid
High
Unassigned

Bug Description

Seems like currently the plugin uses the "check_user" service (passed as parameter to pam_start() in plugin/auth_pam/auth_pam.cc line 115), even though I see in bug #484069 that drizzled should be used instead (local patch?).

Having a name as generic as check_user doesn't seem right, I guess I should also rename it for Gentoo and provide a pam.d configuration file if needed.

Revision history for this message
Diego Elio Pettenò (flameeyes) wrote :

Still nothing on this? Latest release still has the same check_user service…

Revision history for this message
Jay Pipes (jaypipes) wrote :

Hi Diego! Sorry for the delay on this :( I'll look into it and see what I can come up with.

Thanks for your patience!

-jay

Revision history for this message
Jay Pipes (jaypipes) wrote :

Hi again,

Yeah, after looking into the source code a bit, I believe that the service name should be "drizzled". Or possibly common-auth (at least on Debian). For Gentoo, is there a pam.d configuration that is appropriate for "typical" use like common-auth?

Finally, should we install a pam configuration file specific to individuals systems? Do you have any advice here?

Thanks much!

-jay

Revision history for this message
Jay Pipes (jaypipes) wrote :

Marking this as a duplicate of the above bug. I will resolve the other bug.

Cheers,

Jay

Changed in drizzle:
status: New → Confirmed
importance: Undecided → High
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.