dev-sec / dev-sec/linux-baseline
Test verification for package removal
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 875
- Forks
- 193
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Description
We need to test a default setting for package removal, since the current state my be a little bit confusing for hardening implementors. See the following discussions:
- https://github.com/hardening-io/chef-os-hardening/pull/12
- https://github.com/hardening-io/ansible-os-hardening/pull/30
Currently, we decided to set the default for package removal to true:
default[:security][:packages][:clean] = true
Contributor guide
No contributing guide indexed for this repository
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
Read the linked Chef and Ansible hardening discussions first, then locate the Linux Baseline configuration and tests covering package removal. Add verification that the package-clean setting defaults to true, and consider the work done when the test clearly confirms that default.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux, ruby
- Domain
- operating-systems, security, testing-qa
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100