| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| |
| |
| | |
Remove erroneous NULL from session search directories
Closes #470
See merge request GNOME/gdm!62
|
|/
|
|
| |
Fixes issue #470.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
build: Don't dist generated files
See merge request GNOME/gdm!61
|
|/
|
|
|
|
| |
Various generated files are ending up being disted, which is wrong
becuase they leak the maintainer's prefix into the tarball and are
generated anyway during build.
|
| |
|
|\
| |
| |
| |
| | |
correct gdm_display_store_foreach
See merge request GNOME/gdm!60
|
| |
| |
| |
| |
| |
| |
| |
| | |
The manager code is returning FALSE from its
listify_display_ids foreach function, which is useless
since commit 47d01abe.
This commit makes it return void instead.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The local display factor code is returning FALSE from its
display store foreach functions, which is useless since commit
47d01abe.
This commit makes it return void instead.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The xdmcp code is returning TRUE from its display store foreach
functions, which is useless since commit 47d01abe and wrong
before that.
This commit makes it return void instead.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
gdm_display_store_foreach is designed to iterate through all
displays in the display store. Under the hood, it currently
uses gdm_display_store_find, though, so will prematurely stop
it's loop if a callback returns TRUE. Callers are getting this
wrong. Some return TRUE with the expectation it goes on, and
some fail to return a value at all.
This commit changes gdm_display_store_foreach to use
g_hash_table_foreach instead, so the callback return values no
longer matter.
|
| |
|
|
|
|
| |
(cherry picked from commit 57bf0dd774c6c904291c03e761316b18577b5c3d)
|
|
|
|
|
|
| |
kill-session-processes=1 is long gone
Signed-off-by: Marc-Antoine Perennou <Marc-Antoine@Perennou.com>
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
address timedlogin bug leading to wrong session getting unlocked
Closes #460
See merge request GNOME/gdm!58
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
At the moment it's possible for the login screen to initiate
a timed login operation shortly after a user successfully starts
their session.
GDM won't complete the timed login operation, since a session is
already running, but will erroneously overwrite the username
associated with the session, misattributing the users session
to the timed login user.
Later, attempts to log in as the timed user will instead unlock the
session for the other user, since that session is now associated
with the timed login user.
This commit refuses timed login requests on sessions that are
already running, so the username doesn't get corrupted.
CVE-2019-3825
Closes https://gitlab.gnome.org/GNOME/gdm/issues/460
|
| |
| |
| |
| |
| |
| |
| | |
If a client has a reference to a session that starts running,
refuse to allow further operations on the session.
CVE-2019-3825
|
| |
| |
| |
| |
| |
| |
| |
| | |
There's a bug right now dealing with timed login and reauthentication,
but it's not clear what's going on by looking at the logs.
This commit sprinkles some more logging throughout the code, to make
the bug easier to track.
|
|/
|
|
|
|
|
|
|
| |
At the moment GDM is misidentifying timed login sessions as if
they are automatic login sessions. That leads to their displays
getting killed sometimes shortly after log in.
This commit corrects the check, so that timed login sessions aren't
treated as autologin sessions.
|
|\
| |
| |
| |
| |
| |
| | |
Accept all keyboard layouts by default to prevent confusing behaviour
Closes #433
See merge request GNOME/gdm!57
|
|/ |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Use G_PARAM_STATIC_STRINGS on properties
See merge request GNOME/gdm!56
|
|/
|
|
| |
This prevents strings from being unnecessarily copied.
|
|
|
|
|
|
|
|
|
|
|
| |
Right now if two session files have the same translated name, the login
screen will show both of them. There's no way the user can know which
session does which, so that's not a great user experience. Furthermore,
in the face of symlinks, both sessions truely could be identical.
This commit filters out the duplicates, so only one shows in the list.
Closes https://gitlab.gnome.org/GNOME/gdm/issues/437
|
| |
|
|\
| |
| |
| |
| | |
Get rid of most `g_type_class_add_private` occurrences (and use G_DECLARE_..._TYPE)
See merge request GNOME/gdm!55
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Note that we also removed the finalize() method, as that had become
empty and only gave warnings due to unused variables.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|