- 09 Apr, 2013 2 commits
-
-
Martin Storsjö authored
This was missed from 350ad50b - this fixes building the fate-srtp test. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Andrew Van Til authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 20 Jan, 2013 7 commits
-
-
Martin Storsjö authored
This simplifies the code slightly. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
The theoretical minimum for a (not totally well formed) RTCP packet is 8 bytes, so we shouldn't require 12 bytes as minimum input. Also return AVERROR_INVALIDDATA instead of 0 if something that is not a proper packet is given. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This clarifies where the limit number comes from, and only requires exactly as much padding space as will be needed. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
The main difference to the existing suites from RFC 4568 is that the version with a 32 bit HMAC still uses 80 bit HMAC for RTCP packets. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This is untested in practice, but follows the spec. Signed-off-by: Martin Storsjö <martin@martin.st>
-
- 15 Jan, 2013 3 commits
-
-
Martin Storsjö authored
This squelches false positive warnings (with gcc) about them being used uninitalized. Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
Signed-off-by: Martin Storsjö <martin@martin.st>
-
Martin Storsjö authored
This supports the AES_CM_128_HMAC_SHA1_80 and AES_CM_128_HMAC_SHA1_32 cipher suites (from RFC 4568) at the moment. The main missing features are replay protection (which can be added later without changing the internal API), and the F8 and null ciphers. Signed-off-by: Martin Storsjö <martin@martin.st>
-