- 19 Dec, 2019 1 commit
-
-
James Almer authored
They have been removed altogether without a compat implementation, and are either no-ops or return NULL. This fixes compiler warnings about checks always evaluating to false, and leaks of allocated mutexes. Signed-off-by: James Almer <jamrial@gmail.com>
-
- 11 Dec, 2019 1 commit
-
-
Jun Zhao authored
supporting both pre-1.1.0 and post-1.1.0 version of the OpenSSL library as the link: https://wiki.openssl.org/index.php/Library_InitializationSigned-off-by: Jun Zhao <barryjzhao@tencent.com>
-
- 17 Aug, 2018 1 commit
-
-
Martin Storsjö authored
This was a typo in 0671eb23, spotted by Chris Carroux. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 26 Dec, 2017 1 commit
-
-
wm4 authored
It's completely absurd that libavcodec would care about libavformat locking, but it was there because the lock manager was in libavcodec. This is more stright forward. Changes ABI, but we don't require ABI compatibility currently.
-
- 03 Nov, 2017 1 commit
-
-
James Almer authored
Cosmetic change, reduces differences with libav.
-
- 20 Jun, 2017 1 commit
-
-
Martin Storsjö authored
The rtmp protocol uses nonblocking reads, to poll for incoming messages from the server while publishing a stream. Prior to 94599a6d and d13b124e, the tls protocol handled the nonblocking flag, mostly as a side effect from not using custom IO callbacks for reading from the socket. When custom IO callbacks were taken into use in d15eec4d, the handling of a nonblocking socket wasn't necessary for the default blocking mode any longer. The code was simplified, since it was overlooked that other code within libavformat actually used the tls protocol in nonblocking mode. This fixes publishing over rtmps, with the openssl backend. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 02 Jun, 2017 1 commit
-
-
Diego Biurrun authored
TLS is currently implemented over either OpenSSL or GnuTLS, with more backends likely to appear in the future. Currently, those backend libraries are part of the protocol names used during e.g. the configure stage of a build. Hide those details behind a generically-named declaration for the TLS protocol to avoid leaking those details into the configuration stage.
-
- 17 Dec, 2016 1 commit
-
-
Jay Ridgeway authored
Support url_get_file_handle on TLS streams. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 31 Oct, 2016 1 commit
-
-
Mark Thompson authored
The use of TLSv1_*_method() disallows newer protocol versions; instead use SSLv23_*_method() and then explicitly disable the deprecated protocol versions which should not be supported.
-
- 30 Oct, 2016 1 commit
-
-
Mark Thompson authored
The use of TLSv1_*_method() disallows newer protocol versions; instead use SSLv23_*_method() and then explicitly disable the deprecated protocol versions which should not be supported. Fixes ticket #5915.
-
- 25 Oct, 2016 1 commit
-
-
Martin Storsjö authored
When the macro is expanded with a semicolon following it and the macro itself contains a semicolon, we ended up in double semicolons, which is treated as a statement that disallows further declarations. This avoids errors about mixed declarations and statements on gcc, after ee050797. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 23 Oct, 2016 1 commit
-
-
Matt Oliver authored
Further simplifications by Martin Storsjö, to minimize the diff. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 21 Oct, 2016 1 commit
-
-
Matt Oliver authored
Fixes #5675 Signed-off-by: Matt Oliver <protogonoi@gmail.com>
-
- 22 Feb, 2016 1 commit
-
-
Anton Khirnov authored
Instead of a linked list constructed at av_register_all(), store them in a constant array of pointers. Since no registration is necessary now, this removes some global state from lavf. This will also allow the urlprotocol layer caller to limit the available protocols in a simple and flexible way in the following commits.
-
- 27 May, 2015 2 commits
-
-
wm4 authored
There is no need to have this mess in network.c. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
wm4 authored
Move the OpenSSL and GnuTLS implementations to their own files. Other than the connection code (including options) and some boilerplate, no code is actually shared. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 26 May, 2015 2 commits
-
-
wm4 authored
There is no need to have this mess in network.c. Signed-off-by: Martin Storsjö <martin@martin.st>
-
wm4 authored
Move the OpenSSL and GnuTLS implementations to their own files. Other than the connection code (including options) and some boilerplate, no code is actually shared. Signed-off-by: Martin Storsjö <martin@martin.st>
-