Recherche avancée

Sur d’autres sites (8684)

• curl | tar - gzip : stdin : not in gzip format

  17 avril 2021, par Jonathan Ong

  I'm trying to install ffmpeg on travis with this command :

  



  curl http://johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz | tar -C /usr/local/bin/ -xvz


  



  I get this error :

  



  $ curl http://johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz | tar -C /usr/local/bin/ -xvz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time      Current
                                 Dload  Upload   Total   Spent    Left      Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
gzip: stdin: not in gzip format
tar: Child died with signal 13
tar: Error is not recoverable: exiting now
The command "curl http://johnvansickle.com/ffmpeg/releases/ffmpeg-release-64bit-static.tar.xz | tar -C /usr/local/bin/ -xvz" failed and exited with 2 during .


  



  however, it works locally on OS X. what's going on ?

  


• Is there risk of shell/command injection when using FFmpeg or when there's no user input ?

  10 mai 2021, par Tris

  I am new when it comes to thinking about the security of my web applications. I have done research on shell injections and most of the time they say to just avoid using shell/command calls in the web applications. However, my alternative seems to limit which browsers clients can use. So I would prefer executing a shell command in my nodejs server. I am using FFmpeg and calling it through system command in nodejs child processes.

  


  I have a FFmpeg bash script like so :

  


  VIDSOURCE="rtsp:cameraurl"
AUDIO_OPTS="-c:a aac -b:a 160000 -ac 2"
VIDEO_OPTS="-s 854x480 -c:v libx264 -b:v 800000"
OUTPUT_HLS="-hls_time 10 -hls_list_size 10 -start_number 1 -hls_wrap 10"
ffmpeg -i "$VIDSOURCE" -y $AUDIO_OPTS $VIDEO_OPTS $OUTPUT_HLS mystream.m3u8


  


  I am wondering if I should worry about shell injection risk and if I should try another approach. I don't think there is any user input in this besides my own hard coded inputs. Therefore, I think it should be safe to use this script in a web browser... I just want to be safe and be sure. Thank you !

  


• Error happened : 'spawn ffmpeg ENOENT', Node.js & FFmpeg

  4 juin 2021, par Esha Joshi

  I'm really struggling to get ffmpeg working to read .webm data from a file and write that data to a .pcm file. I have ffmpeg at the file location and have made it executable with the sudo chmod +x ffmpeg command.

  


  Does anyone have any idea how I can fix this ? Thank you in advance !

  


         const ffmpeg = require('fluent-ffmpeg')
       const ffmpegPath = 'C:\\usr\\local\\bin\\ffmpeg.exe'
       ffmpeg.setFfmpegPath(ffmpegPath)

      // Now read from the test-video .webm file
        const inputFile = 'test-video.webm'
        var inputStream = fs.createReadStream(inputFile)
        inputStream.on('error', function(error) {
            console.log(`\tError with reading from input stream: ${error}`)
        })

        // And write that data to the .pcm audio file
        var outputFileName = 'test-extracted-audio.pcm'
        var outputStream = fs.createWriteStream(outputFileName)

        var ffmpeg = child_process.spawn('ffmpeg', ['-y', '-i', '-vn', '-ac', '1', '-ar', '16000', 'pcm_s16le'])
        inputStream.pipe(ffmpeg.stdin)
        ffmpeg.stdout.pipe(outputStream)

        ffmpeg.stderr.on('data', function (data) {
            // console.log(data.toString())
            console.log(`DATA FROM FFMPEG: ${data}`)
        })

        ffmpeg.stderr.on('end', function () {
            console.log('\tWebm -> PCM File has been converted succesfully')
        })
        
        ffmpeg.stderr.on('exit', function () {
            console.log('\tFFMPEG child process exited')
        })
        
        ffmpeg.stderr.on('close', function() {
            console.log('\t...Closing time! Bye')
        })