LibreSign / LibreSign/libresign
Check how we can identify if has problem at SELinux side
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 818
- Forks
- 146
- Avg merge
- 11h 31m
- Merged PRs (30d)
- 326
Description
check how we can identify if is a problem at SELinux side.
Originally posted by @vitormattos in https://github.com/LibreSign/libresign/issues/2327#issuecomment-1976555910
We need to check if have problems at SELinux side during setup validation and return tips to solve the problem. The possible problem is documented at this issue:
- #2327
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the setup-validation flow and the documented SELinux case in issue #2327. Define completion as detecting the relevant SELinux-side setup problem and returning actionable tips for resolving it; the payload names no specific source file or test, so those must be located first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, php
- Domain
- infrastructure, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100