You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Overriding default "Checksums = H" with "Checksums = sha256" results in parse failure from lynis script.
Two machines, identical aide.conf configuration, one passes and one fails. Unable to determine reason for failure, aide.db exists on both, aideinit passes successfully on both. Error received as above when overriding:
Default config (lynis passes)
# if you want to sacrifice security for speed, list some checksum
# explicitly here. H specifies that all checksums compiled in are used.
Checksums = H
Custom config (lynis fails)
# if you want to sacrifice security for speed, list some checksum
# explicitly here. H specifies that all checksums compiled in are used.
Checksums = sha256
Believe acceptable values are sha256, sha512 (both lower case) and H.
Version
Distribution Debian 12
Lynis version 3.1.5
Expected behavior
Lynis should accept the user has specified custom checksums instead of all and not flag an error.
Output
Unable to run with developer profile, currently errors per another report. Output as follows with custom config
The text was updated successfully, but these errors were encountered:
Describe the bug
Overriding default "Checksums = H" with "Checksums = sha256" results in parse failure from lynis script.
Two machines, identical aide.conf configuration, one passes and one fails. Unable to determine reason for failure, aide.db exists on both, aideinit passes successfully on both. Error received as above when overriding:
Default config (lynis passes)
Custom config (lynis fails)
Believe acceptable values are sha256, sha512 (both lower case) and H.
Version
Expected behavior
Lynis should accept the user has specified custom checksums instead of all and not flag an error.
Output
Unable to run with developer profile, currently errors per another report. Output as follows with custom config
The text was updated successfully, but these errors were encountered: