RPC_GSS_MAX_DATA_LENGTH(3)

✨ RPC_GSS_MAX_DATA_LENGTH(3) ✨

okay bestie, so this one is a lil function from the Library Functions Manual and it's literally called rpc_gss_max_data_length — we're doing math about packets today, no cap 🎀

💖 NAME 💖

rpc_gss_max_data_length — bestie, we're calculating the maximum data size, that's the whole gig 💅

🌸 SYNOPSIS 🌸

#include <rpc/rpcsec_gss.h>

int
rpc_gss_max_data_length(AUTH *auth, int max_tp_unit_len);

like, that's it. two args. she's lowkey simple 🦋

🫶 DESCRIPTION 🫶

So the way this works: rpc_gss_max_data_length() figures out the biggest message size that will actually fit into a packet of size max_tp_unit_len, and it does that math based on the current service and the QoP setting you've got going on. it's giving "how much can I actually cram in here without things going sideways" ✨

🎀 PARAMETERS 🎀

• auth — a handle to a RPCSEC_GSS security context. like your little pass to the secure zone 🔐
• max_tp_unit_len — the maximum packet size of the underlying transport protocol. basically the container size you're working with 📦

💜 RETURN VALUES 💜

it returns the maximum message size that can be encoded. that's the whole tea ☕

🌈 AVAILABILITY 🌈

The rpc_gss_max_data_length() function is part of libtirpc. so if you're looking for her, she lives there 💖

🔥 SEE ALSO 🔥

• rpc(3)
• gssapi(3)
• rpcsec_gss(3)

go read those if you wanna understand the whole friend group, iykyk 👑

👑 AUTHORS 👑

This manual page was written by Doug Rabson <dfr@FreeBSD.org>. thank you king for the lore 🫶

and that's the whole page, bestie!! this cutie came from the Debian side of things and she's dated January 26, 2010 — iconic vintage behavior fr fr, mwah 💅💖