Add scheduled cryptographic verification of root file systme #15677
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This nginx directive is not required anymore since the middleware path was removed.
* remove dead end-point * remove unused imports * remove more dead endpoints and test * remove unnecessary endpoint from device * fix device.get_info SERIAL
* remove unused imports * fix STIG api tests
* convert unused public to private * remove dead endpoints
* Fix bug when retrieving netmask for virt aliases * Reflect change in 25.10 API
We now raise exception if job id does not match an existing job for the user.
…l cores (#15514) * map hyper-threaded ids temps * be sure and add virtual temp to total_temp * Small fix --------- Co-authored-by: Caleb <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add scheduled cryptographic verification of root file system for STIG
This PR should be merged with the same named PRs in
truenas_verifyandscale-build.setup. The audit setup runs at initial install and every OS update. The verification is achieved viatruenas_verify. The install/updatetruenas_verifycall will generate a versioned discrepancy log in the/var/log/auditdirectory.check. Discrepancies found during the scheduled runs are reported in syslog.NOTE: The truenas_verify call can take several seconds on a VM. This increases the initial boot and update boots by the same amount.
CI tests and inclusion in a diagnostic will be added in separate PRs