On 09/18/12 12:36, Ed Flecko wrote:
I have State and Federal regulators that want me to PROVE (since their
only used to looking at Micro$oft servers) my OBSD 5.1 server is up to
date, and there are no outstanding patches that need to be applied.
*I* know that's the case, because I follow the "patch" branch, but how
do I show (i.e., something I could print for them would be best) them
my system is up to date and that all patches have been applied???
Thank you,
Ed
As others have said, you look at the errata page, *and save it*.
For patches, use script(1) to completely log all your FTP's and
compiles & installs. Liberal use of date might be a good idea.
For further completeness you could do an ls -l on the files that
are being patched, do the patches, and then another ls -l to
show that the files were indeed changed.
I've had some mild run-ins with "inspectors" who had zero
understanding of what they were doing. Showing them a non-
Windows machine makes it only worse. But showing the
process via script(1) will make it easier for second level
people to look at your work.
Lastly, take a copy and (paper) mail it to yourself. If the
inspectors then demand proof, let them open it while being
videoed.
Yes, paranoid. (I'm in the US)
--STeve Andre'
