KCAPI_MEMSET_SECURE(3)

πŸ’– KCAPI_MEMSET_SECURE πŸ’–

okay so bestie, welcome to kcapi_memset_secure β€” part of the libkcapi programming interface (that's the manual we're living in today, mwah) πŸ’…


✨ NAME ✨

kcapi_memset_secure β€” a memset implementation that will not get optimized away by the compiler 🫢

like. it sets memory. but it stays set. the compiler cannot gaslight you about it. iconic behaviour only.


🌸 SYNOPSIS 🌸

void kcapi_memset_secure(void * s, int c, size_t n);

πŸŽ€ ARGUMENTS πŸŽ€

ngl bestie, all three of these are just the memset(3) ones. no new lore. go read that page if you need the tea. πŸ“


πŸ’œ DESCRIPTION πŸ’œ

The parameters, the logic, and the return code are identical to memset(3).

that's it. that's the whole vibe. it's memset but the compiler can't delete it behind your back and pretend nothing happened πŸ’€


πŸ‘‘ AUTHOR πŸ‘‘

Stephan Mueller <smueller@chronox.de>

  • Author. 🫑

this is where the legal girlies live β€” the page belongs to the libkcapi Manual, version 1.5.0, dated July 2025, and the manual page name is KCAPI_MEMSET_SECURE(3).

and that's the whole page bestie, no cap πŸ’– libkcapi Manual 1.5.0, July 2025, KCAPI_MEMSET_SECURE(3) β€” slay, go forth and securely zero your buffers, periodt βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from