| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
It is not necessary and makes it difficult to interact with GObject introspected
languages.
Signed-off-by: Corentin Noël <corentin.noel@collabora.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
| |
* Don't pass invalid data to the mutex functions in an effort
to test them, while running other tests.
https://bugzilla.gnome.org/show_bug.cgi?id=684476
|
| |
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=680271
|
| |
|
|
|
|
|
|
| |
Many files were missing “Public” in “GNU Lesser General Public License”,
probably due to a mass replace that went a bit too far. Restore the
correct wording in all affected places.
https://bugzilla.gnome.org/show_bug.cgi?id=672187
|
| |
|
|
|
|
| |
* Allows us more flexibility in our API in the future
* Simplifies the common case of generating a set of attributes
and directly passing it to a gck function
|
| |
|
|
|
|
|
|
| |
* Use GckBuilder to build a set of attributes, and then
GckAttributes is a immutable set of attributes.
* We reference count the memory used in attributes, so
as we copy and transfer the attributes without duplicating
values unnecessarily
|
| |
|
|
|
|
|
|
|
|
|
| |
* Move key calculation routines into gcr-subject-public-key.c
* Move creation of SPK from gcr-fingerprint.c into here
* Implement loading of SPK from PKCS#11 certificates, public keys,
private keys
* Add support for parsing SubjectPublicKeyInfo to parser. Generates
attributes for a CKO_PUBLIC_KEY
* Fix bugs in DER encoding related to this.
* More tweaks on testing infrastructure
|
| |
|
|
|
|
|
|
|
| |
* This is especially necessary after migrating to EggBytes
since it's reference counted and an easy sourc of memory leaks
* Remove threading from testing framework, as gcr isn't threadsafe
in all parts.
* Fix bugs discovered in memory checking.
* Fix up some of the testing stuff.
|
| |
|
|
| |
* Held a reference to the session and result, which kept the module
|
| |
|
|
|
|
|
|
|
|
|
| |
Commits prior to this commit will not build. To build
old releases of Gcr or Gck you should use the gnome-keyring
git module.
This module currently depends on: gtk+ >= 3.0, glib >= 2.28.0,
p11-kit >= 0.6, libgcrypt >= 1.2.2
Additionally it requires asn1Parser for building.
|
| |
|
|
| |
* In particular, use guchar * for arrays of bytes.
|
| |
|
|
| |
In particular we can lookup certs by issuer from the PKCS#11 store.
|
| | |
|
| |
|
|
|
|
| |
Add concept of session options, which are different (but sometimes
related to) session PKCS#11 flags. The session options take the
place of module options, which were much harder to use appropriately.
|
|
|
Make mock Pkcs#11 module better modularized, and available to other
tests of other modules. Add more test helpers.
|
