After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 750393 - Cannot create GTlsCertificate from PKCS#11
Cannot create GTlsCertificate from PKCS#11
Status: RESOLVED OBSOLETE
Product: glib
Classification: Platform
Component: gio
2.45.x
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2015-06-04 12:24 UTC by David Woodhouse
Modified: 2018-05-24 17:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description David Woodhouse 2015-06-04 12:24:25 UTC 
We appear to have no g_tls_certificate_new_from_pkcs11() function. We should have one.

It should take a PKCS#11 URI according to RFC7512, and automatically use the tokens specified by p11-kit for the currently-running application. No explicit messing with which PKCS#11 modules to load should be necessary.

There might be some merit in g_tls_certificate_new_from_file() actually accepting a PKCS#11 URI as well as a filename — or having *some* function which does so. Then tools which simply have a text field in their configuration that can take a filename *or* a PKCS#11 URI don't need to inspect it to find out which it is and call the appropriate g_tls_certificate_new_from_ function.
Comment 1 Dan Winship 2015-06-21 15:23:15 UTC 
(In reply to David Woodhouse from comment #0)
> There might be some merit in g_tls_certificate_new_from_file() actually
> accepting a PKCS#11 URI as well as a filename

Yeah, the odds of someone having a file whose name was also a valid PKCS#11 URI is pretty negligible, so we could probably get away with that.
Comment 2 GNOME Infrastructure Team 2018-05-24 17:53:10 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/1047.