Re: Timestamp/manifest problems caused by Antivirus
Thomas Leonard <[email protected]> Sun, 5 Jun 2016 14:44:35 +0100
| Newsgroups | gmane.comp.file-systems.zero-install.devel |
|---|---|
| Message-ID | <CAG4opy8=ZbC_mUuJ0+Kz3mJ==svRMAdkV80CUfvMT=wAg+w6cw@mail.gmail.com> |
On 2 June 2016 at 11:14, Bastian Eicher <[email protected]> wrote: >> 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? > The "0install verify" would still have to rely on the actual timestamp > reported by the filesystem. Since we have the .manifest file saved by then, we could offer to fix the problem. > I'd rather not have different verification logic with potentially different > results on first extraction and subsequent checks. -- 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