Fix clam scanning path issues when using mod_vroot #21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using mod_vroot, the chroot path gets prepended to the scan path when it isn't needed. This fixes that problem. (I can't remember exactly why it was that this is needed because it's been so long since I did my investigation, and I had forgotten about submitting a PR for it, but without it doing non-stream scans with mod_vroot doesn't work because the path passed to clamd looks like /vroot/path/vroot/path/jailed/path rather than just /vroot/path/jailed/path).