LIBKECCAK_HMAC_FAST_DESTROY(3)
π NAME π
libkeccak_hmac_fast_destroy β bestie, this one destroys an HMAC-hashing state without erasure π«Ά
β¨ SYNOPSIS β¨
#include <libkeccak.h>
void libkeccak_hamc_fast_destroy(struct libkeccak_hmac_state *state);
Link with -lkeccak.
ok so real talk β yes, the synopsis literally says libkeccak_hamc_fast_destroy, and no, that is not me typo-ing, that's what the page says. Copy it exactly as written, iykyk π
π DESCRIPTION π
So the libkeccak_hmac_fast_destroy() function releases the allocations stored in *state β but not the allocation of state itself. Like, the stuff inside the box? gone. The box? still your problem, bestie π
And the loud part, the part where I need you to pay attention: libkeccak_hmac_fast_destroy() does not securely erase sensitive data. It's the fast version, not the safe-and-scrubbed version. No cap, if there's secret material in there, this function is just gonna walk away and leave it sitting there π
β RETURN VALUES β
The libkeccak_hmac_fast_destroy() function does not return any value. It's a void girlie β gives you nothing back, not even a little nod πΈ
π ERRORS π
The libkeccak_state_fast_destroy() function cannot fail. Iconic behaviour, honestly β no error paths, no drama, it just does the thing π
π¦ SEE ALSO π¦
libkeccak_hmac_fast_free(3)libkeccak_hmac_destroy(3)libkeccak_hmac_initialise(3)libkeccak_hmac_reset(3)libkeccak_hmac_wipe(3)
made with love by the libkeccak girlies π§ β this masterpiece lives in the Library Functions Manual, section 3, LIBKECCAK_...AST_DESTROY(3), brought to you by LIBKECCAK. mwah πππ
π¦ where this page comes from
- arch rolling: libkeccak 1.4.3-1 Β· custom:ISC
- opensuse-leap 16.0: libkeccak-devel 1.4-bp160.1.13 Β· ISC
- opensuse-leap 16.0: libkeccak-devel 1.4-bp160.1.13 Β· ISC
- opensuse-leap 16.0: libkeccak-devel 1.4-bp160.1.13 Β· ISC
- opensuse-leap 16.0: libkeccak-devel 1.4-bp160.1.13 Β· ISC
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms