https://bugzilla.novell.com/show_bug.cgi?id=477488
User kukuk@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=477488#c3
--- Comment #3 from Thorsten Kukuk
(In reply to comment #1)
It is very unlikely that we will ever do that: The result is a far too complex thing as that you can manage that with automated tools.
Well, you can do that unconditionally. Eg:
common-auth: auth substack common-auth-optional-sufficient-required auth include common-auth-after-success
You just need to know which modules to put in common-auth-after-success. I'm sure some other modules could benefit from this.
And I'm sure this will have very bad side effects. substack does _not_ behave the same way as include.
+ http://bugzilla.gnome.org/show_bug.cgi?id=514862 To make the keyring behaves properly with pam-config, I had to revert this upstream change. I couldn't login with an account with an empty password in openSUSE (empty as in "passwd -d"), but I guess it's a config option somewhere since it works on other distros. And now the keyring will force asking a password.
Seems the people discussing in that bug have no clue about the simplest PAM standards.... use_authtok use_first_pass try_first_pass are the "magic" options every PAM module should understand and which would solve the problems of the above bug. Everything suggested and done in that bug report is wrong. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.