ecryptfs_fin..._tok_for_sig(9)
πΈ NAME πΈ
ok so bestie, this is ecryptfs_find_auth_tok_for_sig β and like, the manpage literally gives us no description after the dash π so we're just gonna roll with the name and let the rest of the page do the talking, iykyk.
This one lives in the Kernel API Manual, in case you were wondering where to file it in your brain π§ β¨
β¨ SYNOPSIS β¨
int ecryptfs_find_auth_tok_for_sig (struct key **auth_tok_key , struct
ecryptfs_auth_tok **auth_tok , struct ecryptfs_mount_crypt_stat
*mount_crypt_stat , char *sig );
four args, one int return, and honestly the signature alone is giving main character energy π
π«Ά ARGUMENTS π«Ά
auth_tok_keyβ the key that's holding the authentication token, bestie. that's it, that's the whole vibe πauth_tokβ gets set to the matchingauth_tok. and if nothing matches? it'sNULL. no cap, that's the not-found state πmount_crypt_statβ the inode crypt_stat crypto context. like, the whole context of the operation, okay πsigβ the sig of theauth_tokyou're trying to find. yes, the sig belongs to the auth_tok. that's the assignment π―
π DESCRIPTION π
okay so for now, this function simply looks at the registered auth_tok's linked off the mount_crypt_stat. the consequence of that is kind of a big deal tho: all the auth_toks that can be used must be registered at mount time β° like, at mount time. no late arrivals. the guest list is closed π
and here's the tea β β this function could potentially try a lot harder to find auth_toks. for example (their words, not mine), by calling out to ecryptfsd to dynamically retrieve an auth_tok object. if it did that, then static registration of auth_toks would no longer be necessary. so that's a real possibility floating around out there π¦ absolutely not what it does today, tho β don't get it twisted.
Returns zero on no error; non-zero on error. periodt. π
π SEE ALSO π
Kernel file ./fs/ecryptfs/keystore.c β and the whole friend group right here:
ecryptfs_parse_packet_length(9)ecryptfs_write_packet_length(9)ecryptfs_verify_version(9)ecryptfs_verify_auth_tok_from_key(9)ecryptfs_parse_tag_70_packet(9)decrypt_pki_encrypted_session_key(9)parse_tag_1_packet(9)parse_tag_3_packet(9)parse_tag_11_packet(9)decrypt_passphrase_encrypted_session_key(9)ecryptfs_parse_packet_set(9)write_tag_1_packet(9)write_tag_11_packet(9)write_tag_3_packet(9)ecryptfs_generate_key_packet_set(9)
like, the whole packet squad showed up π«Άβ¨
π
and that's the page!! brought to you by ./fs/ecryptfs, dated October 2026 β mwah, love u, go read your kernel source bestie ππ¦πΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms