paranoid as I am, I am concerned about somebody
exchanging the new database with a forged one.
This could be made a little harder if aide would
calculate cryptographic checksums of the new database
file on the fly while creating it, and write these
checksums to its output as part of the aide report.
The code to create such a checksum should already be
present in aide (*grins*), so implementing this
should be no big challenge.
Log in to post a comment.