rc_avpair_gen(3)

💖 rc_avpair_gen(3) — the Radius client library's little buffer-to-pairs machine 💖

okay so bestie, pull up a chair 🪑 because this is rc_avpair_gen(3), straight out of the Radius client library, and it's genuinely one of those functions that does exactly one thing and does it with main character energy ✨

---

🌸 NAME 🌸

rc_avpair_gen — and that's it, that's the whole name section. The description slot is lowkey empty, no cap 🙈 the function speaks for itself.

---

🎀 SYNOPSIS 🎀

#include <radcli/radcli.h>

VALUE_PAIR * rc_avpair_gen(
    rc_handle const      *rh,
    VALUE_PAIR           *pair,
    unsigned char const  *ptr,
    int                   length,
    uint32_t              vendorspec
);

like. look at her. five args, one pointer returned, no drama 💅

---

✨ DESCRIPTION ✨

So what she does: she takes attribute/value pairs from a buffer and builds a value_pair list, using allocated memory 🧠✨ that's the whole vibe. You hand her raw bytes, she hands you back a whole list of value pairs. It's giving "personal shopper but for RADIUS attributes" 🛍️

no cap: the memory is allocated, so somebody's gotta free it later, bestie. That somebody is you. 🙈

---

🦋 PARAMETERS 🦋

• rh — a handle to your parsed configuration. your whole setup, in one pointer 🫶
• pair — a pointer to a VALUE_PAIR structure.
• ptr — the value itself (like, the actual username, fr fr).
• length — how long ptr is. Or -1 if you want her to calculate it for you (which she can do in the case of strings 🧚).
• vendorspec — the vendor ID, in case this is a vendor specific value. Otherwise 0. Zero means "no vendor, we're being normal today" 💀

---

👑 STRUCTURES 👑

🚨 bestie listen: avoid using this structure directly. Use the rc_avpair_get_ functions instead. That's the assignment, periodt.

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
};

look at that pad[32], sitting there doing literally nothing. iconic behaviour honestly, we stan an unused field 🙈

---

⭐ RETURN VALUE ⭐

a value_pair list 🎉 or NULL on failure 😭 that's it, that's the deal.

---

🌈 SEE ALSO 🌈

the whole friend group, all invited to the group chat 🫶:

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 whole page, bestie 🎀 this one came from radcli, dated 2023-01-29, and it's an absolute bop. go build some value pairs. slay 💅✨🦋