Collaborate Disseminate
Is there a simple C library or function to programmatically generate a self-signed certificate in C on Ubuntu? Of course, one can execute a simple system("….") call to execute a CLI. I am looking for a native, small, stand-alo… Continue reading Independent C library or function (on Linux) to programmatically generate a self-signed certificate [closed]
While I understand the differences between DTLS-SRTP and pure DTLS, I cannot find much information on why exactly is DTLS-SRTP really “optimized” over generic DTLS 1.2.
RFC 5764’s Introduction makes an obvious statement but without spec… Continue reading Why is DTLS-SRTP more efficient for RTP/RTCP than just DTLS 1.2?
A certificate, in itself, (RFC 5280) does not seem to have any indicator of what algorithm was used (for example the argument to openssl req -newkey) to create the public and private keys (“Certificate Key Type”). That surprised me. A cert… Continue reading Explanation required on Relationship between "Certificate Type" and "Key Exchange Algorithms" in TLS 1.2
There are references in TLS 1.2 RFC 5246 about use of certificates (server and client). I am unclear about the “key usage” extension of a certificate as it relates to TLS 1.2 and that too for data encryption only. I am not not concerned a… Continue reading Can someone explain the "Section 4.2.1.3. Key Usage" extension in RFC 5280 as it relates to TLS 1.2 RFC 5246
The a=crypto attribute in RFC 4568 has a separate section 9.2. for SRTP “Crypto” Attribute Grammar. What it basically includes is a list of attribute values required for encrypting media (crypto suite, method, session params… Continue reading Is the SDP a=crypto attribute relevant when DTLS-SRTP is used?
I have been reading RFC 5246 on TLS 1.2 and have a few questions on algorithms chosen. Before I start, let me clarify that I am reading on 1.2 and not 1.3 because my ultimate interest is in DTLS 1.2.
I am confused with what a… Continue reading Questions on TLS 1.2 RFC – Clarification or references needed