Users panel crashes with g_error() if some of libpwquality calls fails,
e.g. when pwquality.conf is broken. The default values should be used
instead of crash. Let's use g_warning() instead of g_error() in that
case.
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/171
The logic for the password mismatch warnings didn't handle the case where
you deleted both the passwords - it would still show them as not
matching.
Fix this by handling the three cases:
- Passwords are different
- Passwords are the same
- No passwords entered
If <tab> is pressed and password is not yet validated (ie. the verify
entry is not sensitive), focus skips the verify entry, even if the
password is strong enough. Let's validate the password when <tab> is
pressed (ie. before focus change) to prevent this <tab> breakage...
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/38
It is possible to use weak passwords in dialogs currently, which is
not intentional and leads to problems in case of changing password of
current user. This regression was introduced by Bug 780002, which added
new strength level for weak passwords. Let's reflect the new level also
when setting sensitivity...
https://bugzilla.gnome.org/show_bug.cgi?id=788122
As a user was not set on the password dialog yet. Also make
sure that we do not try to update the password strength label
before anyone has entered anything in the dialogue itself.
The um-password-dialog combobox has a column in its model associated
with what password action to apply. Possible actions are:
- Normal password
- Set password at next login
- No password needed
- Lock account
- Unlock account
These actions are currently represented in the code with harded coded
numeric values (0-4).
This commit cleans up the hard coding to use a symbolic enumeration
instead.
https://bugzilla.gnome.org/show_bug.cgi?id=671858
Check the new password matching after focusing out either entries.
Validate the content of the verify password entry after
focusing out either the new password entry or the verify entry.
Previously the user could mistype his new password in the new
password entry, but when it was corrected, the verify entry
would still be indicating that the confirmation password did not
match when it did.
https://bugzilla.gnome.org/show_bug.cgi?id=668844
This also adds another out parameter to pw_strength(), which is a discrete
indication of the password strength (to be used with GtkLevelBar). The
advantage of having such a parameter back from pw_strength() is that we
can make sure the fill value and the hint string change at the same
time, for better consistency.
https://bugzilla.gnome.org/show_bug.cgi?id=679984
Passing the username and the old password allows the password
quality check find more bad passwords. Also, add a way to provide
more information about why a password is not good enough.
https://bugzilla.gnome.org/show_bug.cgi?id=676396
Move the 'generate password' icon into the entry to make
the focus chain more straightforward. Also switch from
generating a choice of 6 passwords in a menu, just put
put the next choice directly into the entry.
To keep the password generation keyboard accessible,
add a 'Generate password' context menu item.
https://bugzilla.gnome.org/show_bug.cgi?id=633601https://bugzilla.gnome.org/show_bug.cgi?id=658522
And use a link to local documentation, rather than an
external website in English.
Removed mentions of "in English" for the languages that mentioned it.
https://bugzilla.gnome.org/show_bug.cgi?id=643118
