OBJ_NID2OBJ(3ossl)
π OBJ_NID2OBJ π (3ossl)
okay bestie, sit down, hydrate, because we're about to talk about OpenSSL's ASN1 object utility functions and honestly? they're kind of iconic. this is the OBJ_NID2OBJ(3ossl) page, and by the end you're gonna know your NIDs from your OIDs, no cap. π
β¨ NAME β¨
i2t_ASN1_OBJECT, OBJ_length, OBJ_get0_data, OBJ_nid2obj, OBJ_nid2ln, OBJ_nid2sn, OBJ_obj2nid, OBJ_txt2nid, OBJ_ln2nid, OBJ_sn2nid, OBJ_cmp, OBJ_dup, OBJ_txt2obj, OBJ_obj2txt, OBJ_create, OBJ_cleanup, OBJ_add_sigid β these are the ASN1 object utility functions, and they are the girlies for handling object identifiers. π¦
πΈ SYNOPSIS πΈ
#include <openssl/objects.h>
ASN1_OBJECT *OBJ_nid2obj(int n);
const char *OBJ_nid2ln(int n);
const char *OBJ_nid2sn(int n);
int OBJ_obj2nid(const ASN1_OBJECT *o);
int OBJ_ln2nid(const char *ln);
int OBJ_sn2nid(const char *sn);
int OBJ_txt2nid(const char *s);
ASN1_OBJECT *OBJ_txt2obj(const char *s, int no_name);
int OBJ_obj2txt(char *buf, int buf_len, const ASN1_OBJECT *a, int no_name);
int i2t_ASN1_OBJECT(char *buf, int buf_len, const ASN1_OBJECT *a);
int OBJ_cmp(const ASN1_OBJECT *a, const ASN1_OBJECT *b);
ASN1_OBJECT *OBJ_dup(const ASN1_OBJECT *o);
int OBJ_create(const char *oid, const char *sn, const char *ln);
size_t OBJ_length(const ASN1_OBJECT *obj);
const unsigned char *OBJ_get0_data(const ASN1_OBJECT *obj);
int OBJ_add_sigid(int signid, int dig_id, int pkey_id);
and now, the part nobody's happy about: this next function has been deprecated since OpenSSL 1.1.0, and you can hide it entirely by defining OPENSSL_API_COMPAT with a suitable version value β go check openssl_user_macros(7) for that:
void OBJ_cleanup(void);
π DESCRIPTION π
so the ASN1 object utility functions process ASN1_OBJECT structures, which are basically the representation of the ASN1 OBJECT IDENTIFIER (OID) type. for convenience (and honestly, for our sanity), OIDs are usually written in source code as numeric identifiers, aka NIDs. OpenSSL keeps an internal table of OIDs that gets generated when the library is built, and their corresponding NIDs are available as defined constants. for all the functions below, application code should treat all returned values β OIDs, NIDs, or names β as constants. don't be out here editing them, bestie. π
OBJ_nid2obj(),OBJ_nid2ln()andOBJ_nid2sn()convert the NIDnto anASN1_OBJECTstructure, its long name and its short name respectively β orNULLif an error occurred.OBJ_obj2nid(),OBJ_ln2nid(),OBJ_sn2nid()return the corresponding NID for the objecto, the long namelnor the short namesnrespectively β orNID_undefif an error occurred.OBJ_txt2nid()returns the NID corresponding to the text strings.scan be a long name, a short name, or the numerical representation of an object.OBJ_txt2obj()converts the text stringsinto anASN1_OBJECTstructure. ifno_nameis0then long names and short names will be interpreted as well as numerical forms. ifno_nameis1, only the numerical form is acceptable.OBJ_obj2txt()converts theASN1_OBJECTainto a textual representation. unlessbufisNULL, the representation is written as a NUL-terminated string tobuf, where at mostbuf_lenbytes are written, truncating the result if necessary. in any case it returns the total string length, excluding the NUL character, required for non-truncated representation β or-1on error. ifno_nameis0then if the object has a long or short name then that will be used, otherwise the numerical form will be used. ifno_nameis1then the numerical form will always be used.i2t_ASN1_OBJECT()is the same asOBJ_obj2txt()with theno_nameset to zero. π«OBJ_cmp()comparesatob. if the two are identical,0is returned.OBJ_dup()returns a copy ofo. two of her! πOBJ_create()adds a new object to the internal table.oidis the numerical form of the object,snthe short name andlnthe long name. a new NID is returned for the created object in case of success andNID_undefin case of failure. any ofoid,snandlnmay beNULL, but not all at once. (all three NULL is giving chaos, and not the cute kind.)OBJ_length()returns the size of the content octets ofobj.OBJ_get0_data()returns a pointer to the content octets ofobj. the returned pointer is an internal pointer which must not be freed. hands off, okay? π«ΆOBJ_add_sigid()creates a new composite "Signature Algorithm" that associates a given NID with two other NIDs β one representing the underlying signature algorithm and the other representing a digest algorithm to be used in conjunction with it.signidrepresents the NID for the composite "Signature Algorithm",dig_idis the NID for the digest algorithm andpkey_idis the NID for the underlying signature algorithm. since there are signature algorithms that do not require a digest,NID_undefis a validdig_id.OBJ_cleanup()releases any resources allocated by creating new objects.
π NOTES π
objects in OpenSSL can have a short name, a long name and a numerical identifier (NID) associated with them. a standard set of objects is represented in an internal table. the appropriate values are defined in the header file objects.h.
for example the OID for commonName has the following definitions:
#define SN_commonName "CN"
#define LN_commonName "commonName"
#define NID_commonName 13
new objects can be added by calling OBJ_create().
table objects have certain advantages over other objects: for example their NIDs can be used in a C language switch statement. they are also static constant structures which are shared: that is, there is only a single constant structure for each table object. one shared girlie, many admirers. π
objects which are not in the table have the NID value NID_undef.
objects do not need to be in the internal tables to be processed β OBJ_txt2obj() and OBJ_obj2txt() can process the numerical form of an OID.
some objects are used to represent algorithms which do not have a corresponding ASN.1 OBJECT IDENTIFIER encoding (for example no OID currently exists for a particular algorithm). as a result they cannot be encoded or decoded as part of ASN.1 structures. applications can determine if there is a corresponding OBJECT IDENTIFIER by checking that OBJ_length() is not zero.
these functions cannot return const because an ASN1_OBJECT can represent both an internal, constant, OID and a dynamically-created one. the latter cannot be constant because it needs to be freed after use.
β οΈ heads up: these functions were not thread safe in OpenSSL 3.0 and before. old news, but important news.
β RETURN VALUES β
OBJ_nid2obj()returns anASN1_OBJECTstructure orNULLif an error occurred.OBJ_nid2ln()andOBJ_nid2sn()return a valid string orNULLon error.OBJ_obj2nid(),OBJ_ln2nid(),OBJ_sn2nid()andOBJ_txt2nid()return a NID orNID_undefon error.OBJ_add_sigid()returns1on success or0on error.i2t_ASN1_OBJECT()andOBJ_obj2txt()return-1on error. on success, they return the length of the string written tobufifbufis notNULLandbuf_lenis big enough, otherwise the total string length. note that this does not count the trailing NUL character. (the NUL is free, babes. it just doesn't get counted.) π
π¦ EXAMPLES π¦
create an object for commonName:
ASN1_OBJECT *o = OBJ_nid2obj(NID_commonName);
check if an object is commonName:
if (OBJ_obj2nid(obj) == NID_commonName)
/* Do something */
create a new NID and initialize an object from it:
int new_nid = OBJ_create("1.2.3.4", "NewOID", "New Object Identifier");
ASN1_OBJECT *obj = OBJ_nid2obj(new_nid);
create a new object directly:
obj = OBJ_txt2obj("1.2.3.4", 1);
π SEE ALSO π
π HISTORY π
OBJ_cleanup() was deprecated in OpenSSL 1.1.0 by OPENSSL_init_crypto(3) and should not be used. she's retired, let her rest. π
π COPYRIGHT π
Copyright 2002-2021 The OpenSSL Project Authors. All Rights Reserved.
Licensed under the Apache License 2.0 (the "License"). You may not use this file except in compliance with the License. You can obtain a copy in the file LICENSE in the source distribution or at <https://www.openssl.org/source/license.html>.
and that's the whole page, bestie β this was OBJ_NID2OBJ(3ossl) from OpenSSL 3.5.9, dated 2026-09-29. go forth and identify your objects responsibly. mwah. πβ¨π
π¦ where this page comes from
- fedora 43: openssl-devel 1:3.5.9-1.fc43 Β· Apache-2.0
- fedora 43: openssl-devel 1:3.5.9-1.fc43 Β· Apache-2.0
- fedora 44: openssl-devel 1:3.5.9-1.fc44 Β· Apache-2.0
- fedora 44: openssl-devel 1:3.5.9-1.fc44 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms