how to stop stdout when creating srtpenc/srtpdec

Sebastian Dröge sebastian at centricular.com
Wed Aug 17 08:47:36 UTC 2016


On Tue, 2016-08-16 at 15:25 -0700, Andres Gonzalez wrote:
> Thanks for your reply Sebastian.
> 
> I agree, that stdout output appears to be related to the openssl lib. I will
> check out my openssl code. 
> 
> However, I do not think it is "initialization" output, but instead perhaps
> debug output from srtpenc. I am currently using openssl for my DTLS stack,
> and currently my code initializes the openssl lib, loads certs, does the
> DTLS handshake, exchanges certs, retrieve remote keys, validates/verifies
> them, and successfully sets up a DTLS channel with Chrome browser code.  So
> my current code is already using openssl successfully and I have not seen
> this output from my usage of the openssl API.  Obviously, my code
> initializes the openssl lib, and running all of my current openssl code does
> not trigger that stdout dump.  
> 
> If it is indeed from the openssl lib initialization, then it appears that
> there is some setting in the GStreamer srtpenc code that is enabling that
> output (perhaps a debug option??), because I only see that output when I
> create the srtpenc element.

Well, check the code :) The SRTP elements are not even using openssl
directly, they just use libsrtp.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 931 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160817/172bbeb2/attachment.sig>


More information about the gstreamer-devel mailing list