Go to the documentation of this file.
35 #include <openssl/bio.h>
36 #include <openssl/ssl.h>
37 #include <openssl/err.h>
46 #if OPENSSL_VERSION_NUMBER >= 0x1010000fL
51 #if HAVE_THREADS && OPENSSL_VERSION_NUMBER < 0x10100000L
52 #include <openssl/crypto.h>
56 if (
mode & CRYPTO_LOCK)
61 #if !defined(WIN32) && OPENSSL_VERSION_NUMBER < 0x10000000
62 static unsigned long openssl_thread_id(
void)
64 return (intptr_t) pthread_self();
78 #if OPENSSL_VERSION_NUMBER < 0x10100000L
80 SSL_load_error_strings();
82 #if HAVE_THREADS && OPENSSL_VERSION_NUMBER < 0x10100000L
83 if (!CRYPTO_get_locking_callback()) {
86 if (!openssl_mutexes) {
91 for (
i = 0;
i < CRYPTO_num_locks();
i++)
93 CRYPTO_set_locking_callback(openssl_lock);
94 #if !defined(WIN32) && OPENSSL_VERSION_NUMBER < 0x10000000
95 CRYPTO_set_id_callback(openssl_thread_id);
111 #if HAVE_THREADS && OPENSSL_VERSION_NUMBER < 0x10100000L
112 if (CRYPTO_get_locking_callback() == openssl_lock) {
114 CRYPTO_set_locking_callback(
NULL);
115 for (
i = 0;
i < CRYPTO_num_locks();
i++)
128 int err = SSL_get_error(
c->ssl,
ret);
129 if (err == SSL_ERROR_WANT_READ || err == SSL_ERROR_WANT_WRITE)
140 SSL_shutdown(
c->ssl);
144 SSL_CTX_free(
c->ctx);
146 #if OPENSSL_VERSION_NUMBER >= 0x1010000fL
147 if (
c->url_bio_method)
148 BIO_meth_free(
c->url_bio_method);
156 #if OPENSSL_VERSION_NUMBER >= 0x1010000fL
158 BIO_set_data(
b,
NULL);
173 #if OPENSSL_VERSION_NUMBER >= 0x1010000fL
174 #define GET_BIO_DATA(x) BIO_get_data(x)
176 #define GET_BIO_DATA(x) (x)->ptr
185 BIO_clear_retry_flags(
b);
187 BIO_set_retry_read(
b);
199 BIO_clear_retry_flags(
b);
201 BIO_set_retry_write(
b);
209 if (cmd == BIO_CTRL_FLUSH) {
210 BIO_clear_retry_flags(
b);
221 #if OPENSSL_VERSION_NUMBER < 0x1010000fL
223 .type = BIO_TYPE_SOURCE_SINK,
224 .name =
"urlprotocol bio",
252 p->
ctx = SSL_CTX_new(
c->listen ? SSLv23_server_method() : SSLv23_client_method());
258 SSL_CTX_set_options(p->
ctx, SSL_OP_NO_SSLv2 | SSL_OP_NO_SSLv3);
260 if (!SSL_CTX_load_verify_locations(p->
ctx,
c->ca_file,
NULL))
263 if (
c->cert_file && !SSL_CTX_use_certificate_chain_file(p->
ctx,
c->cert_file)) {
265 c->cert_file, ERR_error_string(ERR_get_error(),
NULL));
269 if (
c->key_file && !SSL_CTX_use_PrivateKey_file(p->
ctx,
c->key_file, SSL_FILETYPE_PEM)) {
271 c->key_file, ERR_error_string(ERR_get_error(),
NULL));
278 SSL_CTX_set_verify(p->
ctx, SSL_VERIFY_PEER|SSL_VERIFY_FAIL_IF_NO_PEER_CERT,
NULL);
285 #if OPENSSL_VERSION_NUMBER >= 0x1010000fL
286 p->url_bio_method = BIO_meth_new(BIO_TYPE_SOURCE_SINK,
"urlprotocol bio");
293 bio = BIO_new(p->url_bio_method);
294 BIO_set_data(bio,
c->tcp);
299 SSL_set_bio(p->
ssl, bio, bio);
300 if (!
c->listen && !
c->numerichost)
301 SSL_set_tlsext_host_name(p->
ssl,
c->host);
302 ret =
c->listen ? SSL_accept(p->
ssl) : SSL_connect(p->
ssl);
307 }
else if (
ret < 0) {
Filter the word “frame” indicates either a video frame or a group of audio as stored in an AVFrame structure Format for each input and each output the list of supported formats For video that means pixel format For audio that means channel sample they are references to shared objects When the negotiation mechanism computes the intersection of the formats supported at each end of a all references to both lists are replaced with a reference to the intersection And when a single format is eventually chosen for a link amongst the remaining all references to the list are updated That means that if a filter requires that its input and output have the same format amongst a supported all it has to do is use a reference to the same list of formats query_formats can leave some formats unset and return AVERROR(EAGAIN) to cause the negotiation mechanism toagain later. That can be used by filters with complex requirements to use the format negotiated on one link to set the formats supported on another. Frame references ownership and permissions
#define URL_PROTOCOL_FLAG_NETWORK
#define AVERROR_EOF
End of file.
static av_always_inline int pthread_mutex_init(pthread_mutex_t *mutex, const pthread_mutexattr_t *attr)
void ff_openssl_deinit(void)
#define TLS_COMMON_OPTIONS(pstruct, options_field)
static const AVClass tls_class
static int url_bio_create(BIO *b)
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf type
#define AV_LOG_ERROR
Something went wrong and cannot losslessly be recovered.
static int tls_write(URLContext *h, const uint8_t *buf, int size)
const URLProtocol ff_tls_protocol
#define LIBAVUTIL_VERSION_INT
Describe the class of an AVClass context structure.
const char * av_default_item_name(void *ptr)
Return the context name.
static long url_bio_ctrl(BIO *b, int cmd, long num, void *ptr)
int ff_openssl_init(void)
static int url_bio_destroy(BIO *b)
Undefined Behavior In the C some operations are like signed integer dereferencing freed accessing outside allocated Undefined Behavior must not occur in a C it is not safe even if the output of undefined operations is unused The unsafety may seem nit picking but Optimizing compilers have in fact optimized code on the assumption that no undefined Behavior occurs Optimizing code based on wrong assumptions can and has in some cases lead to effects beyond the output of computations The signed integer overflow problem in speed critical code Code which is highly optimized and works with signed integers sometimes has the problem that often the output of the computation does not c
static int url_bio_bwrite(BIO *b, const char *buf, int len)
static int tls_open(URLContext *h, const char *uri, int flags, AVDictionary **options)
#define pthread_mutex_unlock(a)
static int url_bio_bread(BIO *b, char *buf, int len)
static const AVOption options[]
static int tls_get_file_handle(URLContext *h)
static av_always_inline int pthread_mutex_destroy(pthread_mutex_t *mutex)
#define i(width, name, range_min, range_max)
#define av_malloc_array(a, b)
static int print_tls_error(URLContext *h, int ret)
int ffurl_closep(URLContext **hh)
Close the resource accessed by the URLContext h, and free the memory used by it.
int ff_tls_open_underlying(TLSShared *c, URLContext *parent, const char *uri, AVDictionary **options)
const char * class_name
The name of the class; usually it is the same name as the context structure type to which the AVClass...
FFmpeg Automated Testing Environment ************************************Introduction Using FATE from your FFmpeg source directory Submitting the results to the FFmpeg result aggregation server Uploading new samples to the fate suite FATE makefile targets and variables Makefile targets Makefile variables Examples Introduction **************FATE is an extended regression suite on the client side and a means for results aggregation and presentation on the server side The first part of this document explains how you can use FATE from your FFmpeg source directory to test your ffmpeg binary The second part describes how you can run FATE to submit the results to FFmpeg’s FATE server In any way you can have a look at the publicly viewable FATE results by visiting this as it can be seen if some test on some platform broke with their recent contribution This usually happens on the platforms the developers could not test on The second part of this document describes how you can run FATE to submit your results to FFmpeg’s FATE server If you want to submit your results be sure to check that your combination of OS and compiler is not already listed on the above mentioned website In the third part you can find a comprehensive listing of FATE makefile targets and variables Using FATE from your FFmpeg source directory **********************************************If you want to run FATE on your machine you need to have the samples in place You can get the samples via the build target fate rsync Use this command from the top level source this will cause FATE to fail NOTE To use a custom wrapper to run the pass ‘ target exec’ to ‘configure’ or set the TARGET_EXEC Make variable Submitting the results to the FFmpeg result aggregation server ****************************************************************To submit your results to the server you should run fate through the shell script ‘tests fate sh’ from the FFmpeg sources This script needs to be invoked with a configuration file as its first argument tests fate sh path to fate_config A configuration file template with comments describing the individual configuration variables can be found at ‘doc fate_config sh template’ Create a configuration that suits your based on the configuration template The ‘slot’ configuration variable can be any string that is not yet but it is suggested that you name it adhering to the following pattern ‘ARCH OS COMPILER COMPILER VERSION’ The configuration file itself will be sourced in a shell therefore all shell features may be used This enables you to setup the environment as you need it for your build For your first test runs the ‘fate_recv’ variable should be empty or commented out This will run everything as normal except that it will omit the submission of the results to the server The following files should be present in $workdir as specified in the configuration file
int ffurl_read(URLContext *h, unsigned char *buf, int size)
Read up to size bytes from the resource accessed by h, and store the read bytes in buf.
int ffurl_write(URLContext *h, const unsigned char *buf, int size)
Write size bytes from buf to the resource accessed by h.
static int tls_read(URLContext *h, uint8_t *buf, int size)
static BIO_METHOD url_bio_method
#define AVIO_FLAG_NONBLOCK
Use non-blocking mode.
#define flags(name, subs,...)
#define AVERROR_EXIT
Immediate exit was requested; the called function should not be restarted.
static int tls_close(URLContext *h)
int ffurl_get_file_handle(URLContext *h)
Return the file descriptor associated with this URL.
static int url_bio_bputs(BIO *b, const char *str)
#define pthread_mutex_lock(a)