On Sat, 13 Feb 2016, Marton Balint wrote:
On Thu, 11 Feb 2016, Marton Balint wrote:
Currently it is broken when explicitly using the file protocol, it uses an
insecure temporary file name, and in commit b4431c80 disabling the option
by
default was already considered. Also it is not very con
On Thu, 11 Feb 2016, Marton Balint wrote:
Currently it is broken when explicitly using the file protocol, it uses an
insecure temporary file name, and in commit b4431c80 disabling the option by
default was already considered. Also it is not very consistent to have such an
option for one particu
Currently it is broken when explicitly using the file protocol, it uses an
insecure temporary file name, and in commit b4431c80 disabling the option by
default was already considered. Also it is not very consistent to have such an
option for one particular muxer.
Signed-off-by: Marton Balint
---
