- 01 Jun, 2013 1 commit
-
-
Kostya Shishkov authored
-
- 30 Apr, 2013 1 commit
-
-
Diego Biurrun authored
-
- 23 Jan, 2013 4 commits
-
-
Xi Wang authored
A negative `size' will bypass FFMIN(). In the subsequent memcpy() call, `size' will be considered as a large positive value, leading to a buffer overflow. Change the type of `size' to unsigned int to avoid buffer overflow, and simplify overflow checks accordingly. Also change a literal buffer size to use sizeof, and limit the amount of data copied in another memcpy call as well. Signed-off-by: Xi Wang <xi.wang@gmail.com> Signed-off-by: Martin Storsjö <martin@martin.st>
-
Xi Wang authored
Sanity checks like `data + size >= data_end || data + size < data' are broken, because `data + size < data' assumes pointer overflow, which is undefined behavior in C. Many compilers such as gcc/clang optimize such checks away. Use `size < 0 || size >= data_end - data' instead. Signed-off-by: Xi Wang <xi.wang@gmail.com> Signed-off-by: Martin Storsjö <martin@martin.st>
-
Xi Wang authored
A negative `size' will bypass FFMIN(). In the subsequent memcpy() call, `size' will be considered as a large positive value, leading to a buffer overflow. Change the type of `size' to unsigned int to avoid buffer overflow, and simplify overflow checks accordingly. Signed-off-by: Xi Wang <xi.wang@gmail.com> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
Xi Wang authored
Sanity checks like `data + size >= data_end || data + size < data' are broken, because `data + size < data' assumes pointer overflow, which is undefined behavior in C. Many compilers such as gcc/clang optimize such checks away. Use `size < 0 || size >= data_end - data' instead. Signed-off-by: Xi Wang <xi.wang@gmail.com> Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 31 Dec, 2012 1 commit
-
-
Martin Storsjö authored
This avoids having to concatenate them into one buffer before writing them as AMF. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 02 Aug, 2012 1 commit
-
-
Jordi Ortiz authored
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>
-
- 14 Jun, 2012 1 commit
-
-
Samuel Pitoiset authored
This makes sure all incoming packets are read and handled (and reacted to) while sending an FLV stream over RTMP to a server. If there were enough incoming data to fill the TCP buffers, this could potentially make things block at unexpected places. For the upcoming RTMPT support, we need to consume all incoming data before we can send the next request. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 24 May, 2012 1 commit
-
-
Samuel Pitoiset authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 23 May, 2012 1 commit
-
-
Samuel Pitoiset authored
Check malloc calls used by ff_rtmp_packet_create, unify error handling and pass on error codes. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 11 Dec, 2011 1 commit
-
-
Mans Rullgard authored
The existing functions defined in intfloat_readwrite.[ch] are both slow and incorrect (infinities are not handled). This introduces a new header with fast, inline conversion functions using direct union punning assuming an IEEE-754 system, an assumption already made throughout the code. The one use of Intel/Motorola extended 80-bit format is replaced by simpler code sufficient under the present constraints (positive normal values). The old functions are marked deprecated and retained for compatibility. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 03 Jul, 2011 1 commit
-
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 25 May, 2011 2 commits
-
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Some received packets can have size 0. The return value from av_malloc(0) may be NULL, which is ok if the size was 0. On OS X, however, the returned pointer is non-null but leads to crashes when trying to free it. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 04 Apr, 2011 3 commits
-
-
Anton Khirnov authored
-
Anton Khirnov authored
-
Anton Khirnov authored
-
- 19 Mar, 2011 1 commit
-
-
Mans Rullgard authored
Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 07 Mar, 2010 1 commit
-
-
Kostya Shishkov authored
Originally committed as revision 22277 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 30 Jan, 2010 2 commits
-
-
Kostya Shishkov authored
Originally committed as revision 21533 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
Kostya Shishkov authored
Originally committed as revision 21532 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 24 Dec, 2009 1 commit
-
-
Diego Biurrun authored
libavformat/rtmppkt.c:350: warning: unused variable ‘i’ libavformat/rtmppkt.c:349: warning: unused variable ‘base’ Originally committed as revision 20917 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 11 Dec, 2009 1 commit
-
-
Kostya Shishkov authored
Originally committed as revision 20799 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 04 Dec, 2009 1 commit
-
-
Sergiy authored
Patch by Sergiy (piratfmGMAIL) Originally committed as revision 20728 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 03 Dec, 2009 1 commit
-
-
Sergiy authored
track timestamp difference as well. Patch by Sergiy (mail.composeAddress("piratfm","gmail.com")) Originally committed as revision 20714 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 01 Dec, 2009 5 commits
-
-
Kostya Shishkov authored
Originally committed as revision 20686 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
Kostya Shishkov authored
difference, so make all read packets store absolute timestamp. As a consequence, we don't need to track audio/video timestamps separately any longer in protocol handler. Originally committed as revision 20685 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
Kostya Shishkov authored
Originally committed as revision 20684 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
Sergiy authored
Extracted from patch by Sergiy in thread "[PATCH] rtmp-output" Originally committed as revision 20683 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
Kostya Shishkov authored
intermediate buffer for reading value instead in RTMP protocol handler. Originally committed as revision 20682 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 22 Nov, 2009 1 commit
-
-
Kostya Shishkov authored
instead of assuming it should occur right at given position. This helps finding human-readable error descriptions in RTMP server replies. Originally committed as revision 20575 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 08 Nov, 2009 1 commit
-
-
Carl Eugen Hoyos authored
Originally committed as revision 20482 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 18 Oct, 2009 2 commits
-
-
Kostya Shishkov authored
Originally committed as revision 20270 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
Kostya Shishkov authored
Originally committed as revision 20269 to svn://svn.ffmpeg.org/ffmpeg/trunk
-
- 31 Jul, 2009 1 commit
-
-
Kostya Shishkov authored
Originally committed as revision 19556 to svn://svn.ffmpeg.org/ffmpeg/trunk
-