LightningCreations / LightningCreations/lc-coreutils
Test suite: Add extensive fuzzing tests to all coreutils
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Presently the coreutils are only tested for correctness, and only in limited ways.
There are no tests for segmentation faults (aside from some cleverly named tests), or for buffer overrun vulnerabilities. An extensive fuzzer should be run over all lc-coreutils. Additionally, all coreutils should be run automatically with valgrind, failing if any memory errors are detected.
Progress:
- [ ] Valgrind tests for all coreutils
- [x] hashfile
- [x] true
- [x] false
- [ ] echo
- [x] chmod-parse
- [ ] chmod
- [ ] mkdir
- [ ] mknod
- [ ] mkfifo
- [ ] which
- [ ] yes
- [ ] link
- [ ] nohup
- [ ] basename
- [ ] dirname
- [ ] Fuzzing for all coreutils
- [ ] hashfile
- [ ] true
- [ ] false
- [ ] echo
- [ ] chmod-parse
- [ ] chmod
- [ ] mkdir
- [ ] mknod
- [ ] mkfifo
- [ ] which
- [ ] yes
- [ ] link
- [ ] nohup
- [ ] basename
- [ ] dirname
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
Start with the existing correctness tests and the completed Valgrind coverage for hashfile, true, false, and chmod-parse to identify the test setup. Extend Valgrind coverage to the unchecked utilities, then add fuzzing for each listed coreutility. Done means every checklist item is covered and memory errors cause the suite to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, security, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100