summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* doc: mention new split authentication featurewip/multi-stackRay Strode2011-06-131-5/+27
| | | | | This commit updates the docs to mention the new split authentication feature recently added.
* greeter: Add smartcard pluginRay Strode2011-06-1320-1/+3272
| | | | | This commit adds a plugin to initiate a conversation when smartcards are inserted.
* greeter: Add fingerprint pluginRay Strode2011-06-1315-1/+696
| | | | | This commit adds a plugin to initiate a conversation for fingerprint scans.
* greeter: Add a login extension mechanism to greeterRay Strode2011-06-1329-378/+3431
| | | | | | | | | | | | | | This allows extensions to drive which PAM conversations get run and potentially augment the login window UI. This commit adds one builtin extension that does the traditional unified authentication thing, and a plugin for password-only based authentication. By default we use the builtin extension, but enable the plugin with --enable-split-authentication Subsequent commits will add support for fingerprint and smartcard plugins.
* daemon: Distinguish "pam module failed" from "authentication failed"Ray Strode2011-06-1311-35/+154
| | | | | | | | If pam_start() fails, that suggests the configured service stack is failing independent of the user account. This commit exposes that failure as "service unavailable" instead of "authentication failed".
* daemon: Store multiple conversations in the sessionRay Strode2011-06-1315-477/+1408
| | | | | | We keep multiple conversations in the session now, keyed off of which PAM service is at the other end. Much of the guts still only operate on the first conversation added though.
* daemon,greeter: Make greeter/autologin session initiate PAM conversationRay Strode2011-06-137-15/+110
| | | | | | | | | | | | | Now the greeter (and also the autologin code) has to say what PAM stack it wants the slave to run. When that stack is ready, we emit the Ready signal as before, but now the Ready signal carries a string argument saying which service is ready to converse. When we support multiple PAM stacks, the greeter will call StartConversation for each stack, and will keep the UI associated with each stack disabled until the Ready signals come back one-by-one.
* daemon: Rename session worker to the service it's managingRay Strode2011-06-133-16/+57
| | | | | This way when we're running multiple PAM conversations at once it will be obvious which worker is managing which conversation.
* daemon: Make current pam conversation explicit throughout codeRay Strode2011-06-1311-144/+260
| | | | | | | | | | | | | | We want to eventually support having multiple simultaneous PAM conversations in one login screen (so, e.g., username/password, smart card, and fingerprint all work at the same time). This commit refactors the session code to be in terms of a conversation object. With this change, it should be easier later to have multiple conversation objects. The conversation is named by the pam service the login screen is talking to.
* greeter: drop is-interactive stuffRay Strode2011-06-131-65/+3
| | | | | | | It's pretty old code that was designed to prevent proceeding until the user had a chance to pick language, etc. I don't think it's really relevant anymore, and it adds some complexity to the code I'd rather not have.
* simple-greeter: Don't request an invalid sizeBenjamin Otte2011-06-131-18/+12
| | | | | | | | | | | | | | | | | | GTK widgets must at all times report a size they can handle. So it is not allowed to return 0 when not realized, because then size allocations break when GTK uses this size for its widget. In this case, GTK uses the pre-realize size to determine the size it should request when creating the greeter window - chicken and egg so to say. This patch just uses the default monitor (I guess the root window's monitor is the default monitor?) for determining the login window size. One thing this patch doesn't do is add a call to gtk_widget_queue_resize() from the realize callback or from monitor-changing signals, though that's probably technically necessary. https://bugzilla.gnome.org/show_bug.cgi?id=646498
* configure: use ustar by defaultRay Strode2011-06-131-1/+1
| | | | This gets around filename length limitations.
* configure: bump version to 3.1.2Ray Strode2011-06-131-1/+1
|
* Updated Slovenian translationMatej Urbančič2011-06-111-41/+128
|
* Allow .xsession-errors to be a symlink or FIFOMartin Pitt2011-06-071-6/+6
| | | | | | | | | | | | | | | | | Don't rename .xsession-errors to .xsession-errors.old if the file is not a regular file. The later code will truncate the file to zero anyway, so even in that case the file won't grow indefinitely. This is handy when the home directory is on NFS and you want to avoid network contention when there are buggy programs which spam .xsession-errors. Also drop the second check that .xsession-errors is a regular file even if the opening succeeded. With that, we'd open a temporary .xsession-errors.XXXXXX even if ~/.xsession-errors was perfectly writable (such as being a symlink to /dev/null). Bug: https://bugzilla.gnome.org/show_bug.cgi?id=639527 Bug-Ubuntu: https://launchpad.net/bugs/771661
* Updated Norwegian bokmål translationKjartan Maraas2011-06-071-37/+42
|
* Updated Galician translationsFran Diéguez2011-06-061-38/+44
|
* Updated Hebrew translation.Yaron Shahrabani2011-06-041-39/+45
|
* dconf: set XDG_CACHE_HOME in addition to XDG_CONFIG_HOMERay Strode2011-06-011-3/+7
| | | | | If we don't set this, it will use the default which can cause weird behavior when building in a logged in session.
* Revert "dconf: set XDG_CACHE_HOME along with XDG_CONFIG_HOME"Ray Strode2011-06-011-1/+0
| | | | | | | This reverts commit 2108fbb01143a6cfd5847e9564f0f20bce00570c. It was wrong. dconf uses both XDG_CACHE_HOME and XDG_CONFIG_HOME. They both need to exist and be distinct.
* data: update uninstall rule for new data filesRay Strode2011-05-311-0/+2
| | | | | | We now install some noop mime uri handlers, so this commit makes sure they get uninstalled at uninstall time as well.
* dconf: set XDG_CACHE_HOME along with XDG_CONFIG_HOMERay Strode2011-05-311-0/+1
| | | | Later versions of dconf seem to stuff it there now.
* Register /bin/true as URI scheme handler for several schemesVincent Untz2011-05-313-0/+35
| | | | | | | | | Starting with glib 2.28, we don't use gconf to find out which handler should be used for a URI scheme, and we need to provide a custom MIME configuration for the gdm user to ensure no default URI scheme handler is used. CVE-2011-1709
* [l10n]Updated Catalan (Valencian) translationCarles Ferrando2011-05-291-343/+288
|
* Updated Spanish translationDaniel Mustieles2011-05-251-2/+2
|
* daemon: Up verbosity of X loggingRay Strode2011-05-241-1/+1
| | | | This makes things a little easier for debugging problems.
* greeter: fix scrollbar in greeterRay Strode2011-05-241-1/+0
| | | | | | | | | | | We were forcing the minimum height of the scrollable widget to be the minimum height of the tree view. This meant the scrollable widget would never "clamp" the tree view to a reasonable size. Downstream report here: https://bugzilla.redhat.com/show_bug.cgi?id=703243
* Add the end tag to method so introspection can work with python-dbus.Martin Owens2011-05-241-0/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=647336
* Added screenshotsJorge González2011-05-241-36/+42
|
* greeter: drop select-language gooRay Strode2011-05-232-17/+0
| | | | | | | It's left over from an era past; before two was superceded by three; when black wasn't yet the new black; when questions were asked more frequently than they needed to be.
* gdmflexiserver: fail more abruptly if user can't jump to login screenRay Strode2011-05-231-9/+14
| | | | | | | | If the user can't jump to an existing login screen, we should fail instead of firing up a new one. This way we don't get a stream of login screens from ssh users or whatever.
* configure: switch to xz instead of bz2Ray Strode2011-05-231-1/+1
| | | | This will save master.gnome.org work when posting new releases.
* configure: require accounts service 0.6.12Ray Strode2011-05-231-1/+1
| | | | | Earlier versions have some bugs that make GDM crash, so probably better to just force this version.
* daemon: move WINDOWPATH setting up top of get_welcome_environmentRay Strode2011-05-201-7/+1
| | | | | | | | | | | | At the top of the function we loop through "optional" environment variables and set them in the welcome environment only if they are already set in the slave environment. After commit 62c19ec5d67bf3f4279607012d04f2ef948a63d5 WINDOWPATH is optional now as well. This commit consolidates the WINDOWPATH setting code with the other optional environment variable code at the top.
* greeter: Fix double free on timed loginJürg Billeter2011-05-201-0/+1
|
* Improve the audit logic. Fix the gdm_session_worker_get_username to cache theBrian Cameron2011-05-191-6/+16
| | | | | | | latest username in the audit class. Then make sure to call this function before auditing to ensure that username is always set. This fixes a problem where audit would have a NULL value if it were obtained via PAM and not the GUI.
* Only get username in the simple-slave if the session is not NULL.Brian Cameron2011-05-191-1/+4
|
* Do not set WINDOWPATH if it is NULL.Brian Cameron2011-05-191-1/+8
|
* daemon: kill stuck processes if they don't die on termRay Strode2011-05-193-4/+48
| | | | | | | Some PAM modules are really slow to shut down. We need to handle them being slow to shut down better, (by not blocking login on them shutting down etc), but in the mean time force them to die immediately.
* greeter: add small delay when presenting messagesJosselin Mouette2011-05-191-10/+150
| | | | | | | | | | | | When PAM sends a message up to the greeter to show the user, it shows it right away, immediately overwriting any previous message. This commit introduces a message queue, so that each pending message gets a reasonable amount of time on screen for the user to read. https://bugzilla.gnome.org/show_bug.cgi?id=583856
* daemon,greeter: login after PAM has had time to talk to userRay Strode2011-05-197-48/+48
| | | | | | | | | | | | | The greeter currently gives the go ahead for the session to start as soon as the user has been authorized. Then the slave quickly runs through the remaining hoops and the greeter gets promptly killed. This commit changes the logic so that the slave doesn't get the go ahead to start the session until all the hoops have been run through, and potential messages have been queued, and displayed. https://bugzilla.gnome.org/show_bug.cgi?id=583856
* daemon: drop dead codeRay Strode2011-05-181-4/+0
| | | | | | | create_static_display checks for a NULL return value in a function that can't return NULL. This commit drops that check.
* Stop hardcoding path to grepJosselin Mouette2011-05-181-1/+1
| | | | | /usr/bin/grep is correct on Solaris but not on Linux/sparc https://bugzilla.gnome.org/show_bug.cgi?id=649415
* configure: drop X_CONFIG_OPTIONSRay Strode2011-05-171-12/+0
| | | | It's unused so get rid of it.
* daemon: drop bogus commentRay Strode2011-05-171-5/+0
| | | | | It appears to be copy-and-paste mistake, or maybe it was relevant before commit a736563893b6c99c900198afaeea1684bc8c1259 not sure.
* greeter: clean up some benign warningsRay Strode2011-05-171-3/+4
|
* greeter: force symbolic icons in panelRay Strode2011-05-121-2/+2
| | | | | | | | | | | | gtk falls back to non-symbolic icons before looking for symbolic icons in parent icon themes. For the greeeter panel, though, any symbolic icon is better than a non-symblic icon, so that behavior is wrong. This commit changes gdm to not check for fallbacks in the absense of a symblic icon. The icons we care about are shipped in the base icon theme anyway, so we can depend on them being available.
* Updated Esperanto translationKristjan SCHMIDT2011-05-121-416/+593
|
* Updated Spanish translationJorge González2011-05-101-406/+411
|
* greeter: disconnect from user manager on tear downRay Strode2011-05-101-0/+16
| | | | | We don't want any signal handlers to run after the widgets they are meant for are destroyed.
View Lorry Controller Status