RPC_GSS_SET_SVC_NAME(3)
π RPC_GSS_SET_SVC_NAME(3) π
okay bestie, so this is a page from the Library Functions Manual β it's rpc_gss_set_svc_name, and it's literally the glow-up your RPC service needs to get a GSS-API service principal attached to it. let's get into it π
β¨ NAME β¨
rpc_gss_set_svc_name β Associate a GSS-API service principal with an RPC service
πΈ SYNOPSIS πΈ
#include <rpc/rpcsec_gss.h>
bool_t
rpc_gss_set_svc_name(const char *principal, const char *mechanism,
u_int req_time, u_int program, u_int version);
π DESCRIPTION π
This function registers a service principal which will be used to authenticate RPCSEC_GSS security contexts for a given RPC program and version. that's it, that's the whole vibe β you hand it a principal, it makes it the identity for that program+version combo, and RPCSEC_GSS contexts get checked against it. iconic behavior, no cap π
π¦ PARAMETERS π¦
principalβ a string representing the service principal, and it has to be in the form"service@hostname". yes the@is mandatory, don't skip it πmechanismβ the name of the security mechanismreq_timeβ the time in seconds that the service credentials should remain valid. peepgss_acquire_cred(3)for more details. principal.programβ RPC program number for this serviceversionβ RPC program version for this service
not me pointing out that stray "principal." at the end of req_time β it's in the original, so it stays, bestie π copy the source, not the typo-eraser
β RETURN VALUES β
Returns TRUE if the service principal was registered or FALSE otherwise. binary. yes or no. slay or flop. that's the whole return contract π
π AVAILABILITY π
The rpc_gss_set_svc_name() function is part of libtirpc. so if you're missing it, that's a linking situation, not a you problem π«Ά
π SEE ALSO π
rpc(3), gssapi(3), gss_acquire_cred(3), rpcsec_gss(3)
π AUTHORS π
This manual page was written by Doug Rabson <dfr@FreeBSD.org>. thank you Doug, absolute legend, we stan π
and that's the whole page, bestie!! this manual page came to you from Debian, dated January 26, 2010 β vintage but still serving looks β¨ go register that principal, mwah π
π¦ where this page comes from
- alpine 3.22: libtirpc-doc 1.3.5-r0 Β· BSD-3-Clause
- alpine 3.23: libtirpc-doc 1.3.5-r1 Β· BSD-3-Clause
- alpine 3.24: libtirpc-doc 1.3.5-r1 Β· BSD-3-Clause
- arch rolling: libtirpc 1.3.8-1 Β· SISSL AND BSD-3-Clause
- centos-stream 10: libtirpc-devel 1.3.5-1.el10 Β· SISSL AND BSD-3-Clause
- centos-stream 9: libtirpc-devel 1.3.3-9.el9 Β· SISSL and BSD
- centos-stream 9: libtirpc-devel 1.3.3-9.el9 Β· SISSL and BSD
- debian bookworm: libtirpc-dev 1.3.3+ds-1 Β· BSD-3-Clause
- debian trixie: libtirpc-dev 1.3.6+ds-1 Β· BSD-3-Clause
- fedora 43: libtirpc-devel 1.3.7-0.fc43 Β· SISSL AND BSD-3-Clause
- fedora 43: libtirpc-devel 1.3.7-0.fc43 Β· SISSL AND BSD-3-Clause
- fedora 43: libtirpc-devel 1.3.7-1.rc1.fc43 Β· SISSL AND BSD-3-Clause
- fedora 43: libtirpc-devel 1.3.7-1.rc1.fc43 Β· SISSL AND BSD-3-Clause
- fedora 44: libtirpc-devel 1.3.7-2.fc44 Β· SISSL AND BSD-3-Clause
- fedora 44: libtirpc-devel 1.3.7-2.fc44 Β· SISSL AND BSD-3-Clause
- fedora 44: libtirpc-devel 1.3.8-0.fc44 Β· SISSL AND BSD-3-Clause
- fedora 44: libtirpc-devel 1.3.8-0.fc44 Β· SISSL AND BSD-3-Clause
- nixos 26.05: libtirpc 1.3.7
- nixpkgs unstable: libtirpc 1.3.7
- opensuse-leap 16.0: libtirpc-devel 1.3.6-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: libtirpc-devel 1.3.6-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: libtirpc-devel 1.3.6-160000.2.2 Β· BSD-3-Clause
- opensuse-leap 16.0: libtirpc-devel 1.3.6-160000.2.2 Β· BSD-3-Clause
- ubuntu jammy: libtirpc-dev 1.3.2-2build1 Β· BSD-3-Clause
- ubuntu jammy: libtirpc-dev 1.3.2-2ubuntu0.1 Β· BSD-3-Clause
- ubuntu noble: libtirpc-dev 1.3.4+ds-1.1build1 Β· BSD-3-Clause
- ubuntu questing: libtirpc-dev 1.3.6+ds-1
- ubuntu resolute: libtirpc-dev 1.3.7-0.1 Β· BSD-3-Clause
- ubuntu stonking: libtirpc-dev 1.3.7+ds-1 Β· BSD-3-Clause
- Copyright (c) 2008 Isilon Inc http://www.isilon.com/
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms