[gnutls-devel] GnuTLS | gnutls_x509_trust_list_t should be safely shared among multiple threads (#1212)
Read-only notification of GnuTLS library development activities
gnutls-devel at lists.gnutls.org
Thu Apr 22 17:51:40 CEST 2021
Daiki Ueno created an issue: https://gitlab.com/gnutls/gnutls/-/issues/1212
The documentation about currently says:
```
The GnuTLS library is thread safe by design, meaning that objects of the
library such as TLS sessions, can be safely divided across threads as
long as a single thread accesses a single object. This is sufficient to
support a server which handles several sessions per thread. Read-only
access to objects, for example the credentials holding structures, is
also thread-safe.
```
The last statement implies that the read-only usage of `gnutls_x509_trust_list_t`, such as for verifying certificate chain with already populated list, should be performed from multiple threads against the single `gnutls_x509_trust_list_t` object. This is apparently not true with the use with PKCS#11 trust store:
https://bugzilla.redhat.com/show_bug.cgi?id=1937513#c33
We should either document this as an exception or actually make it thread safe.
--
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/issues/1212
You're receiving this email because of your account on gitlab.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20210422/d289f276/attachment.html>
More information about the Gnutls-devel
mailing list