Remove random_seed spurious OSSEC alert on first install #2597
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.
Status
Ready for review
Description of Changes
Fixes #2596.
Changes proposed in this pull request:
random_seed
spurious alert on first installTesting
make build-debs
and provision stagingsyscheck
OSSEC alerts related torandom_seed
appear in/var/ossec/logs/alerts/alerts.log
onmon
Deployment
Changes will be deployed in the
securedrop-ossec-agent
debian package.Checklist
We have no testing for
syscheck
(see: #2134) so either inspect the diff manually or follow the test plan.