pamtest_conv_data(3)

💅 NAME 💅

pamtest_conv_data — bestie, this is the struct you reach for when you're using run_pamtest, because that bad boy runs its own internal conversation function. It's giving "middleware for your PAM chat", no cap.

---

✨ SYNOPSIS ✨

#include <include/libpamtest.h>

🎀 Data Fields 🎀

• const char ** in_echo_off — when the conversation function gets handed PAM_PROMPT_ECHO_OFF, it pulls the auth token out of the in_echo_off array and keeps an index internally. Like, it's keeping track so you don't have to 🫶
• const char ** in_echo_on — when the conversation function gets PAM_PROMPT_ECHO_ON, it reads the input from the in_echo_off array and keeps an index internally. (Yes, it says in_echo_off there too — I'm just repeating what the page says, don't come for me 😭)
• char ** out_err — captures messages that come through PAM_ERROR_MSG 💀
• char ** out_info — captures messages that come through PAM_TEXT_INFO 🌸

🦋 Detailed Description 🦋

Okay so, literally: this structure should be used when using run_pamtest, which uses an internal conversation function. That's the whole vibe. Main character struct energy ✨

---

👑 Field Documentation 👑

char** pamtest_conv_data::out_err

Captures messages through PAM_ERROR_MSG. Heads up bestie — the test caller is responsible for allocating enough space in the array. That's on you, not on the library 🙈

char** pamtest_conv_data::out_info

Captures messages through PAM_TEXT_INFO. And same deal: the test caller is responsible for allocating enough space in the array. Allocate responsibly, queen 💅

---

⭐ Author ⭐

Generated automatically by Doxygen for pam_wrapper from the source code. Iconic behaviour, honestly.

---

🧚 Lowkey the whole point: fill the arrays, let the internal conversation function do its thing, and check out_err / out_info after. Just don't forget the allocation, fr fr.

---

That's the whole page, bestie — straight from the pam_wrapper source, pamtest_conv_data(3), brought to you by Doxygen and absolutely zero chill. Slay 💖