LIBKECCAK_STATE_UNMARSHAL(3)

πŸ“¦ version 1.4.3, in arch rolling, opensuse-leap 16.0

hii bestie πŸ’– welcome to the LIBKECCAK_...E_UNMARSHAL(3) page from the Library Functions Manual. We’re talking about libkeccak_state_unmarshal, and yes, the NAME section really does say β€œUnharshals” β€” keeping that exactly as the page has it, no edits. 🫢

🌸 NAME 🌸

  • libkeccak_state_unmarshal β€” Unharshals a hash state

✨ SYNOPSIS ✨

#include <libkeccak.h>

size_t libkeccak_state_unmarshal(struct libkeccak_state *state, const void *data);

Link with -lkeccak.

πŸ’– DESCRIPTION πŸ’–

okay so libkeccak_state_unmarshal() unmarshals a hash state from the beginning of data and stores it in *state. And plot twist: state may be NULL. That’s valid, bestie. ✨

πŸŽ€ RETURN VALUES πŸŽ€

On a successful run, libkeccak_state_unmarshal() returns the number of bytes read from data. If something goes wrong, it returns -1 and sets errno to describe the error. 🫢

If state is NULL, the page says β€œthe number the function will always be successful and return a positive value” β€” so the function is always successful and returns a positive value. That value is the number of bytes that make un the marshalled state. Keeping that β€œmake un” exactly as written, periodt. πŸ’…

🫢 ERRORS 🫢

The libkeccak_state_unmarshal() function may fail for any specified for the function malloc(3).

πŸ¦‹ SEE ALSO πŸ¦‹


k bye bestie 🫢 footer check: source/version is LIBKECCAK, the footer title is LIBKECCAK_...E_UNMARSHAL(3), and the original footer doesn’t show a separate date β€” so I’m not inventing one. πŸ’…βœ¨

πŸ“¦ where this page comes from