Timeout issue with NFS mounts - Don't transverse file system
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- operating-systems, security
Research direction
Start with control os_spec.rb around line 180 and inspect the find command shown in the timeout output. Reproduce or examine how the control traverses the filesystem, then define completion as checking the intended files without timing out when an NFS mount is present.
Written by the indexing model from the issue text.
Description
We are seeing timeout issues on control os-06 https://github.com/dev-sec/linux-baseline/blob/60ae1a5723bca01a9f87b846ede3f8b23a7bd0ed/controls/os_spec.rb#L180 when transversing the file system hits an NFS mount. The result is a timeout error of mixlibshellout exceeding 600s.
[2017-08-09T03:35:28+00:00] ERROR: Report handler Chef::Handler::AuditReport raised #<Mixlib::ShellOut::CommandTimeout: Command timed out after 600s:
Command exceeded allowed execution time, process terminated
---- Begin output of find / -perm -4000 -o -perm -2000 -type f ! -path '/proc/*' ! -path '/var/lib/lxd/containers/*' -print 2>/dev/null | grep -v '^find:' ----
STDOUT:
STDERR:
---- End output of find / -perm -4000 -o -perm -2000 -type f ! -path '/proc/*' ! -path '/var/lib/lxd/containers/*' -print 2>/dev/null | grep -v '^find:' ----
Ran find / -perm -4000 -o -perm -2000 -type f ! -path '/proc/*' ! -path '/var/lib/lxd/containers/*' -print 2>/dev/null | grep -v '^find:' returned >
Is there a better way to do this control?
- Dominant language
- Ruby
- Stars
- 876
- Forks
- 194
- Avg merge
- 9m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from dev-sec/linux-baseline
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
dev-sec/linux-baseline#191 · 2 comments ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 58/100
dev-sec/linux-baseline#188 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
dev-sec/linux-baseline#173 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
dev-sec/linux-baseline#161 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
dev-sec/linux-baseline#140 · 7 comments · 5 reactions ·
All issues in dev-sec/linux-baseline
Similar issues
-
security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CircuitVerse/CircuitVerse#7967 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
simp/pupmod-simp-stunnel#173 ·
-
Polish QDrantOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
o19s/quepid#1825 · 1 comment ·
Maintainers usually reply within 1 day