ecryptfs_ve...tok_from_key(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ecryptfs_verify_auth_tok_from_key β€” Kernel API Manual ✨

okay bestie, so this little cutie lives in the Kernel API Manual and its whole personality is: "is this auth token actually valid or are we being catfished?" πŸ•΅οΈβ€β™€οΈ That's it. That's the vibe. Let's get into it πŸ’–


🌸 SYNOPSIS 🌸

int ecryptfs_verify_auth_tok_from_key (struct key *auth_tok_key , struct
ecryptfs_auth_tok **auth_tok );

no cap, that's literally the whole signature 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • auth_tok_key β€” the struct key * that's holding the authentication token. it's giving "the bag where the token lives" πŸ‘œ
  • auth_tok β€” the authentication token itself, handed over as a struct ecryptfs_auth_tok **. double pointer moment, main character energy ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the tea, bestie πŸ“: this function does a vibe check on your auth tok and reports back like the world's most honest group chat.

  • Returns zero on a valid auth tok β€” slay, we're so back πŸ‘‘
  • -EINVAL if the payload is invalid β€” literally not it, the payload is sus 😭
  • -EKEYREVOKED if the key was revoked before we acquired its semaphore β€” awkward timing fr fr, the semaphore came in late and the key already got the boot πŸ’€
⚠️ watch those two negative returns carefully, bestie β€” -EINVAL and -EKEYREVOKED mean two totally different things and you do not wanna mix them up πŸ™ˆ

🌈 SEE ALSO 🌈

the whole friend group, all in the kernel file ./fs/ecryptfs/keystore.c β€” go say hi 🫢


and that's the whole page, bestie πŸ§šπŸ’œ this icon of a manpage came from ./fs/ecryptfs, dated October 2026 β€” bookmark it, screenshot it, put it on your mood board πŸ’…βœ¨

πŸ“¦ where this page comes from