| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
|
| |
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
gdm-pin was an experimental feature that was going to get added to
gnome-shell many years ago. It never happened and these days it
would probably be implemented a little different anyway.
(It would probably use a gdm pam extension)
There's no point keeping this service file around that we aren't
using, so this commit drops it.
Closes: https://gitlab.gnome.org/GNOME/gdm/-/issues/731
|
| |
|
|
|
|
| |
kill-session-processes=1 is long gone
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
In theory sending the password to them could be beneficial.
If for instance, they have pam_krb5 or pam_ecryptfs or pam_sss.
In practice, the stacks will fail if the passwords don't match,
and prevent autologin from continuing.
This commit just sidesteps them for now. Eventually,
authconfig/et al, will need to get updated to accomodate us.
|
| |
|
|
|
|
|
|
|
|
|
| |
If pam_gdm fails we shouldn't call into pam_unix since it can lead
to the system asking for a password, and autologin isn't equipped for
that.
This commit changes the pam configuration to jump to pam_permit if
pam_gdm fails.
https://bugzilla.gnome.org/show_bug.cgi?id=770612
|
| |
|
|
| |
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If the user has an encrypted disk then systemd will cache the password
they type into the keyring. It makes sense to try to use this password
for automatic login purposes first, since on single user machines,
the sole user password is likely to match the disk password.
Of course if it doesn't work we'll fall back to the old way of doing
automatic login without a password (and then the user will have to
manualy enter if they need to for gnome-keyring or whatever)
https://bugzilla.gnome.org/show_bug.cgi?id=769950
|
| |
|
|
| |
This prevents it from breakings setups building using --without-systemd
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Originally, the idea was to have pam-pin as an optional module in gdm-password,
but since the PIN can easily get misconfigured, what we want here is
to give the user a choice at the login screen, so we want two different
conversations at the same time.
The pin module is marked requisite, so if it fails we stop before touching
the other modules and immediately report to the greeter (which then goes
on with gdm-password)
https://bugzilla.gnome.org/show_bug.cgi?id=693968
|
| |
|
|
|
|
|
|
|
|
| |
From https://bugzilla.redhat.com/show_bug.cgi?id=882385:
"The loginuid is for actual logins by people. Its not intended for
system use. All daemons should have loginuid set to -1, meaning that its
a system process and not related to activity by a person."
https://bugzilla.gnome.org/show_bug.cgi?id=693152
|
| |
|
|
|
|
| |
This is a backport from exherbo changes by Saleem Abdulrasool <compnerd@compnerd.org>
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
|
|
from Exherbo commit http://git.exherbo.org/gnome.git/commit/?id=fadb3f3b8ad30833618f0695e7564983a059d58e
http://bugzilla-attachments.gnome.org/attachment.cgi?id=221058
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
