| Warning | ||
|---|---|---|
| ||
If using Fedora to audit or report To audit the fixity of federated files, the federation configuration property "contentBasedSha1" property must be set to "true" in the federation configuration. |
When a federated file is first accessed, a sha1 SHA-1 hash is computed and cached. This may take a while for large files. At any point, just like any other As is the case for any Fedora node, a request may be made through a web browser or client to recompute and compare the checksum of that a file.
In the HTML view, beside the "digest" property for the content, there's a "check fixity" link which will recompute the sha1 checksum and compare it with the last computed oneolder SHA-1. This feature is documented.
To build a reasonable audit, one needs toshould:
- ensure that all files are visited/accessed to ensure a baseline sha1 SHA-1 is computed (will . This operation can take a very long time for larger large repositories).
- script a period periodic fixity request against each object which looks for the SUCCESS assertion in the response.