OPENSSL_HEXCHAR2INT(3SSL)
β¨ NAME β¨
ok so bestie, this page is from the OpenSSL manual, section 3SSL, and it's all about OPENSSL_hexchar2int, OPENSSL_hexstr2buf_ex, OPENSSL_hexstr2buf, OPENSSL_buf2hexstr_ex, OPENSSL_buf2hexstr β the hex encoding and decoding functions. hexy little squad, truly iconic π
πΈ SYNOPSIS πΈ
#include <openssl/crypto.h>
int OPENSSL_hexchar2int(unsigned char c);
int OPENSSL_hexstr2buf_ex(unsigned char *buf, size_t buf_n, long *buflen,
const char *str, const char sep);
unsigned char *OPENSSL_hexstr2buf(const char *str, long *len);
int OPENSSL_buf2hexstr_ex(char *str, size_t str_n, size_t *strlength,
const unsigned char *buf, long buflen,
const char sep);
char *OPENSSL_buf2hexstr(const unsigned char *buf, long buflen);
like. look at them. five little guys and every one of them is serving π
π¦ DESCRIPTION π¦
OPENSSL_hexchar2int()β takes one hex character and turns it into its numeric equivalent. glow up from char to int, no cap β¨OPENSSL_hexstr2buf_ex()β decodes the hex stringstrand drops the resulting string of bytes into the givenbuf. the charactersepis the separator between the bytes, and setting it to'\0'means there is no separator at all.buf_ngives the size of the buffer. ifbuflenis notNULL, it gets filled in with the result length. wanna know how big the result is gonna be before you commit? call this function withNULLforbuf, that's the vibe check π«Ά. also: colons sitting between two-character hex "bytes" are accepted and just ignored. an odd number of hex digits is an error, periodt π€OPENSSL_hexstr2buf()β does the same thing asOPENSSL_hexstr2buf_ex(), but it allocates the space for the result and returns the result. it uses a default separator of':'. the memory is allocated by callingOPENSSL_malloc()and should be released by callingOPENSSL_free(). please free your memory bestie, i'm begging πOPENSSL_buf2hexstr_ex()β the other direction, we love a reversible moment π«. encodes the contents of the givenbufwith lengthbuflenand places the resulting hexadecimal character string in the givenstr. the charactersepis the separator between the bytes, and setting it to'\0'means there is no separator.str_ngives the size of the of the string buffer. ifstrlengthis notNULL, it gets filled in with the result length. and to find out how large the result will be, call this function withNULLforstrβ same trick, different direction π₯OPENSSL_buf2hexstr()β does the same thing asOPENSSL_buf2hexstr_ex(), but it allocates the space for the result and returns the result. it uses a default separator of':'. the memory is allocated by callingOPENSSL_malloc()and should be released by callingOPENSSL_free()π§
π RETURN VALUES π
OPENSSL_hexchar2intβ returns the value of a decoded hex character, or-1on error πOPENSSL_buf2hexstr()andOPENSSL_hexstr2buf()β return a pointer to allocated memory, orNULLon error πOPENSSL_buf2hexstr_ex()andOPENSSL_hexstr2buf_ex()β return1on success, or0on error. yes bestie, just1and0, they're not being extra about it π
π COPYRIGHT π
Copyright 2016-2022 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>.
ok and that's the whole thing, you ate it up fr fr π this was OpenSSL version 4.0.3, dated 2026-09-29, from the OPENSSL_HEXCHAR2INT(3SSL) manual page. stan hex functions, they're so real for this πβ¨πΈ
π¦ where this page comes from
- ubuntu stonking: libssl-doc 4.0.3-1ubuntu1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms