rlogind_selinux(8)
π rlogind_selinux β the manual page, but make it make sense π
okay so this is rlogind_selinux(8), from the SELinux Policy rlogind corner of the manual-verse. bestie, we're about to get into the whole Security Enhanced Linux Policy for the rlogind processes, and honestly? it's giving "niche but iconic." let's go π«Ά
β¨ NAME β¨
rlogind_selinux β literally the Security Enhanced Linux Policy for the rlogind processes. that's the whole vibe. π
πΈ DESCRIPTION πΈ
so Security-Enhanced Linux secures the rlogind processes via flexible mandatory access control. that's the flex. π₯
the rlogind processes execute with the rlogind_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 rlogind_t
run it, see what's up, no cap. π
π¦ ENTRYPOINTS π¦
the rlogind_t SELinux type can be entered via the rlogind_exec_t file type. that's the doorway, bestie.
the default entrypoint paths for the rlogind_t domain are the following:
/usr/bin/in.rlogind, /usr/lib/telnetlogin, /usr/kerberos/sbin/klogind
three paths. iconic. β¨
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system. yes, every single one gets its own little label. main character energy for everyone.
you can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. SELinux rlogind policy is very flexible, allowing users to setup their rlogind processes in as secure a method as possible. lowkey obsessed with how configurable this is. π
the following process types are defined for rlogind:
rlogind_t
Note:semanage permissive -a rlogind_tcan be used to make the process typerlogind_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated.
so like, permissive = it won't block you, but it WILL still snitch in the logs. π
β BOOLEANS β
SELinux policy is customizable based on least access required. rlogind policy is extremely flexible and has several booleans that allow you to manipulate the policy and run rlogind with the tightest access possible. tightest access = the serve. periodt. π
daemons_dontaudit_schedulingβ 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
fips_modeβ if you want to allow all domains to execute infips_mode, you must turn on thefips_modeboolean. Enabled by default.
setsebool -P fips_mode 1
kerberos_enabledβ if you want to allow confined applications to run with kerberos, you must turn on thekerberos_enabledboolean. Enabled by default.
setsebool -P kerberos_enabled 1
nis_enabledβ if you want to allow system to run with NIS, you must turn on thenis_enabledboolean. Disabled by default.
setsebool -P nis_enabled 1
polyinstantiation_enabledβ if you want to enable polyinstantiated directory support, you must turn on thepolyinstantiation_enabledboolean. Disabled by default.
setsebool -P polyinstantiation_enabled 1
five booleans, all accounted for, not a single one skipped. we don't do that here. π
π PORT TYPES π
SELinux defines port types to represent TCP and UDP ports. yes, ports get types too. everyone's invited to the party.
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 rlogind policy is very flexible, allowing users to setup their rlogind processes in as secure a method as possible.
the following port types are defined for rlogind:
rlogin_port_t
Default Defined Ports:
tcp 543,2105
rlogind_port_t
Default Defined Ports:
tcp 513
yes bestie, there are two of them and they're spelled almost the same. stay woke. π
π MANAGED FILES π
the SELinux process type rlogind_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 is powerful but it's not out here doing DAC's job for it. π«Ά
auth_cache_t
/var/cache/coolkey(/.*)?
auth_home_t
/root/.yubico(/.*)?
/root/.config/Yubico(/.*)?
/root/.google_authenticator
/root/.google_authenticator~
/home/[^/]+/.yubico(/.*)?
/home/[^/]+/.config/Yubico(/.*)?
/home/[^/]+/.google_authenticator
/home/[^/]+/.google_authenticator~
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.*
initrc_var_run_t
/run/sysconfig(/.*)?
/run/utmp
/run/keymap
/run/numlock-on
/run/setleds-on
/run/runlevel.dir
/run/setmixer_flag
/run/bootsplashctl
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
pam_var_run_t
/var/(db|adm)/sudo(/.*)?
/run/sudo(/.*)?
/run/pam_ssh(/.*)?
/run/sepermit(/.*)?
/var/lib/sudo(/.*)?
/run/pam_mount(/.*)?
/run/pam_timestamp(/.*)?
rlogind_tmp_t
(no default paths listed for this one β it speaks for itself β¨)
rlogind_var_run_t
(also no default paths listed, short and mysterious π )
root_t
/sysroot/.aleph-version.json
/sysroot/ostree/deploy/.*-atomic/deploy(/.*)?
/
/initrd
/var/lib/ntp
security_t
/selinux
user_tmp_t
/run/tlog(/.*)?
/run/user/[^/]+
/dev/shm/mono.*
/tmp/.ICE-unix(/.*)?
/tmp/.X11-unix(/.*)?
/dev/shm/pulse-shm.*
/run/user
/tmp/.X0-lock
/tmp/hsperfdata_root
/var/tmp/hsperfdata_root
/home/[^/]+/tmp
/home/[^/]+/.tmp
/run/user/[0-9]+
/tmp/gconfd-[^/]+
var_auth_t
/var/ace(/.*)?
/var/rsa(/.*)?
/var/lib/abl(/.*)?
/var/lib/rsa(/.*)?
/var/lib/pam_ssh(/.*)?
/var/lib/pam_shield(/.*)?
/var/opt/quest/vas/vasd(/.*)?
/var/lib/google-authenticator(/.*)?
wtmpdb_journal_t
/var/lib/wtmpdb/wtmp.db-journal
that's every single file type and every single path, bestie. we do NOT skip entries in this house. π
π§ FILE CONTEXTS π§
SELinux requires files to have an extended attribute to define the file type. it's like a name tag but for files.
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 rlogind policy is very flexible, allowing users to setup their rlogind processes in as secure a method as possible.
π STANDARD FILE CONTEXT π
SELinux defines the file context types for the rlogind, 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 rlogind_exec_t '/srv/rlogind/content(/.*)?'
restorecon -R -v /srv/myrlogind_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. regex girlies rise. πΈ
the following file types are defined for rlogind:
rlogind_exec_t
- Set files with the
rlogind_exec_ttype, if you want to transition an executable to therlogind_tdomain.
Paths:
/usr/bin/in.rlogind, /usr/lib/telnetlogin,
/usr/kerberos/sbin/klogind
rlogind_home_t
- Set files with the
rlogind_home_ttype, if you want to store rlogind files in the users home directory.
Paths:
/root/.rhosts, /root/.rlogin, /home/[^/]+/.rhosts,
/home/[^/]+/.rlogin
rlogind_keytab_t
- Set files with the
rlogind_keytab_ttype, if you want to treat the files as kerberos keytab files.
rlogind_tmp_t
- Set files with the
rlogind_tmp_ttype, if you want to store rlogind temporary files in the/tmpdirectories.
rlogind_var_run_t
- Set files with the
rlogind_var_run_ttype, if you want to store the rlogind files under the/runor/var/rundirectory.
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 β know the difference, or you're gonna have a bad time. π
π COMMANDS π
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 booleanssystem-config-selinuxis a GUI tool available to customize SELinux policy settings. yes, a GUI. for the girlies who like a little pointing and clicking. π±οΈβ¨
π AUTHOR π
This manual page was auto-generated using sepolicy manpage.
(auto-generated and still ate. we love a robot with taste. π€π )
π¦ SEE ALSO π¦
selinux(8), rlogind(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
go read those too, bestie, the lore is deep. π
and that's the whole page!! π this one came from the rlogind source, version/date 26-10-06, and if you flip back to the top it still says rlogind_selinux(8) because some things are simply iconic and don't need to change. mwah! πβ¨
π¦ 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