| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Intltool is deprecated; use gettext instead.
Fixes https://gitlab.gnome.org/GNOME/gcr/issues/18
|
|\
| |
| |
| |
| | |
fix parameter type for signal handler
See merge request GNOME/gcr!16
|
|/
|
|
|
|
|
|
| |
The on_prompter_prompting signal handler used a struct as a otherwise unused parameter
while a pointer was passed by the caller. This led to a stack smashing on the ppc64le
platform and a segfault.
fixes https://bugzilla.redhat.com/show_bug.cgi?id=1631759
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Add myself as maintainer
See merge request GNOME/gcr!13
|
|/
|
|
| |
With the approval of Daiki Ueno.
|
|\
| |
| |
| |
| | |
cleanup: Don't use deprecated g_type_class_add_private() anymore
See merge request GNOME/gcr!12
|
| |
| |
| |
| |
| | |
Use `G_ADD_PRIVATE()` (or the convenience macro
`G_DEFINE_TYPE_WITH_PRIVATE()`) instead.
|
| |
| |
| |
| |
| | |
Use `G_ADD_PRIVATE()` (or the convenience macro
`G_DEFINE_TYPE_WITH_PRIVATE()`) instead.
|
|/
|
|
|
| |
Use `G_ADD_PRIVATE()` (or the convenience macro
`G_DEFINE_TYPE_WITH_PRIVATE()`) instead.
|
|\
| |
| |
| |
| | |
attributes: Fix annotations syntax
See merge request GNOME/gcr!10
|
|/
|
|
| |
Annotations parameters should only have a final colon.
|
| |
|
|\
| |
| |
| |
| | |
build: Fix gcr-trust symbols not appearing in GIR, and hence also VAPI
See merge request GNOME/gcr!7
|
|/
|
|
|
|
|
|
|
|
| |
Despite making it into the API docs, the trust APIs are not included
in the GCR GIR or VAPI files, since they were marked as private in the
Makefile, not public. As a result, apps using language bindings cannot
use the trust API without manual intervention.
This fixes the missing API by marking gcr-trust.c and gcr-trust.h
public.
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
'15-ip-addresses-are-not-shown-in-gcr-viewer-for-subjectalternativename' into 'master'
gcr-certificate-extensions: Fix typo in parsing SubjectAltName
Closes #15
See merge request GNOME/gcr!8
|
|/
|
|
| |
Reported by David Leonard in #15.
|
|\
| |
| |
| |
| | |
Fix hashtable ordering assumptions
See merge request GNOME/gcr!9
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With GLib 2.59, gnome-keyring's `test-login-auto` test fails:
Gcr-CRITICAL **: 14:34:24.126: expected prompt property 'choice-label'
to be "Automatically unlock this keyring whenever I\342\200\231m
logged in", but it is instead ""
This is because, in `mock_secret_C_Initialize()` we assign two sets of
fields to the mock module, one with `CKA_G_LOGIN_COLLECTION` → `CK_TRUE`
and one with it pointing to `CK_FALSE`.
This variable is used to decide, via `is_login_keyring()`, whether to call
`setup_unlock_keyring_login()` or `setup_unlock_keyring_other()`. The
first one sets `choice-label` to the empty string. The second one is
what we want, and upgrading GLib made it flip.
The reason is the same as the previous fix: the mock-secret-store
expects to be able to insert items into a hash table and then iterate it
and get them out in the same order. That was never guaranteed, and now
doesn't happen.
Let's keep a parallel list which keeps track of the order things were
added. And then instead of iterating the hash table, we iterate this
list.
This is a backport of 7aba0e6aadd75fc688bf7f086a620e4dc41da6d0 from
gnome-keyring.
|
|/
|
|
|
|
|
|
|
|
| |
These headers (at least for OpenSSL) must come in this order. We
shouldn't assume that `g_hash_table_foreach` is going to give a
particular ordering - it's not guaranteed, and has changed with GLib
2.59.
This is a cherry-pick of 23fdfe728a27a01ef50affd849be5188c0cda954 from
gnome-keyring.
|
|\
| |
| |
| |
| | |
Update gcr_pkcs11_get_trust_{store|lookup}_slot URI checks
See merge request GNOME/gcr!5
|
|/
|
|
|
|
|
|
|
|
| |
No store/lookup URIs may be present, even after initialising them, if no
appropriate stores are found. Check this is the case before attempting
to use them, and clarify in both debug output and the gtkdocs about what
is happening in such cases.
This makes the underlying problem in #10 a bit more obvious when
debugging.
|
|\
| |
| |
| |
| | |
gcr: Don't specify checksum types for certificate fingerprint docs
See merge request GNOME/gcr!6
|
|/
|
|
|
| |
Remove sentences that suggest only SHA1 and MD5 are supported hashes
when getting a certificate's fingerprint.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
system-prompter: Fix use of g_hash_table_lookup_extended
Closes #9
See merge request GNOME/gcr!4
|
|/
|
|
|
|
|
|
| |
Since the glib commit 8dc8b33d, g_hash_table_lookup_extended() started
to clear the argument to NULL, even if the lookup failed. Do not
expect the original key is preserved in that case.
Fixes #9.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| | |
build: Update tap scripts for Python 3 compat
See merge request GNOME/gcr!2
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This replaces tap-driver and tap-gtester with fresh versions from Cockpit.
https://github.com/cockpit-project/cockpit/pull/9500
https://wiki.gnome.org/Initiatives/GnomeGoals/Python3Porting
Also included are the following gnome-keyring commits that are not included in Cockpit:
* https://gitlab.gnome.org/GNOME/gnome-keyring/commit/918ab836fd23f9b2c0bf655c7f4f575bffff3189
* https://gitlab.gnome.org/GNOME/gnome-keyring/commit/7e75a62e846551c19b9c875f7b237a07ee3b93e1
* https://gitlab.gnome.org/GNOME/gnome-keyring/commit/7120f44ceedd5c10802781d64a5829b3c6d8e13f
Basically a copy of https://gitlab.gnome.org/GNOME/gnome-keyring/merge_requests/4
|
|\
| |
| |
| |
| | |
gitlab-ci: Switch the base image from fedora:rawhide to fedora:latest
See merge request GNOME/gcr!3
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|