tipc_crypto_key_rcv(9)

📦 version 7.3.1, in nixpkgs unstable

💖 tipc_crypto_key_rcv — Receive a session key 💖

Okay bestie, so this is a page from the Kernel API Manual and it's all about one little function that does one very specific job: catching a session key that a peer sent you. Let's get into it 🫶

✨ SYNOPSIS ✨

bool tipc_crypto_key_rcv(struct tipc_crypto *rx, struct tipc_msg *hdr);

That's it, that's the whole signature — a bool goes in, a bool comes out, and in between it does key-receiving business. Slay 💅

🌸 ARGUMENTS 🌸

  • rx — the RX crypto. Like, the crypto object on the receiving side. It's the one who's about to get a new key attached to it 👀
  • hdr — the TIPC v2 message incl. the receiving session key in its data. So the key is literally chillin' inside this message's data field, waiting to be picked up 🎀

🦋 DESCRIPTION 🦋

So what does it actually do? Simple: this function retrieves the session key in the message from the peer, then schedules a RX work to attach the key to the corresponding RX crypto.

That's the whole vibe — grab the key out of the message, then don't attach it right this second, schedule the RX work to do the attaching. Async queen behavior tbh ⭐

💜 RETURN 💜

It returns true if the key has been scheduled for attaching, otherwise false.

No cap, that's literally the whole rule. Scheduled = true, not scheduled = false. Periodt 💀

🧚 SEE ALSO 🧚

Everything else in the TIPC crypto cinematic universe 🌈 — and the kernel file ./net/tipc/crypto.c:

Go read the whole set, bestie — iykyk 🔥

Alright, that's the whole page! This one lives in ./net/tipc, dated October 2026, and it's brought to you by the Kernel API Manual. Mwah, go touch some kernel code 💋🎀

📦 where this page comes from