semanage...set_local(3)

💖 semanage_bool_set_active — the Libsemanage API doc, but make it make sense 💖

okay bestie, so you know how we're poking at libsemanage? This is one of those pages from the Libsemanage API documentation manual, and it's literally just one function. Sit down, hydrate, let's go 🫶

---

✨ NAME ✨

semanage_bool_set_active — update an existing SELinux boolean in the currently active policy

Like. That's it. That's the whole job. You hand it a boolean that already exists and you give it a glow-up ✨

---

🎀 SYNOPSIS 🎀

#include <semanage/booleans_active.h>

extern int semanage_bool_set_active (
     semanage_handle_t *handle,
     const semanage_bool_key_t *key,
     const semanage_bool_t *data);

three args, no drama, iconic signature honestly 💅

---

🌸 DESCRIPTION 🌸

🦋 Behavior

So here's the tea: the set function will fail if no matching key is found in the local store. No key, no vibes, no update. periodt.

Otherwise? The provided object replaces the current one. Out with the old, in with the new 🔥

And then — and this is the main character moment — when semanage_commit(3) is invoked, the changes get written permanently into the local store, and they get loaded into policy. So like, the change doesn't really land until commit. It's giving "texting him back but not hitting send yet" 😭

Also important: the validity of the object being added is checked at commit time. Not now. Later. At commit. Just so you know 🫶

🧚 Parameters

• handle — tracks persistent state across all your semanage calls, and it's also the one doing the error reporting. Basically the group chat admin.
• key — identifies the data object that's gonna be written into the store. It knows who we're talking about.
• data — the actual object getting written into the store.

And a lil detail that matters: the key and the data are properties of the caller. They are not stored or modified internally. So like, they're yours, semanage is just borrowing them, no take-backs, no edits. ✨

⭐ Requirements

This function requires a semanage connection to be established — see semanage_connect(3) — and it must be executed in a transaction — see semanage_begin_transaction(3).

no connection + no transaction = no function. it's a vibe check and you will not pass it 💀

---

💜 RETURN VALUE 💜

If it goes wrong? -1 comes back, and the semanage error callback gets invoked, describing the error. So you won't be left guessing, bestie, it will tell you 🙈

Otherwise 0 is returned. Zero. Perfect. Slay. 🎀

---

🌈 SEE ALSO 🌈

• semanage_handle_create(3)
• semanage_begin_transaction(3)
• semanage_connect(3)
• semanage_commit(3)

go read those, they're the prerequisites, iykyk 🧚

---

okay that's the whole page!! this little masterpiece was written by ivg2@cornell.edu on 4 January 2006 — yes bestie, 2006, it's vintage, it's archival, it's lowkey a piece of history and it still ate 💖 go commit your transaction 🫶✨