Recherche avancée

Sur d’autres sites (13175)

• lavc/mediacodec_wrapper : fix local reference leaks

  10 mai 2017, par Matthieu Bouron

  lavc/mediacodec_wrapper : fix local reference leaks
  Reviewed-by : Clément Bœsch <u@pkh.me>
  

  • [DH] libavcodec/mediacodec_wrapper.c

• ffmpeg 2 output links - local and remote [on hold]

  17 novembre 2016, par arpak

  i have 2 servers
  and i stream some links with ffmpeg in server1 and server2 via ftp (so i have 2 same outputs)

  ffmpeg -i "http://example.com/video.m3u8" -vcodec h264 -acodec libfdk_aac -y "video1.m3u8" "ftp://user:pass@example.com:21/video2.m3u8" 

  this command create output video1.m3u8 on my local folder and video2.m3u8 on ftp server

  so if cpu is 20% for creating video1.m3u8

  problem is with both of them because if i create (video1.m3u8 and video2.m3u8) then cpu is 40%

  both outputs are same so how can cpu be 20%+20% same as processing 2 seperate links

• avformat/hls : Check local file extensions

  3 juin 2017, par Michael Niedermayer

  avformat/hls : Check local file extensions
  This reduces the attack surface of local file-system
  
  information leaking.
  It prevents the existing exploit leading to an information leak. As
  
  well as similar hypothetical attacks.
  Leaks of information from files and symlinks ending in common multimedia extensions
  
  are still possible. But files with sensitive information like private keys and passwords
  
  generally do not use common multimedia filename extensions.
  
  It does not stop leaks via remote addresses in the LAN.
  The existing exploit depends on a specific decoder as well.
  
  It does appear though that the exploit should be possible with any decoder.
  
  The problem is that as long as sensitive information gets into the decoder,
  
  the output of the decoder becomes sensitive as well.
  
  The only obvious solution is to prevent access to sensitive information. Or to
  
  disable hls or possibly some of its feature. More complex solutions like
  
  checking the path to limit access to only subdirectories of the hls path may
  
  work as an alternative. But such solutions are fragile and tricky to implement
  
  portably and would not stop every possible attack nor would they work with all
  
  valid hls files.
  Developers have expressed their dislike / objected to disabling hls by default as well
  
  as disabling hls with local files. There also where objections against restricting
  
  remote url file extensions. This here is a less robust but also lower
  
  inconvenience solution.
  
  It can be applied stand alone or together with other solutions.
  
  limiting the check to local files was suggested by nevcairiel
  This recommits the security fix without the author name joke which was
  
  originally requested by Nicolas.
  Found-by : Emil Lerner and Pavel Cheremushkin
  
  Reported-by : Thierry Foucu <tfoucu@google.com>
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavformat/hls.c