[FFmpeg-devel] modification time in libavformat (.MOV files)
alx.sukhanov at gmail.com
Sat Feb 15 04:39:18 CET 2014
On Fri, Feb 14, 2014 at 4:47 PM, Michael Niedermayer <michaelni at gmx.at>wrote:
> On Fri, Feb 14, 2014 at 07:18:13PM +0100, Ayke van Laethem wrote:
> > Hi,
> > I have been working on a patch to fix a bug I discovered in the saving
> > of .MOV files. In short, the creation time of individual streams isn't
> > copied as it says they will be (it is copied from the output .MOV file
> > instead, which is null if -map_metadata isn't used), and modification
> > time is set to the creation time.
> > This SuperUser post is in part about this issue:
> > I can add a way to reproduce the issue if needed. I will certainly do
> > that before (or while) submitting the patch.
> > The patch I wrote seems to work correctly, but fate fails. I assume
> > this is because the metadata is changed so the output file has a
> > different hash than what fate expects. Updating the hash so it
> > includes the correct creation_time should be easy, but the
> > modification time will be different each time.
> > So here is the question. Should the modification time be set at all? I
> > think it would be the more 'correct' way to go, but it makes testing
> > harder. If modification time will be set, how should testing be done?
> storing the current time in files without the users knowledge poses
> a risk to privacy and security.
> Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
> it is not once nor twice but times without number that the same ideas make
> their appearance in the world. -- Aristotle
> ffmpeg-devel mailing list
> ffmpeg-devel at ffmpeg.org
Sorry for dumb question, but what is a risk to privacy and security?
More information about the ffmpeg-devel