STRUCT ECRYPTFS_KEY_TFM(9)
π NAME π
struct ecryptfs_key_tfm β the Persistent key tfm, aka the crypto handle that just stays around π
β¨ SYNOPSIS β¨
okay so picture the vibes, here's the whole struct bestie:
struct ecryptfs_key_tfm {
struct crypto_skcipher *key_tfm;
size_t key_size;
struct mutex key_tfm_mutex;
struct list_head key_tfm_list;
unsigned char cipher_name[ECRYPTFS_MAX_CIPHER_NAME_SIZE + 1];
};
π Members π
key_tfmβ the crypto API handle to the key, it's giving main character energy π₯key_sizeβ how big the key is, in byteskey_tfm_mutexβ a mutex so that literally only one operation in eCryptfs is using the persistent TFM at any point in time. no sharing, no chaos, one at a time periodt πkey_tfm_listβ the handle that hangs this whole thing off the module-wide TFM list π§΅cipher_nameβ string name for the cipher for this TFM, iconic β¨
π¦ Description π¦
so the tea is: typically eCryptfs will use the same ciphers over and over again throughout the course of its operations. and likeβ¦ re-initializing the same cipher every single time? exhausting. unnecessary. so to avoid unnecessarily destroying and initializing the same cipher repeatedly, eCryptfs keeps a list of crypto API contexts around to use when needed π«Ά
it's literally a little crypto wardrobe. why rebuild the fit every time when you can just keep it on rotation π
πΈ SEE ALSO πΈ
- Kernel file
./fs/ecryptfs/ecryptfs_kernel.hstructecryptfs_global_auth_tok(9)π
and that's the page bestie!! source is ./fs/ecryptfs, dated October 2026, all about struct ecryptfs_key_tfm(9) β go read it again, slay ππβ¨
π¦ 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