Generating a self-signed certificate

Using encryption is highly recommended (I'd say even mandatory) for WebRTC applications. The technology has good support for security and encryption, so there is no reason to ignore them. In this recipe, we will cover the process of creating self-signed certificates. Such a certificate can be used with a TURN server or with a web server when operating with HTTPS channels.

Typically, a public key infrastructure (PKI) is a digital signature from a certificate authority (CA), which attests that a particular PKI is valid and contains correct information. Users or their software then check that the private key used to sign a certificate matches the public key in the CA's certificate. Since CA certificates are often signed by other, high-ranking CAs, there must necessarily be a highest-ranking CA, which provides the ultimate attestation authority in that particular PKI scheme.

The highest-ranking CA's certificates are termed as root certificates...