| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
gck provided some APIs that made working with lists of `GObject`s
easier. GLib has for a long time added API that works well enough for
the same use case, like `g_list_copy_deep()`, `g_list_free_full()` and
more recently also `g_clear_list()`, so use those instead.
This commit also bumps the required GLib version to a more modern 2.64
(which is needed for the `g_clear_list()` API).
|
|
|
|
| |
Automatically define the error quark with this macro.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtk-doc has been slowly dying for the past few years. With gi-docgen we
have a clear successor in sight to replace the voodoo magic one needs to
get the whole documentation setup.
See the [gi-docgen tutorial] for more info on how the system works.
Since we're now only the C compiler (and GIR) parse the C code, that
means we can also get rid of all the special escapes for the # character
in PKCS#11.
[gi-docgen tutorial]: https://gnome.pages.gitlab.gnome.org/gi-docgen/tutorial.html
|
|
|
|
|
|
|
| |
This fixes a few (fatal in gcc 11) warnings, breaking the CI.
For the original discussion on why this change is needed, see
https://gitlab.gnome.org/GNOME/glib/-/issues/600
|
| |
|
| |
|
|
|
|
| |
So you can do things like GCR_CHECK_VERSION(x,y,z)
|
|
|
|
|
|
| |
A gobject-introspection change broke the former.
https://bugzilla.gnome.org/show_bug.cgi?id=693440
|
|
|
|
|
|
|
|
|
| |
* There were problems with applications that didn't use libgck but
linked to the old version with the old libtool number: empathy
* So stub out the removed functions, revert the libtool version changes
instead of removing those functions.
This reverts commit ef7e91d66839d4104ee6ba9681e49506f5dd5fa3.
|
|
|
|
|
|
|
|
|
|
| |
* libgck API is not yet stable.
* Gck is only used internally in the gcr projcet, gnome-keyring project
and the seahorse project.
* We want to be threadsafe with regard to attributes, and the
functions removed can't be implemented within the new framework.
* Remove deprecated functions at the same time, since this is an
opportunity to cleanup.
|
| |
|
|
|
|
|
|
|
|
| |
* The globals for the secure memory pool need to be shared across linked
modules. So that for example gck, gcr, and gsecret libraries can
share the same pool, even though code is compiled into each library.
* There's versioning so they'll only work with each other if they all
share the same code.
|
|
|
|
|
|
| |
* Deprecate the GckModule signals which were used for password auth
* Fire deprecated GckModule signals from a compat GTlsInteraction
* Add some tests for this integration
|
| |
|
|
|
|
| |
* In particular, use guchar * for arrays of bytes.
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=655651
|
|
|
|
|
|
|
|
|
| |
* Allow multiple importers to register, and have a way for
them to identify whether something is importable by the
importer or not.
* Create a new GnuPG keyring importer.
* Add boxed type for a GList of GObject
* Some other minor cleanups.
|
|
|
|
|
| |
* Also fix up Gcr debugging
* And add debugging to trust stuff.
|
| |
|
| |
|
|
|
|
|
| |
Add library-description and library-description and library-manufacturer
parts. And refactor to support parsing in different contexts better.
|
|
|
|
| |
Small grammar and punctuation fixes.
|
|
|
|
|
|
|
| |
There's no way to do a deep copy of a GckMechanisms aka CK_MECHANISM.
The parameter may contain pointers to other memory else where. So we
do a shallow copy instead. The memory is expected to stay around just
like a buffer.
|
|
|
|
|
| |
Add gck_value_to_ulong() and gck_value_to_boolean() to check
and cast CK_BBOOL and CK_ULONG.
|
|
|
|
|
| |
* PKCS#11 URI spec is not completely finalized yet.
* Removed old callback style enumeration and replaced with gio style.
|
|
* Next steps will include cleaning up the API making it ready
for gobject introspection etc..
|