kismet_selinux(8)

πŸ“¦
version 20250627+git412.dbf877ab7 Β· 7 versions
, in opensuse-leap 16.0

πŸ’… kismet_selinux β€” like, the whole SELinux manual page for kismet, bestie

okay so real talk: this is the kismet_selinux(8) page β€” SELinux Policy for kismet β€” and it's about to be your new hyperfixation. grab a boba, we're doing this πŸ“


✨ NAME ✨

kismet_selinux β€” Security Enhanced Linux Policy for the kismet processes. that's it. that's the vibe. πŸŽ€


🌸 DESCRIPTION 🌸

Security-Enhanced Linux secures the kismet processes via flexible mandatory access control. no cap, it's out here protecting your fave sniffer with MAC (the mandatory access control kind, not the makeup kind, sadly πŸ’„).

The kismet processes execute with the kismet_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier.

For example:

ps -eZ | grep kismet_t

literally just run it and see who's living in kismet_t land πŸ•΅οΈβ€β™€οΈ


πŸšͺ ENTRYPOINTS πŸšͺ

The kismet_t SELinux type can be entered via the kismet_exec_t file type.

The default entrypoint paths for the kismet_t domain are the following:

/usr/bin/kismet, /usr/bin/kismet_drone, /usr/bin/kismet_server

three doors, one domain. main character energy honestly πŸ‘‘


🫢 PROCESS TYPES 🫢

SELinux defines process types (domains) for each process running on the system. yes bestie, every single one.

You can see the context of a process using the -Z option to ps.

Policy governs the access confined processes have to files. SELinux kismet policy is very flexible allowing users to setup their kismet processes in as secure a method as possible. flexible and secure?? we love a both/and situation ✨

The following process types are defined for kismet:

  • kismet_t
Note: semanage permissive -a kismet_t can be used to make the process type kismet_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it stops yelling at you but it's still journaling about it. messy but valid πŸ’€

πŸ”₯ BOOLEANS πŸ”₯

SELinux policy is customizable based on least access required. kismet policy is extremely flexible and has several booleans that allow you to manipulate the policy and run kismet with the tightest access possible. tightest access possible = the goal, always πŸ’…

If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default.

setsebool -P fips_mode 1

If you want to allow system to run with NIS, you must turn on the nis_enabled boolean. Disabled by default.

setsebool -P nis_enabled 1

that -P is doing the heavy lifting btw, it makes it persist across reboots. iconic behavior πŸŽ€


πŸ“ MANAGED FILES πŸ“

The SELinux process type kismet_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. SELinux said "i'll handle MAC but UID/DAC is your problem, bestie" 😭

kismet_home_t

/home/[^/]+/.kismet(/.*)?

kismet_tmp_t

(no default paths listed for this one β€” it's giving mystery 🌫️)

kismet_tmpfs_t

(also no paths listed β€” tmpfs things, you know how it is)

kismet_var_lib_t

/var/lib/kismet(/.*)?

krb5_host_rcache_t

/var/tmp/krb5_0.rcache2
/var/cache/krb5rcache(/.*)?
/var/tmp/nfs_0
/var/tmp/DNS_25
/var/tmp/host_0
/var/tmp/imap_0
/var/tmp/HTTP_23
/var/tmp/HTTP_48
/var/tmp/ldap_55
/var/tmp/ldap_487
/var/tmp/ldapmap1_0

look at all those cache paths, highkey a whole mood board of kerberos realness πŸ¦‹


πŸ—‚οΈ FILE CONTEXTS πŸ—‚οΈ

SELinux requires files to have an extended attribute to define the file type.

You can see the context of a file using the -Z option to ls.

Policy governs the access confined processes have to these files. SELinux kismet policy is very flexible allowing users to setup their kismet processes in as secure a method as possible. (yes it says that twice, and yes it's still true both times πŸ’–)


⭐ STANDARD FILE CONTEXT ⭐

SELinux defines the file context types for the kismet, if you wanted to store files with these types in a different paths, you need to execute the semanage command to specify alternate labeling and then use restorecon to put the labels on disk.

semanage fcontext -a -t kismet_exec_t '/srv/kismet/content(/.*)?'
restorecon -R -v /srv/mykismet_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise πŸ™ˆ

The following file types are defined for kismet:

  • kismet_exec_t β€” Set files with the kismet_exec_t type, if you want to transition an executable to the kismet_t domain.

Paths:

/usr/bin/kismet, /usr/bin/kismet_drone, /usr/bin/kismet_server
  • kismet_home_t β€” Set files with the kismet_home_t type, if you want to store kismet files in the users home directory.
  • kismet_initrc_exec_t β€” Set files with the kismet_initrc_exec_t type, if you want to transition an executable to the kismet_initrc_t domain.
  • kismet_log_t β€” Set files with the kismet_log_t type, if you want to treat the data as kismet log data, usually stored under the /var/log directory.
  • kismet_tmp_t β€” Set files with the kismet_tmp_t type, if you want to store kismet temporary files in the /tmp directories.
  • kismet_tmpfs_t β€” Set files with the kismet_tmpfs_t type, if you want to store kismet files on a tmpfs file system.
  • kismet_var_lib_t β€” Set files with the kismet_var_lib_t type, if you want to store the kismet files under the /var/lib directory.
  • kismet_var_run_t β€” Set files with the kismet_var_run_t type, if you want to store the kismet files under the /run or /var/run directory.
Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. so like β€” chcon is a temporary tattoo, semanage fcontext is the real ink. choose wisely πŸŽ€

πŸ› οΈ COMMANDS πŸ› οΈ

  • semanage fcontext can also be used to manipulate default file context mappings.
  • semanage permissive can also be used to manipulate whether or not a process type is permissive.
  • semanage module can also be used to enable/disable/install/remove policy modules.
  • semanage boolean can also be used to manipulate the booleans.
  • system-config-selinux is a GUI tool available to customize SELinux policy settings. a GUI!! for the girlies who prefer clicking to typing πŸ’…βœ¨

πŸ‘‘ AUTHOR πŸ‘‘

This manual page was auto-generated using sepolicy manpage. a bot wrote this and honestly? it ate. πŸ€–πŸ”₯


🌈 SEE ALSO 🌈

selinux(8), kismet(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)

go read those too, i'm literally begging 🫢


that's the whole page bestie!! βœ¨πŸ’– this lil masterpiece is from kismet, version/date 26-10-06, and it lives at kismet_selinux(8) in the manual. mwah, study safe, and remember: never run chcon and call it permanent πŸ˜˜πŸ’…

πŸ“¦ where this page comes from