the *security=none* flag, then SMACK is not enabled. Furthermore, `systemd`
starts the loading of **SMACK** rules during start-up. If this start-up process
is interfered with, then **SMACK** will not run. Alternatively, new policies can
-be added with `smackload` allowing unforseen privileges to alternative
+be added with `smackload` allowing unforeseen privileges to alternative
applications/executables.
Another intrusion on the kernel level is to rebuild the kernel (as it is
- e: Effective: This means the capability is “activated”.
- p: Permitted: This means the capability can be used/is allowed.
- i: Inherited: The capability is kept by child/subprocesses upon execve() for
- example.
\ No newline at end of file
+ example.