AU_IO(3)

AU_IO(3) 💖

okay so bestie, this is the Library Functions Manual page for the audit-record I/O girlies ✨ and it is literally about moving audit records in and out without losing your mind 💅

✨ NAME ✨

au_fetch_tok, au_print_tok, au_read_rec — perform I/O involving an audit record 🫶

📚 LIBRARY 📚

Basic Security Module Library (libbsm, -lbsm) — that’s the vibe check, no cap 🌸

🌈 SYNOPSIS 🌈

#include <bsm/libbsm.h>

int
au_fetch_tok(tokenstr_t *tok, u_char *buf, int len);

void
au_print_tok(FILE *outfp, tokenstr_t *tok, char *del, char raw,
    char sfrm);

int
au_read_rec(FILE *fp, u_char **buf);

💖 DESCRIPTION 💖

These interfaces support input and output (I/O) involving audit records, internalizing an audit record from a byte stream, converting a token to either a raw or default string, and reading a single record from a file. It’s giving “glue code for audit tokens” and honestly? iconic 🎀

The au_fetch_tok() function reads a token from the passed buffer buf of length len bytes, and returns a pointer to the token via tok. Fetch the tok, bestie, it’s right there 🔥

The au_print_tok() function prints a string form of the token tok to the file output stream outfp, either in default mode, or raw mode if raw is set non-zero. The delimiter del is used when printing. Yup, delimiter girlies stay winning 💅

The au_read_rec() function reads an audit record from the file stream fp, and returns an allocated memory buffer containing the record via *buf, which must be freed by the caller using free(3). Important: caller frees it — do not ghost that buffer, fr fr 😭

A typical use of these routines might open a file with fopen(3), then read records from the file sequentially by calling au_read_rec(). Each record would be broken down into components tokens through sequential calls to au_fetch_tok() on the buffer, and then invoking au_print_tok() to print each token to an output stream such as stdout. On completion of the processing of each record, a call to free(3) would be used to free the record buffer. Finally, the source stream would be closed by a call to fclose(3). That’s the whole little pipeline, lowkey elegant 🌈

🎀 RETURN VALUES 🎀

The au_fetch_tok() and au_read_rec() functions return 0 on success, or -1 on failure along with additional error information returned via errno. So 0 is the slay outcome, -1 means check errno and maybe go touch some grass 🫶

🔗 SEE ALSO 🔗

free(3), libbsm(3) — the supporting cast, we love them 💜

🕰️ HISTORY 🕰️

The OpenBSM implementation was created by McAfee Research, the security division of McAfee Inc., under contract to Apple Computer, Inc., in 2004. It was subsequently adopted by the TrustedBSD Project as the foundation for the OpenBSM distribution. A whole origin story, periodt ✨

👑 AUTHORS 👑

This software was created by Robert Watson, Wayne Salamon, and Suresh Krishnaswamy for McAfee Research, the security research division of McAfee, Inc., under contract to Apple Computer, Inc.

The Basic Security Module (BSM) interface to audit records and audit event stream format were defined by Sun Microsystems. Legends only 👑💖

💀 BUGS 💀

The errno variable may not always be properly set in the event of an error.

🚨 bug alert: errno may not always be properly set when there’s an error. So like… don’t fully trust the vibe of errno in every failure case, bestie 😭

---

xoxo, Debian — April 19, 2005, signing off 💅✨