Skip to content

F
ffmpeg.wasm-core
Switch branch/tag
  1. 31 Jan, 2017 1 commit
  3. 30 Jan, 2017 13 commits
  5. 29 Jan, 2017 10 commits
  7. 28 Jan, 2017 6 commits
  9. 27 Jan, 2017 7 commits
  11. 26 Jan, 2017 3 commits
    • Michael Niedermayer's avatar
      avcodec/h264dec: Clear ref_count on slice header processing failure · f28299da
      Michael Niedermayer authored 
      Fixes using freed memory
Introduced in 74480198
Fixes: 471/fuzz-1-ffmpeg_VIDEO_AV_CODEC_ID_H264_fuzzer

Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/targets/ffmpegSigned-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      f28299da
    • James Almer's avatar
      avformat/matroskadec: ProjectionPrivate is optional on Equirectangular projections · 1ae39429
      James Almer authored 
      This reflects a recent change to the spec draft.
Signed-off-by: 's avatarJames Almer <jamrial@gmail.com>
      1ae39429
    • Joel Cunningham's avatar
      tcp: set socket buffer sizes before listen/connect/accept · f3778108
      Joel Cunningham authored 
      From e24d95c0e06a878d401ee34fd6742fcaddeeb95f Mon Sep 17 00:00:00 2001
From: Joel Cunningham <joel.cunningham@me.com>
Date: Mon, 9 Jan 2017 13:37:51 -0600
Subject: [PATCH] tcp: set socket buffer sizes before listen/connect/accept

Attempting to set SO_RCVBUF and SO_SNDBUF on TCP sockets after connection
establishment is incorrect and some stacks ignore the set call on the socket at
this point.  This has been observed on MacOS/iOS.  Windows 7 has some peculiar
behavior where setting SO_RCVBUF after applies only if the buffer is increasing
from the default while decreases are ignored.  This is possibly how the incorrect
usage has gone unnoticed

Unix Network Programming Vol. 1: The Sockets Networking API (3rd edition, seciton 7.5):

"When setting the size of the TCP socket receive buffer, the ordering of the
function calls is important.  This is because of TCP's window scale option,
which is exchanged with the peer on SYN segments when the connection is
established. For a client, this means the SO_RCVBUF socket option must be
set before calling connect.  For a server, this means the socket option must
be set for the listening socket before calling listen.  Setting this option
for the connected socket will have no effect whatsoever on the possible window
scale option because accept does not return with the connected socket until
TCP's three-way handshake is complete.  This is why the option must be set on
the listening socket. (The sizes of the socket buffers are always inherited from
the listening socket by the newly created connected socket)"
Signed-off-by: 's avatarJoel Cunningham <joel.cunningham@me.com>
Signed-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
      f3778108