summaryrefslogtreecommitdiff
path: root/docs
Commit message (Collapse)AuthorAgeFilesLines
* Drop gcr-gtk3 and gcr-gtk4Niels De Graef2022-09-0415-212/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gcr historically consisted of 2 high-level parts: `gcr-base` and `gcr-ui`. `gcr-base` contains the core classes and interfaces to deal with crypto-related items (e.g. `GcrCertificate`), while `gcr-ui` contained GTK widgets to show those items (e.g. `GcrCertificateWidget`). Now: with the move to gcr4, it's becoming more and more clear to that this isn't really a path forward: On one hand, GTK4 has transitioned from a platform toolkit (usually GNOME was the primary target) to one that allows you to build your platform on top (e.g. libadwaita, libgranite, or your very own). Kepeing that in mind, having "GTK-based" widgets for use in general purpose doesn't really make sense, since it will always look out touch on platforms On the other hand, widgets are usually more faster-moving targets in both looks as well as API than an actual library, so in practice gcr-ui has a different lifecycle than gcr-base. Finally, @tintou has been doing an awesome effort to implement an API that allows consumers to write their own widgets, without having to deal with asn1 decoding etc. At this point, I think the certificate widget is likely the only widget we're seeing interest in. As such, this commit drops gcr-gtk3 and gcr-gtk4 as libraries. There's still a gcr-viewer debugging tool as a troubleshooting/debugging tool, that's it. See https://gitlab.gnome.org/GNOME/gcr/-/issues/100 for the related discussion.
* docs: Add a urlmap fileNiels De Graef2022-06-068-0/+28
| | | | | That allows gi-docgen to link types like `GObject` back to the original documentation.
* Add lookup of trust assertions for distrusted certscert-distrustedNiels De Graef2022-06-061-0/+8
| | | | | | | | | | There is one notable type of trust assertions that is not implemented in gcr: those where `CK_X_ASSERTION_TYPE` equals `CKT_X_DISTRUSTED_CERTIFICATE`. This is actually also something needed by Seahorse, as that is showing the infamous "null" certificates due to distrusted certificates being present on the machine, but not having any DER data stored with them.
* gck: use the right namespace for GckUriData methodsCorentin Noël2022-04-091-2/+2
|
* Create gcr-gtk4 libraryCorentin Noël2022-04-093-2/+85
| | | | Signed-off-by: Corentin Noël <corentin.noel@collabora.com>
* Rename gcr-ui into gcr-gtk3Corentin Noël2022-04-0911-10/+10
|
* gcr: Remove gcr-base-3 and make gcr-3 independent of GTKCorentin Noël2022-04-093-7/+7
| | | | Also remove the post-install symlinks
* meson: Declare libversion variables and consistently use itCorentin Noël2022-04-083-8/+8
| | | | | | Do not rely on major_version to manually create the library names. Make sure to be consistent and use a single variable for all the library names and folder mentions.
* docs: Fix cross-documentation linksCorentin Noël2021-11-142-0/+3
| | | | Link to the Gcr and Gck documentation
* docs: Port from gtk-doc to gi-docgenNiels De Graef2021-11-1037-2449/+374
| | | | | | | | | | | | | | 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
* gcr-ssh-agent: Port from gnome-keyringDaiki Ueno2021-03-271-0/+7
| | | | | | This port the ssh-agent support provided as a sub-daemon in gnome-keyring, as a standalone binary, so that it can easily be managed through systemd.
* Remove Autotools buildNiels De Graef2021-01-162-282/+0
| | | | | We have a modern, saner build system in place with Meson, so let's drop autotools before releasing the next version of gcr.
* Support Meson build systemNiels De Graef2019-12-313-0/+114
|
* gcr: Implement GcrSshAskpass APIwip/dueno/ssh-askpassStef Walter2018-02-242-0/+18
| | | | | | | This allows calling ssh programs like ssh-add or ssh itself, and handling the password prompts. https://bugzilla.gnome.org/show_bug.cgi?id=735873
* egg: Move mock-interaction.[ch] to egg/ directoryStef Walter2018-02-151-2/+1
| | | | | | Since we want to use this from the gcr/ code https://bugzilla.gnome.org/show_bug.cgi?id=735873
* Use the g_debug() mechanism from GLib directlyStef Walter2014-09-032-4/+1
| | | | | Rather than using our own _gck_debug() and _gcr_debug() wrappers.
* gck: Add gck_enumerator_set_object_type_full() functionStef Walter2014-03-031-0/+1
| | | | | | | | This is more bindable than setting fields in the GckObjectCacheIface struct directly. Hide the old gck_enumerator_set_object_type() for scripting and introspection using languages.
* gcr: Add gcr_certificate_get_markup() functionStef Walter2014-03-031-0/+1
| | | | | For seahorse to use when implementing its GcrCertificate derived class.
* Makefile.am: Single Makefile mode and parallel-testsStef Walter2014-03-034-10/+6
| | | | | | | | | | | | | | | | gtk-doc doesn't work as an included Makefile so continue to use SUBDIRS with docs/reference/* Run the tests using TAP. Unfortunately the GTest --tap output mode doesn't behave well in the face of failures, and doesn't output a test plan. Use our own tap-driver and tap-compiler for these reasons. This also fixes several builddir != srcdir issues and testing hacks that were sneaking around in the code base. Move the tests into the same directories as the code that it is testing.
* gck: Add an accessor for GckAttribute raw value dataStef Walter2014-03-031-1/+2
| | | | | vapigen is completely broken when it comes to having arrays as fields in a compact class (ie: struct).
* Add version checking macrosStef Walter2014-01-064-1/+21
| | | | So you can do things like GCR_CHECK_VERSION(x,y,z)
* eggimagemenubutton: Copy and un-deprecate GtkImageMenuitemStef Walter2014-01-051-0/+1
| | | | | | | | | This was deprecated without reference to a bug or reasoning, and we need it for our importer drop down button. We want to show the device image in the drop down menu. So copy it from GTK+, clean it up, and keep using it. Add a tool to test GcrImportButton
* Fix up documentation warningsStef Walter2013-10-182-1/+5
|
* Parser: Store imported key filename in Parsed & ParserHashem Nasarat2013-10-071-0/+3
| | | | | | | | | | | | | | | 1. Access to the filename is useful in many ways. Importers, e.g. GcrOpenSshImporter, have access to the GcrParsed, and can read the filename to preserve filenames of imported keys. 2. When the GcrViewerWindow reads a key to create a parser, store the filename as an instance variable of the parser 3. In the parse_...() functions where the GcrParsed is created, store the filename as an instance variable via push_parsed (read it from the parser). https://bugzilla.gnome.org/show_bug.cgi?id=705225
* gcr: Allow using GBytes with GcrParserStef Walter2013-09-301-0/+4
| | | | | | | | | | | | This also solves a corner case where GcrParser would keep around a pointer to the data passed into gcr_parser_parse_data(), even after that data had been freed. gcr_parser_parse_data() now copies the data passed in, where as the new gcr_parser_parse_bytes() simply keeps a reference to the GBytes. https://bugzilla.gnome.org/show_bug.cgi?id=708736
* docs: GcrViewerWindow shouldn't be in the documentation typesStef Walter2013-09-251-1/+0
| | | | Since it's not public API, at least not yet.
* ui: Add gcr_viewer_window_get_viewer() functionStef Walter2013-09-251-0/+1
| | | | This allows frob-unlock tool to start working again.
* Add vala vapi files for Gck and Gcr librariesStef Walter2013-04-211-4/+0
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=689685
* Separate the base and ui parts of the Gcr library more thoroughly.Stef Walter2012-12-221-6/+6
| | | | | | | | | | | | | | | | * This is due to gobject introspection not being able to have separate GIRs provide the same namespace, and the desire to conditionally build the GTK+ dependent stuff. * Partially based on a patch by Mathias Hasselmann * Separate GIRs: Gcr and GcrUi * Separate libraries: libgcr-base-3.so and libgcr-ui-3.so. The latter links to the former. * Symlink libgcr-3.so to libgcr-ui-3.so * Expose internal symbols in libgcr-base-3.so so they can be easily shared by libgcr-ui-3.so * Add --without-gtk argument https://bugzilla.gnome.org/show_bug.cgi?id=688678
* Split up the Gcr GIR files into base/uiStef Walter2012-12-221-1/+1
| | | | | | | | | | | | | | | * Reorganize our libraries too, in a backwards compatible manner, in order to better match this split. * This reorganization was predicated on the fact that we can't have two GIRs with the same namespace. So the two namespaces are: - Gcr - GcrUi * The pkg-config files are: - gcr-base - gcr-ui - gcr (which depends on both of the above) https://bugzilla.gnome.org/show_bug.cgi?id=689685
* Fix more build problems with glib 2.35.0Stef Walter2012-12-052-3/+6
|
* Release version 3.7.13.7.1Stef Walter2012-10-221-1/+1
|
* gcr: Implement prompt-close in GcrSystemPrompt and GcrSystemPrompterStef Walter2012-10-221-0/+1
| | | | | | | | | | | * Properly relay the prompt-close signal from GcrSystemPrompter back to GcrSystemPrompt by firing the PromptDone callback method on the caller's DBus interface. * Make sure GcrSystemPrompt emits prompt-close appropriately for all the various paths that can close the prompt. * Add testing of the above, and changes in the mock prompter for this. https://bugzilla.gnome.org/show_bug.cgi?id=678611
* gcr: Add prompt-close action signal to GcrPromptStef Walter2012-10-221-0/+1
| | | | | | | | | | | * This signal is fired when the prompt is closed, regardless of whether that closure was initiated by the user, or by the the application. * Add a gcr_prompt_close() method to fire this signal. * After closing a prompt the prompt should not display any further password or confirm prompts to the user. https://bugzilla.gnome.org/show_bug.cgi?id=678611
* Documentation fixesStef Walter2012-06-262-4/+11
| | | | | * Clean up documentation and introspection warnings * Separate GcrImportInteraction docs into own page
* Remove interfaces file, should be auto-generated.Stef Walter2012-03-091-1/+0
|
* gcr: Expose secure memory APIStef Walter2012-02-102-0/+14
| | | | | | | * Add gcr_secure_memory_new() and gcr_secure_memory_free() and friends. * Exposed so that we can implement secure entry widget in gnome-shell
* gcr: Add gcr_prompt_reset() functionStef Walter2012-02-102-43/+1
| | | | | * Resets all properties of the prompt to the defaults in the interface
* gcr: Add way to set the labels for the prompt buttonsStef Walter2012-02-101-0/+4
| | | | | | | * Add continue-label and cancel-label properties to GcrPrompt * Implement in GcrSystemPrompt and in the mock prompter https://bugzilla.gnome.org/show_bug.cgi?id=669793
* gcr: Display an appropriate title in gcr-viewerStef Walter2012-01-102-2/+4
| | | | * And add display-name property to GcrViewerWidget
* gcr: Include GcrPrompt stuff in documentationStef Walter2012-01-031-0/+8
|
* gck: Remove gck_attributes_add_owned()Stef Walter2011-12-211-1/+0
| | | | | | * And make gck_attributes_add_attribute() handle owned attributes * Unowned attributes should be done with gck_attributes_add_data() * This change to ABI cleans things up before API is released as stable
* gck: Documentation warning fixesStef Walter2011-12-191-0/+1
|
* gcr: Add timeout to gcr-prompter processStef Walter2011-12-181-0/+1
| | | | * When no prompts occur for 10 seconds, quit process
* gcr: Fix up documentation for recent prompting workStef Walter2011-12-173-2/+134
|
* gcr: Add system prompt and prompterStef Walter2011-12-132-0/+7
| | | | | | | * GcrSystemPrompt is a class used on the client. * GcrSystemPrompter is a base class for implementing the actual prompter * GcrMockPrompter is a mock prompter, which returns predefined values useful in tests
* gcr: Expose GcrSecureEntryBuffer as a public classStef Walter2011-12-133-0/+19
| | | | | * This is a GtkEntryBuffer that uses non-pageable memory for the buffer, to be used with passwords and secrets.
* Revert changes to libtool version and removed APIStef Walter2011-12-092-2/+25
| | | | | | | | | * 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.
* gck: Bump gck libtool version, as we removed interfaces from libgckStef Walter2011-12-082-8/+2
| | | | | | | | | | * 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.
* gck: Add documentation for newly functionsStef Walter2011-12-082-46/+80
|
View Lorry Controller Status