On 20.03.2009 4:39, Marc Weber wrote:
I appreciate any idea which can help me finding the problem.
I've rebuilt pam witth --enable-debug.
That's the result (bad system):
http://rafb.net/p/UjuL0Z71.html
I've got a lot of trouble interpreting it..
What is causing the final failure.
It doesn't look like this (healthy system):
http://rafb.net/p/uK6Mv531.html
Somewhere
[misc_conv.c:misc_conv(280)] allocating empty response structure array.
[misc_conv.c:misc_conv(289)] entering conversation function.
[misc_conv.c:read_string(136)] called with echo='OFF', prompt='New Password: '. New Password:
[misc_conv.c:read_string(204)] we got some user input
[pam_item.c:pam_get_item(152)] called.
[misc_conv.c:misc_conv(280)] allocating empty response structure array.
[misc_conv.c:misc_conv(289)] entering conversation function.
[misc_conv.c:read_string(136)] called with echo='OFF', prompt='Reenter New Password: '. Reenter New Password:
[misc_conv.c:read_string(204)] we got some user input
appears asking for the new password?
Can you at help me interpreting that file output?
Eg where does the execution of a config line start and end?
What to say? The key line in the "bad" system debug output is:
[pam_dispatch.c:_pam_dispatch_aux(85)] module returned: User not known to the
underlying authentication module
IOW, your configuration is somehow broken.
--
Sincerely Your, Dan.
_______________________________________________
Pam-list mailing list
Pam-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/pam-list
