Ludwig Nussel wrote:
Stephan Kulow wrote:
Possibly I can even have a su without pam for this purpose - now that I think about it.
Another idea, what about just build ignoring the dependency of pam to krb5? That breaks pam_unix but su as called by the build script skips calling pam_unix.so anyways due to use of pam_rootok.so for auth and account. AFAICS pam_unix doesn't do anything useful in session either (just syslogs the call). So it's 'required' flag in common-sessoin could be changed to 'optional' without negative impact. That way su when called by root would still work despite broken pam_unix
Ah, spoke too fast. That would still make pam require krb5 for building ie keep it in the loop of course. So pam would need to be split up to build the library and the modules separately. Looks doable as well as the modules all live in a subdirectory that could be skipped when building. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org