Fulltext results:
- syslog-ng @documentation:rsbac_handbook:configuration_basics:administration_examples
- # (defaults are 0, 0, 0600) # Replace secoff with whoever user you want to use for # ... e policy protecting syslog-ng-rsbac owner(secoff); group(secoff); perm(0600); # default owner, group, and permissions for created... # (defaults are 0, 0, 0700) # Replace secoff dir_owner(secoff); dir_group(seco
- upgrade_and_migration @documentation:rsbac_handbook:maintenance
- ogging source with "cat /proc/rsbac-info/rmsg" as secoff (uid 400). If you want, you can install rsbac_klo... ogging source with "cat /proc/rsbac-info/rmsg" as secoff (uid 400). If you want, you can install rsbac_klo... n tools contrib or "cat /proc/rsbac-info/rmsg" as secoff (uid 400). * RC: Add GET_STATUS_DATA right for ... n tools contrib or "cat /proc/rsbac-info/rmsg" as secoff (uid 400). * RC: Add GET_STATUS_DATA and MODIFY
- cap @documentation:rsbac_handbook:configuration_basics:setting_up_modules
- o add a DAC_READ_SEARCH and KILL capabilities for secoff, so that this user can browse the complete filesystem: attr_set_user CAP secoff min_caps DAC_READ_SEARCH KILL \\ ---- **Table o
- first_boot @documentation:rsbac_handbook:installation
- ng is fine. You will be able to login as root and secoff (sometimes called so, it's the Security Officer),
- acl @documentation:rsbac_handbook:security_models
- maintaining a sensible group structure, e.g. user secoff. Just to mention: Similarities to other PC netwo
- vum @documentation:rsbac_handbook:security_models
- "I have no name" - user 1/root is not known. As secoff (uid 0/400), copy group and user root from set 0
- daz @documentation:rsbac_handbook:configuration_basics:setting_up_modules
- . Security Officer :) (1): <code> # attr_set_user secoff daz_role 1 </code> ===== Running, testing, trou