Re: Timestamp/manifest problems caused by Antivirus

On 31 May 2016 at 09:08, Bastian Eicher <[email protected]> wrote:
>> Does sound like a scanner bug. Could we set the file as read-only to
>> prevent it updating it?
> Zero Install for Windows already does this. The current workflow is:
> 1. Extract files from archive
> 2. Set timestamps for extracted files as specified in the archive
> 3. Generate and compare manifest digest
> 4. Make files immutable by setting "Deny Write to All" ACL
> The scanner seems to be sneaking in between steps 2 and 3. I've submitted a
> bug report to the manufacturer so hopefully this will get fixed.

Ah, so we're reading the timestamps directly from the archive, not
looking at what the archiver produced? In that case, perhaps we could
use the timestamp from the archive to generate the manifest?

> However, I still wonder whether including timestamps in the manifest digest
> hasn't caused more trouble than its worth in the long run.
> On the other hand, introducing YAMF (Yet Another Manifest Format) probably
> wouldn't exactly "simplify" things either. ;)

Perhaps, but we'd still want to fix it for the programs that do care,
and if we fixed it for them then it would work everywhere.



-- 
Dr Thomas Leonard        http://roscidus.com/blog/
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity 
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e