ecryptfs_set...pt_stat_vals(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ NAME πŸ¦‹

ecryptfs_set_default_crypt_stat_vals β€”

okay so bestie, real talk, the manpage gives you the function name and then just... leaves the dash hanging there with nothing after it. iconic honestly. no one-liner, no explanation, just vibes. so we're moving on πŸ’…

(quick note, this is from the Kernel API Manual, in case the whole (9) situation wasn't a dead giveaway 🧚)


✨ SYNOPSIS ✨

void ecryptfs_set_default_crypt_stat_vals (struct ecryptfs_crypt_stat
*crypt_stat , struct ecryptfs_mount_crypt_stat *mount_crypt_stat );

it's a void function, so like, it doesn't hand you anything back. it just does the thing and dips πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • crypt_stat β€” the inode's cryptographic context, aka the crypto brain of the file you're looking at 🧠✨
  • mount_crypt_stat β€” the mount point's cryptographic context, aka the crypto brain of the whole mount, the bigger-picture queen πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

these are the default values in the event that policy does not override them. periodt. that's it, that's the whole description πŸ’€

like, think of it as the backup outfit. policy gets first dibs on the look, but if policy doesn't show up? these defaults are absolutely still slaying in the mirror, no cap πŸͺžπŸ’…


🌈 SEE ALSO 🌈

kernel file ./fs/ecryptfs/crypto.c, plus literally the entire friend group:


go read them all, bestie. all thirty. i'll wait 🫢

anyway that's the whole page from ./fs/ecryptfs, dated October 2026 β€” mwah, love u, go set some defaults πŸ’œπŸŒΈβ­

πŸ“¦ where this page comes from