how to stop stdout when creating srtpenc/srtpdec

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

how to stop stdout when creating srtpenc/srtpdec

Andres Gonzalez
Hi,

When I create srtpenc and srtpdec elements using gst_element_factory_make() WITHOUT adding them to any bin, I get the following stdout:

testing rand_source...passed
cipher: AES-256 GCM using openssl
  instance count: 0
  self-test: passed
cipher: AES-128 GCM using openssl
  instance count: 0
  self-test: passed
cipher: AES-128 counter mode using openssl
  instance count: 0
  self-test: passed
cipher: null cipher
  instance count: 0
  self-test: passed
auth func: hmac sha-1 authentication function
  instance count: 0
  self-test: passed
auth func: null authentication function
  instance count: 0
  self-test: passed
debug modules loaded:
  srtp (off)
  hmac sha-1 openssl (off)
  aes gcm (off)
  aes icm ossl (off)
  alloc (off)
  stat test (off)
  cipher (off)
  auth func (off)
  crypto kernel (off)

Question: what is causing this and how do I stop it?
Question: this appears that it might be useful in debugging, and if so, how do I control it and use it in a useful way?

Thanks,
-Andres
Reply | Threaded
Open this post in threaded view
|

Re: how to stop stdout when creating srtpenc/srtpdec

Sebastian Dröge-3
On Sat, 2016-08-13 at 16:35 -0700, Andres Gonzalez wrote:

> Hi,
>
> When I create srtpenc and srtpdec elements using
> gst_element_factory_make()
> WITHOUT adding them to any bin, I get the following stdout:
>
> testing rand_source...passed
> [...]
>
> Question: what is causing this and how do I stop it?
> Question: this appears that it might be useful in debugging, and if
> so, how do I control it and use it in a useful way?
That looks like something openssl prints during initialization, but it
must be something configurable (it doesn't do that here).

Check your openssl build :)

--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

signature.asc (949 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: how to stop stdout when creating srtpenc/srtpdec

Andres Gonzalez
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.

-Andres
Reply | Threaded
Open this post in threaded view
|

Re: how to stop stdout when creating srtpenc/srtpdec

Sebastian Dröge-3
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
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

signature.asc (949 bytes) Download Attachment