asn1_expand_octet_string(3)
β¨ asn1_expand_octet_string(3) β¨
okay so bestie, you're in the libtasn1 manual (we're on version 4.21.0 btw, iconic) and this page is literally all about the asn1_expand_octet_string API function. she's a glow-up function. let's get into it π
πΈ NAME πΈ
asn1_expand_octet_string β it's an API function, periodt β¨
π¦ SYNOPSIS π¦
#include <libtasn1.h>
int asn1_expand_octet_string(asn1_node_const definitions, asn1_node *
element, const char * octetName, const char * objectName);
copy that include, bestie, you need it fr fr π«Ά
π ARGUMENTS π
asn1_node_const definitionsβ the ASN1 definitions. your whole little schema situation πasn1_node * elementβ a pointer to an ASN1 structure. she's pointing, she's serving directions πββοΈconst char * octetNameβ the name of theOCTET STRINGfield that we're gonna expand. that's the one getting the glow-up β¨const char * objectNameβ the name of theOBJECT IDENTIFIERfield that tells us which type to use for the expansion. she's the main character that decides everything π
π DESCRIPTION π
so what she actually does: she expands an "OCTET STRING" element inside a structure that came out of a DER decoding process β like, the one you got from the asn1_der_decoding() function. iykyk π
and the type she uses for that expansion? it's the first one that follows the definition of the actual value of the OBJECT IDENTIFIER that's pointed at by OBJECTNAME. that's the whole vibe check right there π
β RETURNS β
ASN1_SUCCESSβ substitution went okay, ate and left no crumbs πASN1_ELEMENT_NOT_FOUNDβ if objectName or octetName are not correct. wrong names, bestie, not the move πASN1_VALUE_NOT_VALIDβ if it wasn't possible to find the type to use for expansion π- or other errors depending on DER decoding. yeah, there's more, it depends π
π COPYRIGHT π
Copyright Β© 2006-2025 Free Software Foundation, Inc..
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. slay, that's the whole license, go off π
π§ SEE ALSO π§
The full documentation for libtasn1 is maintained as a Texinfo manual. If the info and libtasn1 programs are properly installed at your site, the command
info libtasn1
should give you access to the complete manual. As an alternative you may obtain the manual from:
https://www.gnu.org/software/libtasn1/manual/
ngl bestie, if info libtasn1 doesn't hit, that URL is right there. no cap π«Ά
and that's the page!! brought to you by libtasn1 version 4.21.0, page asn1_expand_octet_string(3). stay hydrated, read your manuals, mwah ππβ¨
π¦ where this page comes from
- alpine 3.22: libtasn1-doc 4.21.0-r0 Β· LGPL-2.1-or-later
- alpine 3.23: libtasn1-doc 4.21.0-r0 Β· LGPL-2.1-or-later
- alpine 3.24: libtasn1-doc 4.21.0-r0 Β· LGPL-2.1-or-later
- arch rolling: libtasn1 4.21.0-1 Β· GPL-3.0-or-later AND LGPL-2.1-or-later AND GFDL-1.3-or-later
- fedora 43: libtasn1-devel 4.21.0-1.fc43 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- fedora 43: libtasn1-devel 4.21.0-1.fc43 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- fedora 44: libtasn1-devel 4.21.0-1.fc44 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- fedora 44: libtasn1-devel 4.21.0-1.fc44 Β· GPL-3.0-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: libtasn1-devel 4.21.0-160000.1.1 Β· GFDL-1.3-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: libtasn1-devel 4.21.0-160000.1.1 Β· GFDL-1.3-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: libtasn1-devel 4.21.0-160000.1.1 Β· GFDL-1.3-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: libtasn1-devel 4.21.0-160000.1.1 Β· GFDL-1.3-or-later AND LGPL-2.1-or-later
- ubuntu resolute: libtasn1-6-dev 4.21.0-2
- ubuntu stonking: libtasn1-6-dev 4.21.0-2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms