Re: [Cooker] Re: Cooker Login Fail after daily Update

[Gustavo De Nardin (spuk)]

* Olivier Blin <blino@mandriva.com> [2008-05-20 10:57 +0200]:
> "Gustavo De Nardin (spuk)" <gustavodn@mandriva.com> writes:
> 
> > * Moreno <moreno.mg@gmail.com> [2008-05-20 08:37 +0200]:
> >> Hi
> >> 
> >> On Tue, May 20, 2008 at 8:01 AM, Moreno <moreno.mg@gmail.com> wrote:
> >> > Hi
> >> >
> >> > After the daily update of my Cooker machine all attempts to make a login fail.
> >> 
> >> The problem is which urpmi have installed the packages and generated 2
> >> rpmnew files but it do not have signalled this.
> >> 
> >> I have replaced the /etc/login-def and /etc/pam.d/system-auth file
> >> with the .rpmnew file and all return to work normally.
> >
> > Do you have msec installled? See
> > <https://qa.mandriva.com/show_bug.cgi?id=29719>.
> 
> That's not strictly related to msec, other config tools can modify pam
> config files.

The problem here is Msec changing it without my knowledge. I would watch, or
at least be more wary, for trouble, if (I knew) my pam config was modified.


> But is it normal that pam_unix does not work anymore in the config
> file? In the initial plan, it was said that pam_tcb was backwards
> compatible with pam_unix, it does not seem to be the case...
> 
> Anyway, I don't think we should force migration to pam_tcb in %post,
> there's no real reason to handle .rpmnew files differently in this
> package if pam_tcb is backwards compatible as you claim.

I'm not sure I upgraded to that version of pam. I'll check later at home. I
think I'll put the old pam and config back and watch how %post handles it.