IPSEC_STRERROR(3)

💖 ipsec_strerror — error messages for the IPsec policy manipulation library

okay bestie, welcome to ipsec_strerror(3) from the Library Functions Manual 📚✨. This is the little function that hands you the error-message string for the IPsec policy manipulation library, and it’s giving “tiny but important” energy fr fr.

🩷 NAME

ipsec_strerror — error messages for the IPsec policy manipulation library

🌸 SYNOPSIS

#include <netipsec/ipsec.h>

const char *
ipsec_strerror();

🦋 DESCRIPTION

So <netipsec/ipsec.h> declares this:

extern int ipsec_errcode;

and that ipsec_errcode is literally the thing used to pass an error code from the IPsec policy manipulation library to a user program 🫶. The ipsec_strerror() function can be used to obtain the error message string for that error code.

Do not modify the array pointed to by the program — no cap, hands off 🙅‍♀️. And listen: since ipsec_strerror() uses strerror(3) as an underlying function, calling strerror(3) after ipsec_strerror() would overwrite the return value from ipsec_strerror() and make it invalid 😭. So like… don’t do that, bestie.

🎀 RETURN VALUES

The ipsec_strerror() function always returns a pointer to a C string ✨. That C string must not be overwritten by the caller, okay? It’s not yours to scribble on 💅.

👑 SEE ALSO

• ipsec_set_policy(3) — go read that one too, iykyk 💜

🌈 HISTORY

The ipsec_strerror() function first appeared in the WIDE/KAME IPv6 protocol stack kit 🧚‍♀️✨.

💀 BUGS

• The ipsec_strerror() function will return its result which may be overwritten by subsequent calls 😵‍💫.
• ipsec_errcode is not thread safe 🚩.

---

mwah 💋 — this page is from Debian, dated February 14, 2006, and it’s IPSEC_STRERROR(3), okay bye bestie 🫶🌟