gnutls_x509_tr...erify_named_crt(3)
π gnutls_x509_trust_list_verify_named_crt π
okay so bestie, welcome to the gnutls manual β yes, the gnutls, the manual you're holding right now. This page is gnutls_x509_tr...erify_named_crt(3), and it's literally just about one little function: gnutls_x509_trust_list_verify_named_crt. Let's get into it π«Ά
β¨ NAME β¨
gnutls_x509_trust_list_verify_named_crt β API function
πΈ SYNOPSIS πΈ
#include <gnutls/x509.h>
int gnutls_x509_trust_list_verify_named_crt(gnutls_x509_trust_list_t
list, gnutls_x509_crt_t cert, const void * name, size_t name_size,
unsigned int flags, unsigned int * voutput,
gnutls_verify_output_function func);
π ARGUMENTS π
gnutls_x509_trust_list_t listβ The list. your lil roster of trust, the squad, the guest list at the door πgnutls_x509_crt_t certβ is the certificate to be verified. this is the one we're putting under the microscope, no cap πconst void * nameβ is the certificate's name. the name we're matching against, bestiesize_t name_sizeβ is the certificate's name size. how big that name is, in bytes, pls don't get it wrong πunsigned int flagsβ Flags that may be used to change the verification algorithm. Use OR of thegnutls_certificate_verify_flagsenumerations. mix and match with OR, it's giving custom vibe check β¨unsigned int * voutputβ will hold the certificate verification output. the receipts go here πgnutls_verify_output_function funcβ If non-null will be called on each chain element verification with the output. so like, a little callback that gets pinged for every link in the chain, okay?? π
π¦ DESCRIPTION π¦
This function will try to find a certificate that is associated with the provided name --see gnutls_x509_trust_list_add_named_crt(). If a match is found the certificate is considered valid. Periodt. π―
In addition to that this function will also check CRLs. Not me doing the extra credit, but yes, we do check those. π
The voutput parameter will hold an OR'ed sequence of gnutls_certificate_status_t flags.
Additionally a certificate verification profile can be specified from the ones in gnutls_certificate_verification_profiles_t by ORing the result of GNUTLS_PROFILE_TO_VFLAGS() to the verification flags. slay, custom profiles, we love to see it π
β RETURNS β
On success, GNUTLS_E_SUCCESS (0) is returned, otherwise a negative error value. so like, zero is the good ending, anything negative is the plot twist π
π§ SINCE π§
3.0.0 β she's been iconic since day one, fr fr π
π REPORTING BUGS π
Report bugs to <bugs@gnutls.org>.
Home page: https://www.gnutls.org
π COPYRIGHT π
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. (translation: take it, share it, remix it β just keep the copyright notice and this notice, bestie, that's the whole deal π«Ά)
π 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/
okay that's the whole page!! you ate that π
β¨ this was gnutls version 3.8.13, page gnutls_x509_tr...erify_named_crt(3) β mwah, go verify something cute ππΈπ¦
π¦ where this page comes from
- alpine 3.22: gnutls-doc 3.8.13-r0 Β· LGPL-2.1-or-later
- alpine 3.23: gnutls-doc 3.8.13-r0 Β· LGPL-2.1-or-later
- alpine 3.24: gnutls-doc 3.8.13-r0 Β· LGPL-2.1-or-later
- arch rolling: gnutls 3.8.13-3 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- fedora 43: gnutls-devel 3.8.13-1.fc43 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- fedora 43: gnutls-devel 3.8.13-1.fc43 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- fedora 44: gnutls-devel 3.8.13-1.fc44 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- fedora 44: gnutls-devel 3.8.13-1.fc44 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- ubuntu stonking: gnutls-doc 3.8.13-1ubuntu1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms