- 26 Apr, 2018 1 commit
-
-
Carl Eugen Hoyos authored
The av_rc4_crypt() documentation allows src == dst. Silences the following warning: libavformat/rtmpcrypt.c:304:36: warning: passing argument 2 of 'av_rc4_crypt' discards 'const' qualifier from pointer target type Reported-by: Reino Wijnsma
-
- 24 Mar, 2016 1 commit
-
-
Martin Storsjö authored
Since all URLContexts have the same AVOptions, such AVOptions will be applied on the outermost context only and removed from the dict, while they probably make sense on all contexts. This makes sure that rw_timeout gets propagated to the innermost URLContext (to make sure it gets passed to the tcp protocol, when opening a http connection for instance). Alternatively, such matching options would be kept in the dict and only removed after the ffurl_connect call. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 04 Mar, 2016 1 commit
-
-
Derek Buitenhuis authored
Signed-off-by:
Derek Buitenhuis <derek.buitenhuis@gmail.com>
-
- 22 Feb, 2016 2 commits
-
-
Anton Khirnov authored
This way, the decisions about which protocols are available for use in any given situations can be delegated to the caller.
-
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.
-
- 02 Feb, 2016 1 commit
-
-
Michael Niedermayer authored
Reviewed-by:
Andreas Cadhalpun <andreas.cadhalpun@googlemail.com> Signed-off-by:
Michael Niedermayer <michael@niedermayer.cc>
-
- 13 Nov, 2015 2 commits
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
The XTEA algorithm operates on 32 bit numbers, not on byte sequences. The XTEA implementation in libavutil is written assuming big endian numbers, while the rtmpe signature encryption assumes little endian. This fixes rtmpe communication with rtmpe servers that use signature type 8 (XTEA), e.g. crunchyroll. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 29 May, 2015 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 04 Sep, 2012 1 commit
-
-
Martin Storsjö authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 24 Jul, 2012 1 commit
-
-
Martin Storsjö authored
Our implementation of RTMPE is heavily based on librtmp. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 23 Jul, 2012 2 commits
-
-
Samuel Pitoiset authored
Signed-off-by:
Martin Storsjö <martin@martin.st>
-
Samuel Pitoiset authored
This adds two protocols, but one of them is an internal implementation detail just used as an abstraction layer/generalization in the code. The RTMPE protocol implementation uses ffrtmpcrypt:// as an alternative to the tcp:// protocol. This allows moving most of the lower level logic out from the higher level generic rtmp code. Signed-off-by:
Martin Storsjö <martin@martin.st>
-