crack_selinux(8)
π
crack_selinux(8) β the crack SELinux page, but make it make sense
okay so bestie, buckle up β this is the SELinux policy page for the crack processes, and we're gonna get into it. π
β¨ NAME β¨
crack_selinux β the Security Enhanced Linux Policy for the crack processes π«Ά
πΈ DESCRIPTION πΈ
So like, Security-Enhanced Linux secures the crack processes via flexible mandatory access control. That's the whole vibe β mandatory access control, no cap, the policy is literally in charge. π
Your crack processes run with the crack_t SELinux type. Wanna check if you've got these processes running? Just execute the ps command with the -Z qualifier, like:
ps -eZ | grep crack_t
That's it, that's the check. Slay. β¨
π¦ ENTRYPOINTS π¦
The crack_t SELinux type can be entered via the crack_exec_t file type.
And the default entrypoint paths for the crack_t domain are literally these:
/usr/bin/crack_[a-z]*, /usr/bin/cracklib-[a-z]*
Those are your doors in. πͺ
π PROCESS TYPES π
SELinux defines process types (domains) for each process running on the system β yes, every single one, it's giving main character energy for every process tbh.
You can see the context of a process using the -Z option to ps.
Policy governs the access confined processes have to files. The SELinux crack policy is very flexible, allowing users to setup their crack processes in as secure a method as possible. π
The following process types are defined for crack:
crack_t
Note:semanage permissive -a crack_tcan be used to make the process typecrack_tpermissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. So like, you're not off the hook β the receipts still show up. π§Ύπ
π BOOLEANS π
SELinux policy is customizable based on least access required. The crack policy is extremely flexible and has several booleans that allow you to manipulate the policy and run crack with the tightest access possible. Locked down and cute about it. π
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
That's the one boolean listed here, and yes it's enabled by default, so it's already serving. π
π MANAGED FILES π
The SELinux process type crack_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 isn't doing everything for you, bestie. π
crack_db_t/usr/share/cracklib(/.*)?/var/cache/cracklib(/.*)?/usr/lib/cracklib_dict.*
crack_tmp_t- (no default paths listed for this one, it's a mystery but we move π§)
π FILE CONTEXTS π
SELinux requires files to have an extended attribute to define the file type. It's literally how it knows what's what.
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 crack policy is very flexible, allowing users to setup their crack processes in as secure a method as possible. (Yes, same energy as before β it's a whole theme. π)
β STANDARD FILE CONTEXT β
SELinux defines the file context types for the crack. 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 this:
semanage fcontext -a -t crack_exec_t '/srv/crack/content(/.*)?'
restorecon -R -v /srv/mycrack_content
Note: SELinux often uses regular expressions to specify labels that match multiple files. Regex girlies rise. π₯
The following file types are defined for crack:
crack_db_t
- Set files with the
crack_db_ttype, if you want to treat the files as crack database content.
Paths:
/usr/share/cracklib(/.*)?, /var/cache/cracklib(/.*)?, /usr/lib/cracklib_dict.*
crack_exec_t
- Set files with the
crack_exec_ttype, if you want to transition an executable to thecrack_tdomain.
Paths:
/usr/bin/crack_[a-z]*, /usr/bin/cracklib-[a-z]*
crack_tmp_t
- Set files with the
crack_tmp_ttype, if you want to store crack temporary files in the/tmpdirectories.
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'll be confused later, fr fr. π
π«Ά 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 booleancan also be used to manipulate the booleans.system-config-selinuxis a GUI tool available to customize SELinux policy settings. Yes, a GUI β for when the terminal is doing too much. π
π§ AUTHOR π§
This manual page was auto-generated using sepolicy manpage . β not me hand-writing it at 2am, the machine did that. π€β¨
π SEE ALSO π
selinux(8), crack(8), semanage(8), restorecon(8), chcon(1), sepolicy(8), setsebool(8)
Go read those too, bestie, iykyk. π
and that's the whole page!! π this beauty is crack manual page, dated 26-10-06, and it lives at crack_selinux(8). periodt. ππ¦β¨
π¦ 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