oscam.whitelist(5)

💅 oscam.whitelist — the glow-up guide ✨

Okay bestie, gather round, because this is the manual page for oscam.whitelist(5), aka the global ECM length whitelisting configuration file for OSCam. Yes, the whole file. It's giving "small file, big opinions" and honestly? We're obsessed. 🎀

---

🌸 SYNOPSIS 🌸

ECM length whitelisting

That's it. That's the whole vibe. Short, sweet, iconic. 👑

---

🦋 DESCRIPTIONS 🦋

So every line in this file is basically a little rule, and each rule starts with a letter that tells OSCam what kind of rule it is. Every one of them uses the same shape for the address-y part:

[CAID][:][provider ID][:][service ID][:][ECM PID][:][CHID][:][ECM length 1[,ECM length 2]...]

• w: — ECM length whitelisting. Classic. The moment. ✨

w:[CAID][:][provider ID][:][service ID][:][ECM PID][:][CHID][:][ECM length 1[,ECM length 2]...]

• l: — ECM length whitelisting, but make it exclusive: it does not proceed with any other ECM length whitelisting when matching. It's literally the abbreviation for normal ECM length whitelisting using the w parameter — same energy, but it commits. No cap. 💅

l:[CAID][:][provider ID][:][service ID][:][ECM PID][:][CHID][:][ECM length 1[,ECM length 2]...]

• i: — ignore ECM length. Not me ignoring my problems, but make it ECM lengths. 🙈

i:[CAID][:][provider ID][:][service ID][:][ECM PID][:][CHID][:][ECM length 1[,ECM length 2]...]

• m: — CAID and provider ID mapping. It goes by first matching rules, and this mapping is preferred over all other whitelistings. Main character energy, fr fr. 👑

m:[CAID][:][provider ID][:][service ID][:][ECM PID][:][CHID][:][ECM length 1[,ECM length 2]...] [new CAID][:][new provider ID]

---

💀 ANNONTATIONS 💀

(Yes the heading is spelled like that in the original and we are respecting the lore. 🫶)

Please use Unix text file format only. Like, only only. Windows line endings will not be slaying today. 😭

---

🌈 EXAMPLES 🌈

These are the moment, the blueprint, the whole mood board:

 w:0100                          # whitelisting for CAID 0100

 i:0200::1234                    # ignore CAID 0200 with
                                 # service ID 1234

 i:::::2345                      # ignore CHID 2345

 m:3456:123456::::: 4567:234567  # mapping

 w:                              # allow all others (blacklist)

 l:0300                          # whitelisting for CAID 0300 not
                                 # proceeding if matching

Look at all those colons bestie. Empty fields are just placeholders — leave the gaps, the vibe check is fine. 🍓

---

🧚 SEE ALSO 🧚

Go read the whole friend group, they're all iconic:

list_smargo(1), oscam(1), oscam.ac(5), oscam.cacheex(5), oscam.cert(5), oscam.conf(5), oscam.dvbapi(5), oscam.fakecws(5), oscam.guess(5), oscam.ird(5), oscam.provid(5), oscam.ratelimit(5), oscam.server(5), oscam.services(5), oscam.srvid(5), oscam.srvid2(5), oscam.user(5)

---

💖 That's the whole page, bestie! This little beauty lives in the File Formats Manual as oscam.whitelist(5) — same source, same version, same date as always, no edits from me, just vibes. Slay your whitelisting responsibly. 🎀✨🦋