rc_avpair_get(3)
π rc_avpair_get(3) π
okay so real quick before anything: this page is part of the radcli manual β that's the Radius client library situation, and the star of the show is a little function called rc_avpair_get. bestie, we're gonna find attributes. it's giving β¨detective eraβ¨.
πΈ NAME πΈ
rc_avpair_get β literally the whole description in the original is just blank, no cap, they left it empty. so here's the vibe: it's the function that finds an attribute value-pair for you. that's it. that's the girl. π
β¨ SYNOPSIS β¨
#include <radcli/radcli.h>
VALUE_PAIR * rc_avpair_get(
VALUE_PAIR *vp,
uint32_t attrid,
uint32_t vendorspec
);
look at her. three args. no drama. π
π¦ DESCRIPTION π¦
okay so what does she actually do? she finds the first attribute value-pair that matches the attribute you asked for, digging through the value-pair list you handed her. first match only, bestie β she's not gonna scroll the whole list for you, she stops the second she finds her girl. π₯
π PARAMETERS π
vpβ a pointer to aVALUE_PAIRstructure. that's the list you're snooping through, your starting point, your main character. π«Άattridβ the attribute of the pair to find (e.g.,PW_USER_NAME). yes, exactly like that, that's the example, it's iconic. πvendorspecβ the vendor ID, but ONLY in case of a vendor specific value β otherwise0. so like. zero means "no vendor, just vibes". don't forget the zero. π
π STRUCTURES π
β οΈ WARNING β οΈ bestie. listen. Avoid using this structure directly. fr fr. use the rc_avpair_get_ functions instead. she said what she said. π
but because you're nosy (love that for you), here's the whole thing, verbatim, character for character, don't touch a single bracket:
struct rc_value_pair {
char name[RC_NAME_LENGTH+1]; // attribute name if known.
uint64_t attribute; // attribute numeric value of type rc_attr_id including vendor; use VENDOR() and ATTRID() to separate.
rc_attr_type type; // attribute type.
uint32_t lvalue; // attribute value if type is PW_TYPE_INTEGER, PW_TYPE_DATE or PW_TYPE_IPADDR.
char strvalue[AUTH_STRING_LEN+1]; // contains attribute value in other cases.
struct rc_value_pair *next;
char pad[32]; // unused pad
};
quick field tour, bestie, so it's not just a wall of text:
name[RC_NAME_LENGTH+1]β attribute name, but only if it's known. if not? mystery girl. πattributeβ the attribute numeric value of typerc_attr_id, including vendor. useVENDOR()andATTRID()to separate them, iykyk. βtypeβ attribute type. she's got a type. iconic.lvalueβ attribute value, but only if the type isPW_TYPE_INTEGER,PW_TYPE_DATEorPW_TYPE_IPADDR. those are the girlies for this field.strvalue[AUTH_STRING_LEN+1]β contains the attribute value in other cases. so everybody else lives here. πnextβ the link to the next pair in the chain. π¦pad[32]β unused pad. it's just sitting there. unused. minding its business. β¨
π RETURN VALUE π
the value pair found. that's it. that's the return. she delivers. π
π SEE ALSO π
okay this is the group chat, the whole squad, every single one, don't skip anybody:
radcli.h(3), rc_aaa(3), rc_aaa_ctx(3), rc_aaa_ctx_free(3), rc_aaa_ctx_get_secret(3), rc_aaa_ctx_get_vector(3), rc_aaa_ctx_server(3), rc_acct(3), rc_acct_proxy(3), rc_add_config(3), rc_apply_config(3), rc_auth(3), rc_auth_proxy(3), rc_avpair_add(3), rc_avpair_assign(3), rc_avpair_copy(3), rc_avpair_free(3), rc_avpair_gen(3), rc_avpair_get(3), rc_avpair_get_attr(3), rc_avpair_get_in6(3), rc_avpair_get_raw(3), rc_avpair_get_uint32(3), rc_avpair_insert(3), rc_avpair_log(3), rc_avpair_new(3), rc_avpair_next(3), rc_avpair_parse(3), rc_avpair_remove(3), rc_avpair_tostr(3), rc_buildreq(3), rc_check(3), rc_check_tls(3), rc_conf_int(3), rc_conf_srv(3), rc_conf_str(3), rc_config_free(3), rc_config_init(3), rc_destroy(3), rc_dict_addattr(3), rc_dict_addval(3), rc_dict_addvend(3), rc_dict_findattr(3), rc_dict_findval(3), rc_dict_findvend(3), rc_dict_free(3), rc_dict_getattr(3), rc_dict_getval(3), rc_dict_getvend(3), rc_find_server_addr(3), rc_get_socket_type(3), rc_get_srcaddr(3), rc_getport(3), rc_mksid(3), rc_new(3), rc_openlog(3), rc_own_hostname(3), rc_read_config(3), rc_read_dictionary(3), rc_read_dictionary_from_buffer(3), rc_send_server(3), rc_setdebug(3), rc_test_config(3), rc_tls_fd(3)
and that's the page, bestie!! π«Ά this whole thing came from radcli and it's dated 2023-01-29 β so it's a lil vintage, but she still ate. go find your attributes. periodt. π β¨
π¦ where this page comes from
- alpine 3.24: radcli-doc 1.4.0-r0 Β· BSD-2-Clause AND MIT
- epel 10: radcli-devel 1.5.2-3.el10_3 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 43: radcli-devel 1.4.0-5.fc43 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 43: radcli-devel 1.4.0-5.fc43 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.4.0-6.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.4.0-6.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.5.2-3.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- fedora 44: radcli-devel 1.5.2-3.fc44 Β· BSD-2-Clause AND UMich-Merit AND HPND-Fenneberg-Livingston
- nixos 26.05: radcli 1.5.1
- nixpkgs unstable: radcli 1.5.2
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- opensuse-leap 16.0: radcli-devel 1.4.0-bp160.1.11 Β· BSD-2-Clause AND MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms