gnutls_sign_set_secure_for_certs(3)

📦
version 3.8.13 · 7 versions
, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, fedora 43, fedora 44, ubuntu stonking

💖 gnutls_sign_set_secure_for_certs — the manual page, but make it make sense 💖

okay bestie, so this is one of the gnutls pages, and it's a very specific little function. like, niche-niche. but we're gonna slay it anyway. 🎀

✨ NAME ✨

gnutls_sign_set_secure_for_certs — it's an API function, bestie. that's the whole name. 💅

🌸 SYNOPSIS 🌸

#include <gnutls/gnutls.h>

int gnutls_sign_set_secure_for_certs(gnutls_sign_algorithm_t sign,
unsigned int secure);

🦋 ARGUMENTS 🦋

  • gnutls_sign_algorithm_t sign — the sign algorithm in question, the one we're talking about, the main character of this function 💫
  • unsigned int secure — whether we're marking that sign algorithm as secure for certificates. yes or no, secure or not, that's the vibe check right there 🌈

👑 DESCRIPTION 👑

okay so here's the tea. this function modifies the previous system-wide setting that marked sign as secure or insecure for use in certificates. like, you're going in and changing what was already decided. iconic behaviour, honestly. ✨

but — and this is the big but — calling this function is only allowed if allowlisting mode is set in the configuration file, AND only if the system-wide TLS priority string has not been initialized yet. so if you've already initialized that thing? nope. sorry bestie. 🙈

the intended usage is to give applications a way to expressly deviate from the distribution or site defaults that they inherited from the configuration file. like, the distro said one thing, and your app is like "actually no, i'm built different." 💅 and the modification is composable with further modifications performed through the priority string mechanism — they stack, they layer, they coexist. no cap. 🫶

⚠️ IMPORTANT, FR FR: this function is not thread-safe. it is intended to be called in the main thread at the beginning of the process execution. do not be out here calling it from a random thread in the middle of everything, that's not the move. 😭

and now the part where you gotta read carefully, because the words are doing a lot:

  • when secure is true, sign is marked as secure for any use — unlike gnutls_sign_set_secure(). 👀
  • otherwise (when secure is not true), it is marked as insecure only for the use in certificates.

so if you want to mark it insecure for any uses, you need to use gnutls_sign_set_secure() instead. different function, different job. iykyk. 🧚

⭐ RETURNS ⭐

0 on success, or a negative error code otherwise. so basically: zero = we ate, negative = we did not eat. 💀

🎀 SINCE 🎀

3.7.3 — she's been around a minute, but she's still cute. 🌸

💜 REPORTING BUGS 💜

found a bug? report it, bestie, don't just sit on it:

Copyright © 2001-2023 Free Software Foundation, Inc., and others.

Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. so like, go off, just keep the receipts. 🫶

🔥 SEE ALSO 🔥

The full documentation for gnutls is maintained as a Texinfo manual. If the /usr/share/doc/gnutls/ directory does not contain the HTML form, visit:

https://www.gnutls.org/manual/

and that's the whole page, bestie. you now know everything there is to know about gnutls_sign_set_secure_for_certs. go forth and configure responsibly. 💖

this has been the gnutls manual, version 3.8.13 — mwah, bye, ily, go read the Texinfo manual if you want more. 💅✨

📦 where this page comes from