rtmpdh: Initialize gcrypt before using it
authorRicardo Constantino <wiiaboo@gmail.com>
Tue, 29 Dec 2015 21:40:14 +0000 (21:40 +0000)
committerMichael Niedermayer <michael@niedermayer.cc>
Mon, 11 Jan 2016 23:56:02 +0000 (00:56 +0100)
commitd50b5d547f4070678c88aa095b5292c872e2c1dc
tree0138851ccac566eaea6166dd1775c9b939213062
parentd637a58750ef456e4254736add04b5c7d0b6dc40
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>
libavformat/rtmpdh.c