In your description above, did you mean:
"Modify a manifest file in dest to contain the wrong hash." rather than
"Modify a manifest file in ~/.cache to contain the wrong hash"?
As I understand it, you are saying that the cache should be ignored in any verify, so changing the cache shouldn't stop the verify succeeding.
Peter,
Is there any chance you could please re-test this on the trunk, as I suspect it has been fixed?
The tests that I added in: /code.launchpad .net/~hooloovoo /duplicity/ add-additional- verify- tests-for- corrupted- archives
https:/
(now merged) were designed to corrupt the destination archives, rather than the cache, and these tests are passing as expected.
In your description above, did you mean:
"Modify a manifest file in dest to contain the wrong hash." rather than
"Modify a manifest file in ~/.cache to contain the wrong hash"?
As I understand it, you are saying that the cache should be ignored in any verify, so changing the cache shouldn't stop the verify succeeding.