Summary: | reinstate pam_console references in /etc/pam.d/* if pam_console use flag present | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | splite <splite-gentoo> |
Component: | [OLD] Unspecified | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
splite
2005-08-30 08:33:05 UTC
I'd say because the idea is of removing pam_console entirely with new version of sys-libs/pam. Is this an upstream decision, or Gentoo's? Is it going to be replaced with something equivalent? (Group-based access control doesn't scale to hundreds of users sharing hundreds of machines. Whoever is sitting at the console should have control of the devices, not someone logged in remotely.) Upstream never supported pam_console (it's a RedHat patch). pam_console will probably have its own ebuild for who wants to tinker with it, but it's up to them to change their pam.d files. It's pointless adding pam_console useflag on other packages, as just login and eventually ?dm should use it. Also, it screw ups pretty badly when used in the wrong way. It's a no-go for now. |