wireshark_selinux(8)

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

πŸ’… wireshark_selinux β€” the SELinux tea for wireshark

okay so bestie, welcome to wireshark_selinux, the manual page (wireshark_selinux(8)) that spills ALL the policy details for the wireshark processes. grab a strawberry drink πŸ“ and let's get into it.


πŸ¦‹ NAME

wireshark_selinux β€” Security Enhanced Linux Policy for the wireshark processes. that's it, that's the whole vibe.


✨ DESCRIPTION

Security-Enhanced Linux secures the wireshark processes via flexible mandatory access control. yes ma'am, mandatory. not the cute optional kind. πŸ”₯

The wireshark processes execute with the wireshark_t SELinux type. wanna check if you've got these processes running? run the ps command with the -Z qualifier. like this:

ps -eZ | grep wireshark_t

literally that simple, no cap. πŸ‘‘


πŸšͺ ENTRYPOINTS

The wireshark_t SELinux type can be entered via the wireshark_exec_t file type. that's the doorway, bestie. πŸšͺ✨

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

/usr/bin/tshark, /usr/bin/wireshark

πŸ‘― PROCESS TYPES

SELinux defines process types (domains) for each process running on the system. every process gets a little label, iykyk.

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

Policy governs the access confined processes have to files. SELinux wireshark policy is very flexible, allowing users to setup their wireshark processes in as secure a method as possible.

The following process types are defined for wireshark:

  • wireshark_t
Note: semanage permissive -a wireshark_t can be used to make the process type wireshark_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's chill but it's still snitching πŸ’€

πŸŽ€ BOOLEANS

SELinux policy is customizable based on least access required. wireshark policy is extremely flexible and has several booleans that allow you to manipulate the policy and run wireshark with the tightest access possible. tightest access = main character energy, honestly. πŸ‘‘

  • If you want to deny all system processes and Linux users to use bluetooth wireless technology, you must turn on the deny_bluetooth boolean. Disabled by default.
setsebool -P deny_bluetooth 1
  • 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
  • If you want to allow regular users direct dri device access, you must turn on the selinuxuser_direct_dri_enabled boolean. Disabled by default.
setsebool -P selinuxuser_direct_dri_enabled 1
  • If you want to allows clients to write to the X server shared memory segments, you must turn on the xserver_clients_write_xshm boolean. Disabled by default.
setsebool -P xserver_clients_write_xshm 1

πŸ—‚οΈ MANAGED FILES

The SELinux process type wireshark_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 doesn't do ALL the work, bestie πŸ™ˆ

cache_home_t

/root/.cache(/.*)?
/home/[^/]+/.nv(/.*)?
/home/[^/]+/.cache(/.*)?

cifs_t

(no default paths listed, it's giving minimal 🌸)

config_home_t

/root/.kde(/.*)?
/root/.xine(/.*)?
/root/.config(/.*)?
/root/.Xdefaults
/home/[^/]+/.kde(/.*)?
/home/[^/]+/.xine(/.*)?
/home/[^/]+/.config(/.*)?
/home/[^/]+/.cache/dconf(/.*)?
/home/[^/]+/.Xdefaults
/run/user/[0-9]+/dconf(/.*)?

ecryptfs_t

/home/[^/]+/.Private(/.*)?
/home/[^/]+/.ecryptfs(/.*)?

fusefs_t

/run/user/[0-9]+/gvfs

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

nfs_t

(again, no default paths listed ✨)

user_fonts_cache_t

/root/.fontconfig(/.*)?
/root/.fonts/auto(/.*)?
/root/.fonts.cache-.*
/root/.cache/fontconfig(/.*)?
/home/[^/]+/.fontconfig(/.*)?
/home/[^/]+/.fonts/auto(/.*)?
/home/[^/]+/.fonts.cache-.*
/home/[^/]+/.cache/fontconfig(/.*)?

user_home_t

/home/[^/]+/.+

wireshark_home_t

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

wireshark_tmp_t

(no default paths listed 🫢)

wireshark_tmpfs_t

(no default paths listed either, we love a lowkey type πŸ’œ)


🏷️ FILE CONTEXTS

SELinux requires files to have an extended attribute to define the file type. yes, files have vibes and the vibes are stored as attributes. 🌈

You can see the context of a file using the -Z option to ls. go ahead, peek. πŸ‘€

Policy governs the access confined processes have to these files. SELinux wireshark policy is very flexible, allowing users to setup their wireshark processes in as secure a method as possible.

πŸ“ STANDARD FILE CONTEXT

SELinux defines the file context types for the wireshark, and 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. two-step slay ✨

semanage fcontext -a -t wireshark_exec_t '/srv/wireshark/content(/.*)?'
restorecon -R -v /srv/mywireshark_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex icons, we stan 🧚

The following file types are defined for wireshark:

wireshark_exec_t

  • Set files with the wireshark_exec_t type, if you want to transition an executable to the wireshark_t domain.

Paths:

/usr/bin/tshark, /usr/bin/wireshark

wireshark_home_t

  • Set files with the wireshark_home_t type, if you want to store wireshark files in the users home directory.

wireshark_tmp_t

  • Set files with the wireshark_tmp_t type, if you want to store wireshark temporary files in the /tmp directories.

wireshark_tmpfs_t

  • Set files with the wireshark_tmpfs_t type, if you want to store wireshark files on a tmpfs file system.
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. temporary = cute little experiment, permanent = you're committed, no take-backs πŸ’…

πŸ› οΈ 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 whole GUI, for the girlies who like clicking πŸŽ€

πŸ‘‘ AUTHOR

This manual page was auto-generated using sepolicy manpage. robot wrote it, I just gave it the glow-up. πŸ€–πŸ’–


πŸ”— SEE ALSO

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


okay bestie that's the whole page, ate and left no crumbs πŸ’…βœ¨ this one's from wireshark, dated 26-10-06, and the page is wireshark_selinux(8) β€” go forth and confine those processes responsibly, mwah πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from