mysqld_selinux(8)
β¨ mysqld_selinux β the manual page, but make it make sense β¨
okay so bestie, you're reading the mysqld_selinux(8) page from the SELinux Policy mysqld set, and honestly? it's giving security lore. let's get into it π
π NAME π
mysqld_selinux β Security Enhanced Linux Policy for the mysqld processes. that's the whole vibe. it's the policy page for your mysql/mariadb daemons and it ate. π
πΈ DESCRIPTION πΈ
Security-Enhanced Linux secures the mysqld processes via flexible mandatory access control. yes, flexible. mandatory. both. iconic behavior honestly. β¨
the mysqld processes execute with the mysqld_t SELinux type. you can check if you've got these processes running by executing the ps command with the -Z qualifier. like this, for example:
ps -eZ | grep mysqld_t
that's it. that's the vibe check. π¦
π§ ENTRYPOINTS π§
the mysqld_t SELinux type can be entered via the mysqld_exec_t file type. no cap, that's the doorway. πͺβ¨
the default entrypoint paths for the mysqld_t domain are literally these:
/usr/bin/mysqld(-max|-debug)?
/usr/bin/ndbd
/usr/bin/mysqld
/usr/bin/mariadbd
/usr/libexec/mysqld
/usr/libexec/mariadbd
/usr/bin/mysql_upgrade
/usr/bin/mariadb-backup
/usr/bin/mariadb-upgrade
/usr/bin/mysqld_safe_helper
/usr/bin/mariadbd-safe-helper
look at all those little binaries. main character energy, every single one of them. π
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. one for everybody, basically. π«Ά
you can see the context of a process using the -Z option to ps. yep, same flag, doing the same thing. consistency slay. β¨
Policy governs the access confined processes have to files. SELinux mysqld policy is very flexible, allowing users to setup their mysqld processes in as secure a method as possible. very flexible. we love options. π
the following process types are defined for mysqld:
mysqld_tmysqld_safe_tmysqld_systemd_helper_t
Note:semanage permissive -a mysqld_tcan be used to make the process typemysqld_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. so like, it's chill about it but it's still watching. π ngl that's kind of the whole point.
π BOOLEANS π
SELinux policy is customizable based on least access required. mysqld policy is extremely flexible and has several booleans that allow you to manipulate the policy and run mysqld with the tightest access possible. tightest access = the outfit that fits exactly. periodt. π
so, one by one, bestie:
- if you want to allow
mysqldto connect to all ports, you must turn on themysql_connect_anyboolean. disabled by default.
setsebool -P mysql_connect_any 1
- if you want to allow
mysqldto connect to http port, you must turn on themysql_connect_httpboolean. disabled by default.
setsebool -P mysql_connect_http 1
- if you want to allow
mysqldto run under a different user via--user, you must turn on themysql_run_under_different_userboolean. enabled by default.
setsebool -P mysql_run_under_different_user 1
- if you want to dontaudit all daemons scheduling requests (
setsched,sys_nice), you must turn on thedaemons_dontaudit_schedulingboolean. enabled by default.
setsebool -P daemons_dontaudit_scheduling 1
- if you want to determine whether exim can connect to databases, you must turn on the
exim_can_connect_dbboolean. disabled by default.
setsebool -P exim_can_connect_db 1
- if you want to allow all domains to execute in
fips_mode, you must turn on thefips_modeboolean. enabled by default.
setsebool -P fips_mode 1
- if you want to determine whether ftpd can connect to databases over the TCP network, you must turn on the
ftpd_connect_dbboolean. disabled by default.
setsebool -P ftpd_connect_db 1
- if you want to allow HTTPD scripts and modules to connect to databases over the network, you must turn on the
httpd_can_network_connect_dbboolean. disabled by default.
setsebool -P httpd_can_network_connect_db 1
- if you want to allow confined applications to run with kerberos, you must turn on the
kerberos_enabledboolean. enabled by default.
setsebool -P kerberos_enabled 1
- if you want to allow system to run with NIS, you must turn on the
nis_enabledboolean. disabled by default.
setsebool -P nis_enabled 1
- if you want to allow PowerDNS to connect to databases over the network, you must turn on the
pdns_can_network_connect_dbboolean. disabled by default.
setsebool -P pdns_can_network_connect_db 1
that's eleven booleans, and yes i counted them twice because bestie, accuracy is the whole brand. π
π¦ PORT TYPES π¦
SELinux defines port types to represent TCP and UDP ports. cute little labels for your network doors. πͺ
you can see the types associated with a port by using the following command:
semanage port -l
Policy governs the access confined processes have to these ports. SELinux mysqld policy is very flexible, allowing users to setup their mysqld processes in as secure a method as possible. yes, same sentence energy, because it's the same promise. π
the following port types are defined for mysqld:
mysqld_port_t
Default Defined Ports:
tcp 1186,3306,63132-63164
3306? the classic. we know her. iykyk. π π₯
β MANAGED FILES β
the SELinux process type mysqld_t can manage files labeled with the following file types. the paths listed are the default paths for these file types. and remember, bestie:
the process's UID still needs to have DAC permissions. SELinux is not out here doing DAC's job for it, no matter how good the vibes are. π
cluster_conf_t
/etc/cluster(/.*)?
cluster_var_lib_t
/var/lib/pcsd(/.*)?
/var/lib/cluster(/.*)?
/var/lib/openais(/.*)?
/var/lib/pengine(/.*)?
/var/lib/corosync(/.*)?
/usr/lib/heartbeat(/.*)?
/var/lib/heartbeat(/.*)?
/var/lib/pacemaker(/.*)?
cluster_var_run_t
/run/crm(/.*)?
/run/cman_.*
/run/rsctmp(/.*)?
/run/aisexec.*
/run/heartbeat(/.*)?
/run/pcsd-ruby.socket
/run/corosync-qnetd(/.*)?
/run/corosync-qdevice(/.*)?
/run/pcsd.socket
/run/corosync.pid
/run/cpglockd.pid
/run/rgmanager.pid
/run/cluster/rgmanager.sk
faillog_t
/var/log/btmp.*
/run/faillock(/.*)?
/var/log/faillog.*
/var/log/tallylog.*
hugetlbfs_t
/dev/hugepages
/usr/lib/udev/devices/hugepages
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
lastlog_t
/var/log/lastlog.*
/var/lib/lastlog(/.*)?
mysqld_db_t
/var/lib/mysql(-files|-keyring)?(/.*)?
/var/lib/mysql-.*(/.*)?
mysqld_log_t
/var/log/mysql.*
/var/log/mysql(/.*)?
/var/log/mariadb(/.*)?
mysqld_tmp_t
no default paths listed for this one β it's mysqld_tmp_t, that's the whole entry. she's mysterious like that. π
mysqld_var_run_t
/run/mysql(/.*)?
/run/mysqld(/.*)?
/run/mariadb(/.*)?
/var/lib/mysql-.*/mysql(x)?.sock
/var/lib/mysql/mysql(x)?.sock
/var/tmp/mysql-protected.*(/.*)?
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
security_t
/selinux
wtmpdb_journal_t
/var/lib/wtmpdb/wtmp.db-journal
and that's where part one wraps up β the rest is still coming, don't go anywhere, we're literally not done yet πβ¨
πΎ FILE CONTEXTS πΎ
Okay so real talk bestie β SELinux is literally nothing without file contexts, because SELinux requires files to have an extended attribute to define the file type. That's the whole gig. No attribute, no vibe. π
You can see the context of a file using the -Z option to ls β yes, that's your new fave party trick, go try it, I'll wait. π
Policy governs the access confined processes have to these files. And good news: SELinux mysqld policy is super flexible, allowing users to setup their mysqld processes in as secure a method as possible. Iconic behaviour, honestly. π
ποΈ EQUIVALENCE DIRECTORIES ποΈ
So here's the tea: mysqld policy stores data with multiple different file context types under the /var/lib/mysql-.* directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. Say you wanted to store this data under the /srv directory β you would execute the following command:
semanage fcontext -a -e /var/lib/mysql-.* /srv/mysql-.*
restorecon -R -v /srv/mysql-.*
Same energy for logs, bestie: mysqld policy stores data with multiple different file context types under the /var/log/mysql directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. And if you wanted to store this data under the /srv directory you would execute the following command:
semanage fcontext -a -e /var/log/mysql /srv/mysql
restorecon -R -v /srv/mysql
See? Not scary. Slay. π
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the mysqld, so 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. Like so:
semanage fcontext -a -t mysqld_exec_t '/srv/mysqld/content(/.*)?'
restorecon -R -v /srv/mymysqld_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. So likeβ¦ don't panic when you see the regex-looking stuff. It's giving intentional. β¨
The following file types are defined for mysqld:
π mysqld_db_t
- Set files with the
mysqld_db_ttype, if you want to treat the files as mysqld database content.
Paths:
/var/lib/mysql(-files|-keyring)?(/.*)?, /var/lib/mysql-.*(/.*)?
π mysqld_etc_t
- Set files with the
mysqld_etc_ttype, if you want to store mysqld files in the/etcdirectories.
Paths:
/etc/mysql(/.*)?, /etc/my.cnf.d(/.*)?, /etc/my.cnf
π mysqld_exec_t
- Set files with the
mysqld_exec_ttype, if you want to transition an executable to themysqld_tdomain.
Paths:
/usr/bin/mysqld(-max|-debug)?, /usr/bin/ndbd, /usr/bin/mysqld,
/usr/bin/mariadbd, /usr/libexec/mysqld, /usr/libexec/mariadbd,
/usr/bin/mysql_upgrade, /usr/bin/mariadb-backup, /usr/bin/mariadb-upgrade,
/usr/bin/mysqld_safe_helper, /usr/bin/mariadbd-safe-helper
π mysqld_home_t
- Set files with the
mysqld_home_ttype, if you want to store mysqld files in the users home directory.
Paths:
/root/.my.cnf, /home/[^/]+/.my.cnf
π mysqld_initrc_exec_t
- Set files with the
mysqld_initrc_exec_ttype, if you want to transition an executable to themysqld_initrc_tdomain.
(No paths listed for this one β it's mysterious like that. π¦)
π mysqld_log_t
- Set files with the
mysqld_log_ttype, if you want to treat the data as mysqld log data, usually stored under the/var/logdirectory.
Paths:
/var/log/mysql.*, /var/log/mysql(/.*)?, /var/log/mariadb(/.*)?
π mysqld_safe_exec_t
- Set files with the
mysqld_safe_exec_ttype, if you want to transition an executable to themysqld_safe_tdomain.
Paths:
/usr/bin/mysqld_safe, /usr/bin/mariadbd-safe,
/usr/libexec/mysqld_safe-scl-helper
π mysqld_systemd_helper_exec_t
- Set files with the
mysqld_systemd_helper_exec_ttype, if you want to transition an executable to themysqld_systemd_helper_tdomain.
(Also no paths. We respect the mystery. π)
π mysqld_tmp_t
- Set files with the
mysqld_tmp_ttype, if you want to store mysqld temporary files in the/tmpdirectories.
π mysqld_unit_file_t
- Set files with the
mysqld_unit_file_ttype, if you want to treat the files as mysqld unit content.
Paths:
/usr/lib/systemd/system/mysql.*, /usr/lib/systemd/system/mysqld.*,
/usr/lib/systemd/system/mariadb.*
π mysqld_var_run_t
- Set files with the
mysqld_var_run_ttype, if you want to store the mysqld files under the/runor/var/rundirectory.
Paths:
/run/mysql(/.*)?, /run/mysqld(/.*)?, /run/mariadb(/.*)?,
/var/lib/mysql-.*/mysql(x)?.sock, /var/lib/mysql/mysql(x)?.sock,
/var/tmp/mysql-protected.*(/.*)?
Note: File context can be temporarily modified with thechconcommand. If you want to permanently change the file context you need to use thesemanage fcontextcommand. This will modify the SELinux labeling database. You will need to userestoreconto apply the labels. Temporary vs permanent is lowkey the whole plot twist here, don't forget it. π
π§° COMMANDS π§°
Here's your little toolbox, bestie β every one of these is a semanage subcommand with main character energy:
semanage fcontextcan also be used to manipulate default file context mappings.semanage permissivecan also be used to manipulate whether or not a process type is permissive.semanage modulecan also be used to enable/disable/install/remove policy modules.semanage portcan also be used to manipulate the port definitionssemanage booleancan also be used to manipulate the booleans
And then there's system-config-selinux β a GUI tool available to customize SELinux policy settings. For when you want the whole experience but, like, clicky. π±οΈβ¨
βοΈ AUTHOR βοΈ
This manual page was auto-generated using sepolicy manpage . No human author to thank, just the machine doing its thing. Fr fr. π€π
π SEE ALSO π
Go read these next, they're all part of the same friend group:
selinux(8), mysqld(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8), mysqld_safe_selinux(8), mysqld_systemd_helper_selinux(8)
That's a wrap on the mysqld_selinux(8) page, page mysqld, dated 26-10-06 β go forth and label responsibly, bestie. π«Άπ You ate. π
β¨π¦
π¦ where this page comes from
- opensuse-leap 16.0: selinux-policy-doc 20250627+git412.dbf877ab7-160000.1.1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms