Recherche avancée

Sur d’autres sites (11795)

• http: avoid out of bound accesses on broken Set-Cookie headers

  8 mars 2018, par wm4

  http: avoid out of bound accesses on broken Set-Cookie headers
  It's trivial to craft a HTTP response that will make the code for
  
  skipping trailing whitespace access and possibly overwrite bytes outside
  
  of the memory allocation. Why this can happen is blindingly obvious : it
  
  accesses cstr[strlen(cstr)-1] without checking whether the string is
  
  empty.
  

  • [DH] libavformat/http.c

• ffmpeg yuvj422p color movie conversion avi2ogv

  28 juillet 2017, par 7Tonin

  While converting avi video to ogv, there is a color problem in output file.
  How can I solve this issue ?
  normal colors altered colors

  Actually a part of the problem is from the player - so weak question

  Command using ffmpeg-3.3.2-1.mga6.tainted :

  ffmpeg -i dscn0146.avi -pix_fmt yuv422p -s 640x480 dscn0146_hq.ogv -y

  And input metadata :

  Guessed Channel Layout for Input Stream #0.1 : mono
  
  Input #0, avi, from 'dscn0146.avi':
  
    Metadata:
  
      encoder         : 
  
      maker           : NIKON
  
      model           : COOLPIX S3500
  
      creation_time   : 2017-07-22 12:09:06
  
    Duration: 00:00:07.33, start: 0.000000, bitrate: 11091 kb/s
  
      Stream #0:0: Video: mjpeg (MJPG / 0x47504A4D), yuvj422p(pc, bt470bg/unknown/unknown), 640x480, 10770 kb/s, 30 fps, 30 tbr, 30 tbn, 30 tbc
  
      Stream #0:1: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 22050 Hz, mono, s16, 352 kb/s
  
  Stream mapping:
  
    Stream #0:0 -> #0:0 (mjpeg (native) -> theora (libtheora))
  
    Stream #0:1 -> #0:1 (pcm_s16le (native) -> vorbis (libvorbis))

  Processes normaly, but fires a warning :

  [swscaler @ 0xd3c3a0] deprecated pixel format used, make sure you did set range correctly

  Output metadata :

  Output #0, ogv, to 'dscn0146_hq.ogv':
  
    Metadata:
  
      model           : COOLPIX S3500
  
      maker           : NIKON
  
      encoder         : Lavf57.71.100
  
      Stream #0:0: Video: theora (libtheora), yuv422p(progressive), 640x480, q=2-31, 200 kb/s, 30 fps, 30 tbn, 30 tbc
  
      Metadata:
  
        encoder         : Lavc57.89.100 libtheora
  
        model           : COOLPIX S3500
  
        maker           : NIKON
  
      Stream #0:1: Audio: vorbis (libvorbis), 22050 Hz, mono, fltp
  
      Metadata:
  
        encoder         : Lavc57.89.100 libvorbis
  
        model           : COOLPIX S3500
  
        maker           : NIKON

• conflicting of headers between ffmpeg and s3

  2 août 2021, par Juliette

  I have the code below in my server.js file for a web app that uses express for the backend and a built create react app that it serves.

  


  require('rootpath')();
const path = require('path');
const express = require('express');
const app = express();
const bodyParser = require('body-parser');
const cookieParser = require('cookie-parser');
const cors = require('cors');

app.use(bodyParser.urlencoded({ extended: false }));
app.use(bodyParser.json());
app.use(cookieParser());

app.use(cors());


app.use(function(req, res, next) {
  res.header("Cross-Origin-Embedder-Policy", "require-corp");
  res.header("Cross-Origin-Opener-Policy", "same-origin");
  next();
});

// Have Node serve the files for our built React app
app.use(express.static(path.resolve(__dirname, 'build')));

// file api routes
app.use('/accounts', require('./accounts/accounts.controller'));

// file api routes
app.use('/files', require('./files/files.controller'));


// All other GET requests not handled before will return our React app
app.get('*', (req, res) => {
    res.sendFile(path.resolve(__dirname, 'build', 'index.html'));
});

// start server
const port = process.env.PORT || 2002;
app.listen(port, () => console.log('Server listening on port ' + port));


  


  The issue here is that I need this segment of code for my ffmpeg file upload to occur otherwise it throws a SharedArrayBuffer error :

  


     app.use(function(req, res, next) {
      res.header("Cross-Origin-Embedder-Policy", "require-corp");
      res.header("Cross-Origin-Opener-Policy", "same-origin");
      next();
    });


  


  However, when I leave this code in, another part of my program breaks down which gets presigned urls from s3 and plays audio. The issue whenever I play audios from my s3 bucket there is this :

  


  ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep


  


  The s3 code is this :

  


  function getTemporaryURL({ data }) {

  const customer_id = data['customer-id'];
  const sound_id = data['sound-id'];
  
  return new Promise((resolve, reject) => {
    //get presigned url

    var myBucket = process.env.NODE_APP_BUCKET_NAME;
    var myKey = "sounds/" + customer_id + "/" + sound_id + ".wav"; 
    const signedUrlExpireSeconds = 120;
    try {
      const url = s3.getSignedUrl('getObject', {
        Bucket: myBucket,
        Key: myKey,
        ResponseContentDisposition: 'attachment',
        Expires: signedUrlExpireSeconds
      });
      resolve(url)
    }
    catch {
      console.log('S3 Object does not exist');
      resolve('');
    }
  });
}


  


  How can I modify my server.js to accommodate both of my needs ?