users-dont-autofill-generated-passwd : lp:~vcs-imports/gnome-control-center/+git/gnome-control-center : Git : Code : gnome-control-center

Get this branch:: git clone -b users-dont-autofill-generated-passwd https://git.launchpad.net/~vcs-imports/gnome-control-center/+git/gnome-control-center

Branch merges

Branch information

Name:: users-dont-autofill-generated-passwd

Repository:: lp:~vcs-imports/gnome-control-center/+git/gnome-control-center

Recent commits

817cb64... by Felipe Borges <email address hidden> on 2020-01-06

user-accounts: Don't fill verification entry for generated passwords

Users can generate passwords while creating a new account or when
changing their existing account's password. The verification entry
is a security measure to make sure users didn't confuse their
passwords and get locked out of their accounts. For this reason,
it is important that users physically type the generated password,
to make sure they are able to login using it subsequently.

Fixes #827

3576133... by Felipe Borges <email address hidden> on 2019-12-19

user-accounts: Use CcPermissionInfobar to lock/unlock the panel

This moves the GtkLockButton out of the headerbar and starts to
consume the CcPermissionInfobar API to lock/unlock the panel.

See #771

5d2a884... by Felipe Borges <email address hidden> on 2019-12-19

common: Introduce "CcPermissionInfobar" widget

The "CcPermissionInfobar" widget is a more descriptive way to
communicate that some Settings panel needs authentication in order
to perform certain actions.

This widget doesn't handle the permissions (as in GPermission)
itself. It needs to be binded to an existing instance of GPermission,
and it will react to the permission's state (show when the current
user is not authorized, and hide when the user is authorized).

This is part of a big set of changes that aim to set a consistent
authentication method accross Settings panels.

See #685, #556, and #771

f7ac015... by Jordi Mas on 2020-01-03