aboutsummaryrefslogtreecommitdiffstats
path: root/libavcodec/x86/vp9dsp_init_12bpp.c
diff options
context:
space:
mode:
authorRicardo Constantino <wiiaboo@gmail.com>2015-12-29 21:40:14 +0000
committerMichael Niedermayer <michael@niedermayer.cc>2016-01-12 00:56:02 +0100
commitd50b5d547f4070678c88aa095b5292c872e2c1dc (patch)
tree0138851ccac566eaea6166dd1775c9b939213062 /libavcodec/x86/vp9dsp_init_12bpp.c
parentd637a58750ef456e4254736add04b5c7d0b6dc40 (diff)
downloadffmpeg-d50b5d547f4070678c88aa095b5292c872e2c1dc.tar.gz
rtmpdh: Initialize gcrypt before using it
Either disabling or init'ing secure memory is required after the use of gcry_check_version. From a look at the functions rtmpdh uses, I noticed none require the use of secure memory, so we disable it [1][2]. This resolves some errors returned by rtmpdh code with uninitialized gcrypt, especifically: Fatal: failed to create the RNG lock: Invalid argument FATAL: failed to acquire the FSM lock in libgrypt: Invalid argument Version "1.5.4" was arbitrarily chosen. An older version probably works as well, but I couldn't compile older versions to test on my machine. [1] https://gnupg.org/documentation/manuals/gcrypt/Initializing-the-library.html [2] https://www.gnupg.org/documentation/manuals/gcrypt/Controlling-the-library.html Signed-off-by: Ricardo Constantino <wiiaboo@gmail.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
Diffstat (limited to 'libavcodec/x86/vp9dsp_init_12bpp.c')
0 files changed, 0 insertions, 0 deletions