On Mon, 23 Dec 2019, alexandre.schm...@gmail.com wrote:
not sure why i just now realize it but
Storing the source path is problematic privacy and security wise
Thanks
What does this means? That it won't be applied?
It only means that you may have to only activate this (or at least the
full path metadata) feature if the user explicitly requests it. Probably
the best way to do that is to introduce a new option of the image2
demuxer, probably with an AV_OPT_TYPE_FLAGS type.
Can you give an example on why this would be a security issue, considering
you already have it anywhere, only not available to filters until now?
Besides, isn't metadata way more sensitive than a simple file path?
The problem is possible leaking of information about the system which
processed the file, because it is typically not disclosed in an output
file where the system stores media files it processes.
Regards,
Marton
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
