ENUM FWCTL_RPC_SCOPE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… enum fwctl_rpc_scope(9) β€” like, the whole vibe

okay bestie, so this is from the Kernel API Manual and the star of the show is enum fwctl_rpc_scope, which is literally the scope of access for the RPC. that's it, that's the NAME. πŸŽ€


✨ SYNOPSIS ✨

enum fwctl_rpc_scope {
    FWCTL_RPC_CONFIGURATION ,
    FWCTL_RPC_DEBUG_READ_ONLY ,
    FWCTL_RPC_DEBUG_WRITE ,
    FWCTL_RPC_DEBUG_WRITE_FULL

};

no cap, that's the whole thing πŸ¦‹


🌸 Constants 🌸

πŸ’– FWCTL_RPC_CONFIGURATION β€” Device configuration access scope

this one is read/write access to device configuration. and the iconic part? when configuration is written to the device, it remains in a fully supported state. so like, you're not breaking anything, you're just being a good little config gremlin 🧚

πŸ¦‹ FWCTL_RPC_DEBUG_READ_ONLY β€” Read only access to debug information

readable debug info, periodt. this info is compatible with kernel lockdown and it does not disclose any sensitive information. for instance β€” and this is a real rule β€” exposing any encryption secrets from this information is forbidden. 🚫 so keep your hands to yourself on that one.

πŸ”₯ FWCTL_RPC_DEBUG_WRITE β€” Writable access to lockdown compatible debug information

this lets you write to data in the device, which may leave a fully supported state. it's intended to permit intensive and possibly invasive debugging. and the thing to remember: this scope will taint the kernel. πŸ’€ so like, slay, but also be aware.

πŸ‘‘ FWCTL_RPC_DEBUG_WRITE_FULL β€” Write access to all debug information

read/write access to everything. it requires CAP_SYS_RAW_IO, so it is not required to follow lockdown principals. and if in doubt? debugging should be placed in this scope. also, heads up: this scope will taint the kernel. πŸ”₯


🌈 Description 🌈

refer to fwctl.rst for a more detailed discussion of these scopes, bestie. that's where the lore lives 🫢

lowkey important: the taint warnings are real, fr fr. don't say i didn't tell you πŸ’…

⭐ SEE ALSO ⭐

  • Kernel file ./include/uapi/fwctl/fwctl.h
  • General ioctl format(9)
  • struct fwctl_info(9)
  • struct fwctl_rpc(9)

okay that's the whole page, no notes πŸ˜­πŸ’œ this lore comes to you from ./include/uapi/fwctl, dated October 2026, and yes it's still enum fwctl_rpc_scope(9) at the end β€” bye bestie, go read your scopes responsibly πŸŽ€βœ¨πŸ‘‘

πŸ“¦ where this page comes from