tldr-pages/tldr

Let's document: SELinux

Open

#11,896 opened on Dec 28, 2023

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Shell (2,507 forks)batch import
help wantedlet's documentnew command

Repository metrics

Stars
 (30,937 stars)
PR merge metrics
 (Avg merge 7d 5h) (321 merged PRs in 30d)

Description

Command description

"A security enhancement to Linux which allows users and administrators more control over access control."

Documentation

https://wiki.gentoo.org/wiki/SELinux/Tutorials/How_SELinux_controls_file_and_directory_accesses https://selinuxproject.org/page/User_Resources

Platform

Linux

Additional information

No response

Commands

  • apol
  • audit2allow #13612
  • audit2why #17202
  • ausearch #18452
  • chcat #18454
  • chcon #2895
  • fixfiles #9161
  • getenforce #12741
  • getsebool #12834
  • matchpathcon #12841
  • newrole #18457
  • restorecon #10550
  • restorecond #18458
  • run_init #18459
  • runcon #3297
  • sealert #18456
  • sechecker
  • secon #12841
  • sediff
  • sedta
  • seinfo
  • seinfoflow
  • selinuxenabled #18444
  • semanage #4353
  • semanage-boolean #12834
  • semanage-fcontext #10550
  • semanage-interface #18460
  • semanage-login #18471
  • semanage-permissive #12834
  • semanage-port #12834
  • semanage-user #18472
  • semodule #18448
  • semodule_expand
  • semodule_link
  • semodule_package
  • semodule_unpackage
  • sesearch #18450
  • sestatus #14037
  • setenforce #12834
  • setfiles #18473
  • setoolsgui
  • setsebool #12834
  • togglesebool #12840

Contributor guide

Research direction
Write tldr pages for the unchecked SELinux commands by studying the provided resources and following the style of existing pages. Focus on commands like apol, sechecker, sediff, sedta, seinfo, seinfoflow, semodule expand, semodule link, semodule package, semodule unpackage, setoolsgui.
Tech stack
shell
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
LinuxSELinux basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70