Recherche avancée

Sur d’autres sites (6158)

• Ffmpeg gets aborted in an Electron sandboxed application

  6 décembre 2017, par YoannM

  I have an Electron app, published on the Mac AppStore, and sandboxed.

  I’m trying to add a new feature that will encode/decode videos on the fly so I can stream more video formats in an Electron context.

  I’m using fluent-ffmpeg and a static exec of ffmpeg.

  Everything works awesomely, I’ve uploaded the sandboxed app to Apple, and got rejected because ffmpeg is using by default a secure transport protocol which is using non-public API, this is what they’ve sent me with the rejection :

  Your app uses or references the following non-public API(s) :

  ’/System/Library/Frameworks/Security.framework/Versions/A/Security’

   : SecIdentityCreate

  Alright, after much investigation, it appears that I have to compile ffmpeg myself with a --disable-securetransport flag. Easy enough, I do it using the same config as the static build I’ve downloaded simply adding the new flag.

  I manage to install every dependencies needed, except libxavs, no big deal I guess and simply remove its flag from the configure command :

  ./configure \
  
  --cc=/usr/bin/clang \
  
  --prefix=/opt/ffmpeg \
  
  --extra-version=tessus \
  
  --enable-avisynth \
  
  --enable-fontconfig \
  
  --enable-gpl \
  
  --enable-libass \
  
  --enable-libbluray \
  
  --enable-libfreetype \
  
  --enable-libgsm \
  
  --enable-libmodplug \
  
  --enable-libmp3lame \
  
  --enable-libopencore-amrnb \
  
  --enable-libopencore-amrwb \
  
  --enable-libopus \
  
  --enable-libsnappy \
  
  --enable-libsoxr \
  
  --enable-libspeex \
  
  --enable-libtheora \
  
  --enable-libvidstab \
  
  --enable-libvo-amrwbenc \
  
  --enable-libvorbis \
  
  --enable-libvpx \
  
  --enable-libwavpack \
  
  --enable-libx264 \
  
  --enable-libx265 \
  
  --enable-libxvid \
  
  --enable-libzmq \
  
  --enable-libzvbi \
  
  --enable-version3 \
  
  --pkg-config-flags=--static \
  
  --disable-securetransport \
  
  --disable-ffplay

  With the new ffmpeg exec, everything still works as expected. But once I’m packaging, signing and sandboxing the app, ffmpeg stops working as soon as I try to launch it throwing this error :

  An error occurred ffmpeg was killed with signal SIGABRT Error: ffmpeg was killed with signal SIGABRT
  
      at ChildProcess.eval (webpack:///../node_modules/fluent-ffmpeg/lib/processor.js?:180:22)
  
      at emitTwo (events.js:125:13)
  
      at ChildProcess.emit (events.js:213:7)
  
      at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

  I’ve tried to remove the --disable-securetransport flag, see if it could have messed with something, same result.

  I’ve tried to compile on a Linux machine, just to see if it could help, same thing.

  As soon as I’m using my custom compiled exec it doesn’t work in the sandbox, but when using the static one, everything is ok (after I xattr it, because it’s quarantined and blocked in sandbox).

  The only thing I’ve noticed that seems odd is that my custom compilation is only 20mo or so, when the static install I’ve downloaded is 43mo.

  I’m really stuck with this.

• Unable to run a program in PATH from Java code

  17 novembre 2012, par user1831004

  I am developing a Red5 media server application on a Mac (Dynamic Web Project in Eclipse). The app has to invoke FFMPEG to convert the video to a different format.

  I added "/Applications/FFMPEG" to PATH variable by running the following command in Terminal :

  echo 'export PATH=/Applications/FFMPEG:$PATH' >> ~/.profile

  When I invoke FFMPEG from terminal, it works fine. However, every time I run it from Java code with :

  Process p = Runtime.getRuntime().exec("ffmpeg");
  
  p.waitFor();

  I get the following error :

  Cannot run program "ffmpeg": error=2, No such file or directory

  I thought this might be a security limitation specific to the type of project, but even a simple Java program produces the same result. What am I missing ?

  ---

  Changing "ffmpeg" to full path of the application works, but I don't want to upload FFMPEG into the same directory as Red5 on a production server.

• avformat/http: add "Opening" info logging to ff_http_do_new_request

  13 décembre 2017, par Aman Gupta

  avformat/http: add "Opening" info logging to ff_http_do_new_request
  This mimics logging that was added in 53e0d5d7247 for security
  
  purposes.
  Signed-off-by : Aman Gupta <aman@tmm1.net>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavformat/http.c