summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Updated Portuguese translationgnome-3-14Pedro Albuquerque2015-10-291-189/+186
|
* Updated Occitan translationCédric Valmary2015-05-201-267/+335
|
* Updated Turkish translationNecdet Yücel2015-03-161-128/+128
|
* Updated Bosnian translationSamir Ribic2015-03-141-294/+340
|
* Release version 3.14.03.14.0Stef Walter2014-09-232-1/+6
|
* tool: Remove residual GTK+ usagetomsod-m@ya.ru2014-09-231-3/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=736973
* Updated Nepali translationPawan Chitrakar2014-09-221-289/+324
|
* egg: Fix libgcrypt initialization for libgcrypt older than 1.6Stef Walter2014-09-131-0/+1
| | | | A header was missing
* egg: Move file tracker code to egg/ directoryStef Walter2014-09-1310-133/+149
| | | | So that it can be used in other parts of gnome-keyring.
* Release version 3.13.913.13.91Stef Walter2014-09-092-1/+7
|
* configure: Use subdir-objects automake optionStef Walter2014-09-091-1/+1
| | | | In order to shut up automake 1.14
* build: Fix tap-driver to respect tests that skip completelyStef Walter2014-09-091-3/+6
|
* gkm: Fix test for libgcrypt 1.6+ versionStef Walter2014-09-091-0/+6
|
* egg: Accomodate thread-safe libgcrypt 1.6+Stef Walter2014-09-091-37/+8
| | | | | | | | | | | | | libcrypt no longer supports setting our own threading callbacks, and is thread-safe if we call gcry_check_version() before creating threads. Unfortunately we can't guarantee that we call gcry_check_version() early enough, we try our best. Most of the callers of Gcr either don't use libgcrypt, or also initialize it appropriately themselves. Bump libgcrypt dependency to 1.4.5+, and have earlier versions use the native pthread implementation of locking.
* l10n: Update Japanese translationJiro Matsuzawa2014-09-081-3/+3
|
* l10n: Update Japanese translationJiro Matsuzawa2014-09-081-111/+111
| | | | Merge the latest pot.
* gkr-pam-module: Don't use password to determine whether this is a loginwip/emptyJasper St. Pierre2014-09-041-4/+6
| | | | | | | NULL or empty passwords are also valid passwords, so add a separate flag to determine whether to pass --login. https://bugzilla.gnome.org/show_bug.cgi?id=736085
* Updated Russian translationYuri Myasoedov2014-08-291-72/+67
|
* Updated Greek translationTom Tryfonidis2014-08-131-117/+119
|
* pam: Don't use geteuid() to get uid for authenticated userStef Walter2014-08-111-12/+16
| | | | | | | | | Instead we use the 'struct passwd' that we looked up earlier. This causes issues when the PAM stack is not running as the user but as root or someone else. https://bugzilla.gnome.org/show_bug.cgi?id=733418
* doap: add <programming-language>Piotr Drąg2014-07-311-0/+1
|
* doap category coreOlav Vitters2014-07-301-1/+1
|
* autogen.sh: Change CVS to Git in error messageJohannes Löthberg2014-05-191-1/+1
| | | | | | | GNOME has migrated to Git, so the error message should no longer refer to the GNOME CVS. https://bugzilla.gnome.org/show_bug.cgi?id=730340
* Release version 3.12.23.12.2Stef Walter2014-05-132-1/+4
|
* Fix build when configure is called with --disable-docStef Walter2014-05-132-1/+5
|
* Remove useless output from configure statusStef Walter2014-05-131-1/+0
|
* Revert "Revert "Add docs/ directory back into Makefile""Stef Walter2014-05-132-15/+20
| | | | This reverts commit b324fe2d976512b7705beca57ff9a62630cc6c83.
* Revert "Add docs/ directory back into Makefile"Jasper St. Pierre2014-05-012-11/+8
| | | | | | This reverts commit 8ac66bf0d2befdef3b8c96ef147e4e60fa7df0f7. This broke the build. Probably srcdir != builddir troubles.
* Add docs/ directory back into MakefileStef Walter2014-05-012-8/+11
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=727010
* doap: update URLsPiotr Drąg2014-04-042-6/+6
|
* Release version 3.12.03.12.0Stef Walter2014-03-232-1/+4
|
* build: Use /usr/bin/env to find pythonStef Walter2014-03-232-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=726909
* gkm: A testing reliability fixStef Walter2014-03-191-1/+1
|
* Makefile.am: Fixes for building with/without optional componentsStef Walter2014-03-191-3/+5
| | | | | Make build with --disable-pam work again. And enforce that we have all the optional components when doing a 'make distcheck'
* Release version 3.11.923.11.92Stef Walter2014-03-162-1/+19
|
* pam: Fix issue with changed password not unlocking keyringStef Walter2014-03-142-15/+76
| | | | | | | | | | | If a user (needs to) change their password while authenticating (via GDM for example), and pam_gnome_keyring is configured to start the daemon from the session PAM stage, then we were failing to pass the changed password to our session handler. Fix this issue so that this workflow works. https://bugzilla.gnome.org/show_bug.cgi?id=726196
* pam: Pass XDG_RUNTIME_DIR to new processStef Walter2014-03-142-1/+16
| | | | | | | | If XDG_RUNTIME_DIR is not in the PAM envlist, but *is* in the process environment, then steal it from there similar to how we handle DISPLAY. https://bugzilla.gnome.org/show_bug.cgi?id=726196
* pam: Allow unlock_keyring() to be called with a NULL passwordStef Walter2014-03-142-1/+30
| | | | | | | | | | | This happens when doing auto-login. The various side effects of unlock_keyring (including setting *need_daemon) are valuable even in the cases where password is NULL. Add a test that checks that the daemon starts as expected when the user did not authenticate. http://bugzilla.gnome.org/show_bug.cgi?id=726245
* pam: Export a pam_sm_close_session() function entry pointStef Walter2014-03-141-0/+7
| | | | | | | Some PAM callers want this even though we don't do anything interesting in here. https://bugzilla.gnome.org/show_bug.cgi?id=726245
* daemon: Provide caller syncronization for quitting the daemonStef Walter2014-03-145-19/+66
| | | | | | | | | | | Quit control messages are a bit strange because the daemon will quit shortly afterwards. There are three syncronization issues here. 1. We need the response to be written right away, because if we wait for the main loop it might not be written. 2. Callers may want to wait for the daemon to exit, so keep the socket open until we do. 3. Prevent additional connections on the control socket.
* daemon: Stop exposing a GNOME_KEYRING_PID variableStef Walter2014-03-064-88/+34
| | | | | | | | | We exit with the DBus session bus. Remove this clutter from the environment. PAM module no longer cares about the lifetime of the deamon, except in one case: where it started the daemon in order to change a password and the auto_start argument wasn't set. https://bugzilla.gnome.org/show_bug.cgi?id=725801
* daemon: Stop exporting the $GNOME_KEYRING_CONTROL env variableStef Walter2014-03-0610-177/+252
| | | | | | | | | | | | | | | | | | | | In cases where we're using $XDG_RUNTIME_DIR to create a predictable control socket directory, stop setting the $GNOME_KEYRING_CONTROL environment variable. Note that we don't use the $XDG_RUNTIME_DIR fallback. This is because two of our clients don't link in GLib, both the pam and pkcs11 modules. Getting involved in the whole tree of fallback possibilities for how to resolve $XDG_RUNTIME_DIR is not something I'm interested in duplicating. So instead what we do is if $XDG_RUNTIME_DIR is not set, we fall back to using the old $GNOME_KEYRING_CONTROL environment variable. We use the GLib logic when looking for XDG_RUNTIME_DIR. The variable is considered present even when empty. https://bugzilla.gnome.org/show_bug.cgi?id=725801
* daemon: Use $XDG_RUNTIME_DIR to create keyring socket directoryStef Walter2014-03-062-31/+87
| | | | | | | | | | | We create a predictable location under $XDG_RUNTIME_DIR. GNOME does not support multiple GUI sessions per user, so using a predictable directory works well for us. If someone somewhere still wants an alternate location use the --control-directory argument. https://bugzilla.gnome.org/show_bug.cgi?id=725801
* pam: Fix starting the daemon to change passwordStef Walter2014-03-061-10/+19
| | | | | This was broken and would cause the daemon to fail internally. The daemon wasn't being initialized due to the --login argument.
* pam: Add some tests for the PAM moduleStef Walter2014-03-069-0/+729
| | | | | | | | These require you to install some pam configs into /etc/pam.d. You can do it with the following commands: $ make enable-pam-tests $ make disable-pam-tests
* daemon: Don't log debug messages to syslogStef Walter2014-03-061-5/+7
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=711537
* egg: Add egg_tests_copy_scratch_file() method for fixture filesStef Walter2014-03-062-4/+7
|
* daemon: Don't initialize in an idle handler, this is racyStef Walter2014-03-061-21/+16
| | | | | This races with things connecting over the control socket and trying to initialize the daemon
* daemon: During testing write aliases to right directoryStef Walter2014-03-061-0/+10
|
* daemon: More indicative preconditions when startup ordering goes badStef Walter2014-03-062-2/+12
|
View Lorry Controller Status