Recherche avancée

Sur d’autres sites (8142)

• Matomo will now pay researchers 5,000 USD for a critical security vulnerability

  7 mai 2020, par Matomo Core Team
  Matomo Analytics is the leading open-source web analytics solution, designed to give you conclusive insights while respecting your user’s privacy, and keeping your data secure. We’re so proud Matomo is trusted with the analytics data of more than 1 million sites worldwide.

  Although we have had an excellent security track record so far, we recognise security is an ongoing challenge and requires constant vigilance. With this announcement we’re showing our commitment to reward those who help us maintain the highest security in Matomo.

  New bounty of 5,000 USD for a CRITICAL security issue responsibly disclosed to us

  We’re now paying 5,000 USD or 4,700 EUR for each critical vulnerability found, and responsibly disclosed to us. (Previously this bounty was less than 1,000USD.) 

  A Critical Issue in Matomo means an issue in our latest official release at : builds.matomo.org/latest.zip as installed on a typical server (and possibly using any of our official plugins by Matomo or InnoCraft from the Marketplace).

  If you can gain remote code execution on the server (i.e. RCE), or if you’re able to delete data with an HTTPS request (i.e. SQL Injection), this may qualify as a Critical Issue. Please report it on Hackerone.

  Matomo keeps your data secure

  The Matomo team has always been committed to achieving the highest standard of security. For example, Matomo was one of the first open-source projects in the world to launch a public bug bounty in January 2011. Every year many researchers, users and customers review the Matomo source code, and overall we’ve rewarded dozens of researchers over the years for their work in keeping Matomo data safe.

  How to make your Matomo server even more secure ?

  Check out our recommendations in How to configure Matomo for Security

   

• Displaying an AVFrame on the screen with SDL 2.0

  22 septembre 2013, par jsp99

  I am working on some code with the help of this tutorial and using the latest development libraries of ffmpeg and SDL. I am stuck at the point where I have to display the decoded frame (AVFrame) on the screen. I am inclined to do the above task i.e, Displaying the AVFrame on screen using the latest API of SDL 2.0 (Using Renderers and Textures alongside the usage of SDL_Window). Frankly speaking, I am not an expert in SDL_Renderer, SDL_Texture and the functions associated with them. But I am reading the documentation in the official site of SDL 2.0 and working my way through them.

  Is there a way to do the following using SDL 2.0 API :

  • Convert the native frame format to a flavour of YUV and display it.

    (OR)

  • If it is possible, display the frame without having to convert it from native format.

  I want to do the above using Renderers and Textures. There doesn't seem to be an easy way to work with them.

  Can anyone guide me through the steps to do the above tasks ?

  PS : Though I have not explicitly tried it, I came across some ways to display AVFrame on the screen by converting the AVFrame format(native) to RGB. But I do not want the native frame format (which is mostly YUV) to RGB conversion, as it is computationally expensive.

  Converting between formats is done by sws_scale()

• Why the output of the ffmpeg-python doesn't match the image shape ?

  9 novembre 2019, par Swi Jason

  I used the ffmpeg-python module to convert video to images. Specifically, I used the code provided by the official git repo of ffmpeg-python, as below

  out, _ = (
  
      ffmpeg
  
      .input(in_filename)
  
      .filter('select', 'gte(n,{})'.format(frame_num))
  
      .output('pipe:', vframes=1, format='image2', vcodec='mjpeg')
  
      .run(capture_stdout=True)
  
  )
  
  im = np.frombuffer(out, 'uint8')
  
  print(im.shape[0]/3/1080)
  
  # 924.907098765432

  The original video is of size (1920, 1080) and pix_fmt ’yuv420p’, but the outputs of the above code is not 1920.

  I have figured out by myself that the output of ffmpeg.run() is not a decoded image array, but a byte string encoded by JPEG format. To restore the image into a numpy array, simply use the cv2.imdecode() function. For example,

  im = cv2.imdecode(im, cv2.IMREAD_COLOR)

  However, I can’t use opencv on my embeded Linux system. So my question now is that, can I get numpy output from ffmpeg-python directly, without the need of converting it by opencv ?