BYTE_EQUAL_NOTIMINGATTACK(3)
β¨ NAME β¨
byte_equal_notimingattack β bestie, it compares two strings π
π SYNTAX π
okay so first you gotta pull in the header, like:
#include <libowfat/byte.h>
and then the function itself is literally this:
int byte_equal_notimingattack(const char *one,size_t len,const char
*two);
π¦ DESCRIPTION π¦
So byte_equal_notimingattack is giving β¨comparison functionβ¨. It returns 1 if the strings are equal, and 0 otherwise. That's it, that's the whole vibe check π«Ά
But here's the iconic part, the main character energy π: when the strings are different, byte_equal_notimingattack will still read and compare all the other bytes. The way that it does not just bail early?? Obsessed. π
Why does that matter, you ask? Because an attacker who's watching the timing of the execution can not learn where the first mismatch occurred. No little timing breadcrumb trail, no sneaky hint, no cap. π
πΈ SEE ALSO πΈ
and that's the whole page, bestie π§ footer era: this one lives in the Library Functions Manual, and the footer just echoes the truncated name byte_equal...imingattack(3) back at you like a little goodbye kiss π no extra source/version or date tea on this page, fr fr.
π¦ where this page comes from
- alpine 3.24: libowfat-doc 0.34-r0 Β· GPL-2.0-only
- nixos 26.05: libowfat 0.34
- nixpkgs unstable: libowfat 0.34
- opensuse-leap 16.0: libowfat-devel 0.33-bp160.1.11 Β· GPL-2.0-only
- opensuse-leap 16.0: libowfat-devel 0.33-bp160.1.11 Β· GPL-2.0-only
- opensuse-leap 16.0: libowfat-devel 0.33-bp160.1.11 Β· GPL-2.0-only
- opensuse-leap 16.0: libowfat-devel 0.33-bp160.1.11 Β· GPL-2.0-only
- ubuntu resolute: libowfat-dev 0.34-2 Β· GPL-2.0-only
- ubuntu stonking: libowfat-dev 0.34-2 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms