X509_PUBKEY_NEW(3)
π NAME π
okay so bestie, welcome to X509_PUBKEY_NEW(3) from the Library Functions Manual β this is the whole squad: X509_PUBKEY_new, X509_PUBKEY_free, X509_PUBKEY_set, X509_PUBKEY_get0, X509_PUBKEY_get, d2i_X509_PUBKEY, i2d_X509_PUBKEY, d2i_PUBKEY, i2d_PUBKEY, d2i_PUBKEY_bio, d2i_PUBKEY_fp, i2d_PUBKEY_fp, i2d_PUBKEY_bio, X509_PUBKEY_set0_param, X509_PUBKEY_get0_param β all about the X.509 SubjectPublicKeyInfo structure. periodt π
πΈ SYNOPSIS πΈ
first things first: you're on libcrypto energy, and you're pulling in <openssl/x509.h>. here's the whole function lineup, exactly as it is:
library βlibcryptoβ #include <openssl/x509.h>
X509_PUBKEY *
X509_PUBKEY_new(void);
void
X509_PUBKEY_free(X509_PUBKEY *a);
int
X509_PUBKEY_set(X509_PUBKEY **x, EVP_PKEY *pkey);
EVP_PKEY *
X509_PUBKEY_get0(X509_PUBKEY *key);
EVP_PKEY *
X509_PUBKEY_get(X509_PUBKEY *key);
X509_PUBKEY *
d2i_X509_PUBKEY(X509_PUBKEY **val_out, const unsigned char **der_in,
long length);
int
i2d_X509_PUBKEY(X509_PUBKEY *val_in, unsigned char **der_out);
EVP_PKEY *
d2i_PUBKEY(EVP_PKEY **val_out, const unsigned char **der_in,
long length);
int
i2d_PUBKEY(EVP_PKEY *val_in, unsigned char **der_out);
EVP_PKEY *
d2i_PUBKEY_bio(BIO *bp, EVP_PKEY **val_out);
EVP_PKEY *
d2i_PUBKEY_fp(FILE *fp, EVP_PKEY **val_out);
int
i2d_PUBKEY_fp(FILE *fp, EVP_PKEY *val_in);
int
i2d_PUBKEY_bio(BIO *bp, EVP_PKEY *val_in);
int
X509_PUBKEY_set0_param(X509_PUBKEY *pub, ASN1_OBJECT *aobj, int ptype,
void *pval, unsigned char *penc, int penclen);
int
X509_PUBKEY_get0_param(ASN1_OBJECT **ppkalg, const unsigned char **pk,
int *ppklen, X509_ALGOR **pa, X509_PUBKEY *pub);
π¦ DESCRIPTION π¦
The X509_PUBKEY structure represents the ASN.1 SubjectPublicKeyInfo structure defined in RFC 5280 section 4.1 and used in certificates and certificate requests. it's literally the main character of public-key packaging, no cap π₯
X509_PUBKEY_new()β allocates and initializes anX509_PUBKEYstructure. fresh out the box β¨X509_PUBKEY_free()β frees up theX509_PUBKEYstructurea. Ifais aNULLpointer, no action occurs. so ifaisNULL, it's giving "nothing to see here" πX509_PUBKEY_set()β sets the public key in*xto the public key contained in theEVP_PKEYstructurepkey. If*xis notNULL, any existing public key structure will be freed. it's a glow-up with cleanup π§X509_PUBKEY_get0()β returns the public key contained inkey. The returned value is an internal pointer which must not be freed after use.
bestie, that "internal pointer" part is serious: do not free it after use. it's borrowed, not yours π
X509_PUBKEY_get()β similar toX509_PUBKEY_get0()except that the reference count on the returned key is incremented so it must be freed usingEVP_PKEY_free(3)after use. so this one is yours to clean up π«Άd2i_X509_PUBKEY(),i2d_X509_PUBKEY(),d2i_PUBKEY(), andi2d_PUBKEY()β decode and encode an ASN.1 SubjectPublicKeyInfo structure using either theX509_PUBKEYor theEVP_PKEYobject type, respectively. For details about the semantics, examples, caveats, and bugs, seeASN1_item_d2i(3).d2i_PUBKEY_bio(),d2i_PUBKEY_fp(),i2d_PUBKEY_bio()andi2d_PUBKEY_fp()β similar tod2i_PUBKEY()andi2d_PUBKEY()except they decode or encode using aBIOorFILEpointer. same vibe, different I/O bestie πX509_PUBKEY_set0_param()β sets the public key parameters ofpub. The OID associated with the algorithm is set toaobj. The type of the algorithm parameters is set toptypeusing the structurepval. The encoding of the public key itself is set to thepenclenbytes contained in bufferpenc. On success ownership of all the supplied parameters is passed topubso they must not be freed after the call.
okay this is the big one: on success, ownership of all the supplied parameters is passed to pub, so you must not free them after the call. not even a little. not even ironically π
X509_PUBKEY_get0_param()β retrieves the public key parameters frompub.*ppkalgis set to the associated OID and the encoding consists of*ppklenbytes at*pk, and*pais set to the associatedAlgorithmIdentifierfor the public key. If the value of any of these parameters is not required, it can be set toNULL. All of the retrieved pointers are internal and must not be freed after the call.
again: all of the retrieved pointers are internal, so do not free them after the call. borrowed pointers stay borrowed, iykyk π
β RETURN VALUES β
- If the allocation fails,
X509_PUBKEY_new()returnsNULLand sets an error code that can be obtained byERR_get_error(3). Otherwise it returns a pointer to the newly allocated structure. X509_PUBKEY_get0()returns an internal pointer orNULLif an error occurs.X509_PUBKEY_get()returns a pointer to an object that had its reference count incremented orNULLif an error occurs.d2i_X509_PUBKEY(),d2i_PUBKEY(),d2i_PUBKEY_bio(), andd2i_PUBKEY_fp()return a pointer to a valid object orNULLif an error occurs.i2d_X509_PUBKEY()andi2d_PUBKEY()return the number of bytes successfully encoded or a negative value if an error occurs.X509_PUBKEY_set(),X509_PUBKEY_set0_param(),X509_PUBKEY_get0_param(),i2d_PUBKEY_fp(), andi2d_PUBKEY_bio()return1for success and0if an error occurred.
π ERRORS π
After failure of X509_PUBKEY_get0() or X509_PUBKEY_get(), one of the following diagnostics can be retrieved with ERR_get_error(3), ERR_GET_REASON(3), and ERR_reason_error_string(3):
X509_R_UNSUPPORTED_ALGORITHMβ"unsupported algorithm"β the public key uses an algorithm unsupported byEVP_PKEY_set_type(3).X509_R_METHOD_NOT_SUPPORTEDβ"method not supported"β while the algorithm is known toEVP_PKEY_set_type(3), using it for decoding is not supported.X509_R_PUBLIC_KEY_DECODE_ERRORβ"public key decode error"β decoding the public key failed.ERR_R_MALLOC_FAILUREβ"malloc failure"β memory was exhausted when trying to allocate the newEVP_PKEYobject.
If key is NULL or does not contain a public key, these functions fail but no error is pushed onto the stack. so it's a fail with no receipts π
π SEE ALSO π
π STANDARDS π
RFC 5280: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
π HISTORY π
X509_PUBKEY_new()andX509_PUBKEY_free()appeared in SSLeay 0.4 or earlier.d2i_X509_PUBKEY()andi2d_X509_PUBKEY()first appeared in SSLeay 0.5.1.X509_PUBKEY_set()andX509_PUBKEY_get()first appeared in SSLeay 0.8.0. These functions have been available since OpenBSD 2.4.d2i_PUBKEY()andi2d_PUBKEY()first appeared in OpenSSL 0.9.5 and have been available since OpenBSD 2.7.d2i_PUBKEY_bio(),d2i_PUBKEY_fp(),i2d_PUBKEY_fp(), andi2d_PUBKEY_bio()first appeared in OpenSSL 0.9.6 and have been available since OpenBSD 2.9.X509_PUBKEY_set0_param()andX509_PUBKEY_get0_param()first appeared in OpenSSL 1.0.0 and have been available since OpenBSD 4.9.X509_PUBKEY_get0()first appeared in OpenSSL 1.1.0 and has been available since OpenBSD 6.3.
source/version: Debian Β· date: June 8, 2025 Β· page: X509_PUBKEY_NEW(3) β okay that's the whole page bestie, love you, bye π«Άπβ¨
π¦ where this page comes from
- alpine 3.24: libressl-doc 4.3.1-r0 Β· custom
- arch rolling: libressl 4.4.0-1 Β· ISC AND custom:OpenSSL
- Copyright (c) 2020, 2021 Ingo Schwarze <schwarze@openbsd.org>
- Copyright (c) 2016 The OpenSSL Project. All rights reserved
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms