LIBRESSL-X509_GET_PUBKEY_PARAMETERS(3)

πŸ“¦ version 4.4.0, in alpine 3.24, arch rolling

πŸ’– NAME πŸ’–

Okay bestie, meet X509_get_pubkey_parameters β€” copy public key parameters from a chain. This is the LIBRESSL-X509_GET_PUBKEY_PARAMETERS(3) page from the Library Functions Manual; the source header spells it X509_GET_PUBKEY_PARAMETE(3) (tiny typo, we still love her πŸ’€). It's a libcrypto situation, and yes, she's serving chain-parameter-copying realness. 🫢

✨ SYNOPSIS ✨

library β€œlibcrypto” #include <openssl/x509.h>

int
X509_get_pubkey_parameters(EVP_PKEY *pkey, STACK_OF(X509) *chain);

🌸 DESCRIPTION 🌸

So what does X509_get_pubkey_parameters() do? It copies public key parameters from the first appropriate certificate in the chain. That's the main character move. πŸ’…

Here's the vibe check on pkey:

  • If pkey is not NULL and already contains complete public key parameters, or if it uses an algorithm that does not use any parameters, then no action occurs, and the function indicates success. It does this without inspecting the existing parameters, without inspecting the chain, and without comparing any parameters. Literally not even peeking. πŸ™ˆ

Otherwise, all public key parameters are copied from the first certificate in the chain that contains complete public key parameters to each certificate preceding it in the chain. Unless pkey is a NULL pointer, the same parameters are also copied to pkey. Periodt. ✨

πŸŽ€ RETURN VALUES πŸŽ€

X509_get_pubkey_parameters() returns 1 for success or 0 for failure. That's it, that's the whole report card. πŸ’–

😭 ERRORS 😭

You can retrieve the following diagnostics with ERR_get_error(3), ERR_GET_REASON(3), and ERR_reason_error_string(3):

  • X509_R_UNABLE_TO_GET_CERTS_PUBLIC_KEY β€” "unable to get certs public key" β€” retrieving the public key from a certificate in the chain failed before a certificate containing complete public key parameters could be found.
  • X509_R_UNABLE_TO_FIND_PARAMETERS_IN_CHAIN β€” "unable to find parameters in chain" β€” none of the certificates in the chain contain complete public key parameters.

πŸ¦‹ SEE ALSO πŸ¦‹

Go be nosy, bestie: EVP_PKEY_copy_parameters(3), EVP_PKEY_new(3), X509_get_pubkey(3), X509_new(3). πŸ“š

πŸ‘‘ HISTORY πŸ‘‘

X509_get_pubkey_parameters() first appeared in SSLeay 0.8.0 and has been available since OpenBSD 2.4. She's vintage, she's iconic, she's been in the group chat since forever. πŸ’œ

πŸ’€ CAVEATS πŸ’€

If X509_get_pubkey_parameters() fails and returns 0, a part of the parameters may or may not have been copied before the failure was detected, whereas other parts of pkey and chain may remain unchanged. So in case of failure, the state of the arguments may change and possibly become inconsistent.

So yeah β€” on failure, the arguments can be left in a messy little state, and possibly inconsistent. Not a clean rollback moment, bestie. 🫠


This page is from Debian, dated June 8, 2025, and it lives at X509_GET_PUBKEY_PARAMETERS(3) β€” mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from