Summary: | sys-auth/pambase-20100723[kerberos] does not allow console login | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Eray Aslan <eras> |
Component: | [OLD] Core system | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Eray Aslan
![]() Sufficient will skip over other limitations, I'll check why it's reporting bad jump, as it works here, but it might be different setup. [success=1 default=ignore] simply means that pam_krb5 acts in the stead of pam_unix if it succeeds or it is ignored altogether if it fails, which is exactly what one would do... My reason for not using the minimum_uid option is that Gentoo still _lacks_ a standardized user id ripartition so I'd rather not consider anything in particular there. It is just too complicated and too fragile, e.g. skipping over pam_unix with success=1. It is best left to sysadmin to decide how to handle kerberos auth. Keep it simple (see above) and let him/her decide according to local security policy. Average *nix user will not (should not?) be using pam_krb5 anyway. Final decision is yours, of course. I am mostly trying to learn. (In reply to comment #1) > My reason for not using the minimum_uid option is that Gentoo still _lacks_ a > standardized user id ripartition True. But I still think a more secure default is warrented here. Sysadmin can change the default. To sum up, I feel that in the sys-auth/pam_krb5 case, our job as developers is to give sysadmins simple and sane defaults and perhaps nudge them gently to what we feel is best. But I expect that all users of pam_krb5 will be looking around under pam.d/ and making the necessary changes according to local policy. Sorry for the bug spam. I fixed the login error... as for the sysadmin vs defaults, I'd say that having it working out of the box for the most stupid case should probably be enough. Most sysadmins would still set up PAM by themselves rather than get it defined by pambase, but it's a start at least, I'd say... |