RPC_GSS_SECCREATE(3)

okay so bestie, welcome to RPC_GSS_SECCREATE(3) — the Library Functions Manual page for rpc_gss_seccreate, and yes, we're gonna get you comfy with it 💅✨

🎀 NAME 🎀

rpc_gss_seccreate — create a security context using the RPCSEC_GSS protocol

📚 LIBRARY 📚

RPC GSS-API Authentication Library (librpcsec_gss, -lrpcsec_gss)

✨ SYNOPSIS ✨

#include <rpc/rpcsec_gss.h>

AUTH *
rpc_gss_seccreate(CLIENT *clnt, const char *principal,
    const char *mechanism, rpc_gss_service_t service, const char *qop,
    rpc_gss_options_req_t *options_req,
    rpc_gss_options_ret_t *options_ret);

💖 DESCRIPTION 💖

This function is used to establish a security context between an application and a remote peer using the RPSEC_GSS protocol. That's the whole vibe: app on one side, remote peer on the other, security context getting set up between them 🫶

🌸 PARAMETERS 🌸

• clnt — an RPC handle that's connected to the remote peer.
• principal — the name of the service principal on the remote peer. For example, an application that needs to contact an NFS server might use a principal such as "nfs@server.example.com".
• mechanism — the desired mechanism for this security context. The value of mechanism should be the name of one of the security mechanisms listed in /etc/gss/mech.
• service — the type of service requested. The options are:
  • rpc_gss_svc_default — the default; typically the same as rpc_gss_svc_none.
  • rpc_gss_svc_none — only RPC headers are integrity protected by a checksum.
  • rpc_gss_svc_integrity — RPC headers and data are integrity protected by a checksum.
  • rpc_gss_svc_privacy — RPC headers are integrity protected by a checksum, and data is encrypted.
• qop — desired quality of protection, or NULL for the default. Available values are listed in /etc/gss/qop.
• options_req — extra security context options to pass to the underlying GSS-API mechanism. Pass NULL to supply default values.
• options_ret — various values returned by the underlying GSS-API mechanism. Pass NULL if you don't need these values.

🔥 RETURN VALUES 🔥

If the security context was created successfully, you get back a pointer to an AUTH structure that represents the context. To use this security context for later RPC calls, set clnt->cl_auth to this value. slay 💅

👀 SEE ALSO 👀

• gssapi(3)
• rpc(3)
• rpcsec_gss(3)
• mech(5)
• qop(5)

🌈 HISTORY 🌈

The rpc_gss_seccreate function first appeared in FreeBSD 8.0.

🫶 AUTHORS 🫶

This manual page was written by Doug Rabson <dfr@FreeBSD.org>.

---

okay that's the page, bestie — sourced from Debian, dated January 26, 2010, and the manual page is RPC_GSS_SECCREATE(3). mwah 💋🎀