RPC_GSS_MAX_DATA_LENGTH(3)

📦 version 15.1, in freebsd 14.5, freebsd 15.1

💖 NAME 💖

okay so bestie, this is the RPC_GSS_MAX_DATA_LENGTH(3) page from the Library Functions Manual — and it’s all about rpc_gss_max_data_length, which calculates maximum data size. No cap, that’s the whole flex. 💅

📚 LIBRARY 📚

This icon lives in the RPC GSS-API Authentication Library — that’s librpcsec_gss, and you link it with -lrpcsec_gss. Slay. ✨

🌸 SYNOPSIS 🌸

#include <rpc/rpcsec_gss.h>

int
rpc_gss_max_data_length(AUTH *auth, int max_tp_unit_len);

🫶 DESCRIPTION 🫶

So here’s the tea, bestie: this function calculates the maximum message size that will fit into a packet of size max_tp_unit_len, given the current service and QoP setting. It’s literally giving “will my message fit in this transport packet?” energy. 💖

🎀 PARAMETERS 🎀

  • auth — a handle to a RPCSEC_GSS security context. Like, your little security-context bestie.
  • max_tp_unit_len — the maximum packet size of the underlying transport protocol. The packet’s size limit, periodt.

⭐ RETURN VALUES ⭐

It returns the maximum message size that can be encoded. That’s the number you get back, bestie. ✨

🌈 SEE ALSO 🌈

🦋 HISTORY 🦋

The rpc_gss_max_data_length function first appeared in FreeBSD 8.0. Iconic behavior from the FreeBSD 8.0 era. 👑

💜 AUTHORS 💜

This manual page was written by Doug Rabson <dfr@FreeBSD.org>. Shoutout to Doug, fr fr. 🫶

Cute sign-off time: this cutie was brought to you by Debian, dated January 26, 2010. Byeee 💖🦋

📦 where this page comes from