|
You are here |
lucasb.eyer.be | ||
| | | | |
zaries.wordpress.com
|
|
| | | | | There are thousands of articles and entries in stackexchange but none of them worked for me out of the box. So after hours of battling with this issue here is my short recipe. Create the Root Key: openssl genrsa -out rootCA.key 2048 Self-sign this root certificate: openssl req -x509 -new -nodes -key rootCA.key -sha256 -days... | |
| | | | |
hobo.house
|
|
| | | | | Plex is a fork of the Open Source Kodi (previously XBMC) project from 2008, the Plex Media Server has evolved into what amounts to a free, personal Netflix + Spotify that lets you stream home content to devices or browsers with an optional subscription model for added features. Here's how to use your own self-signed... | |
| | | | |
www.dgendill.com
|
|
| | | | | [AI summary] A developer shares a detailed tutorial on how to generate self-signed SSL certificates with specific Subject Alternative Names to enable secure service worker testing on mobile devices over a local network. | |
| | | | |
sgued.fr
|
|
| | | X509 certificate can be encoded either as DER or PEM. DER encoding is an efficient binary format, while PEM encoding is a wrapper around the Base 64 DER encoding of the certificate. Usually, when dealing with a specific certificate, you know beforehand whether it's encoded as DER or PEM. For example, in the opennssl CLI, you can give it the -inform parameter, which accepts either DER or PEM. However, what if don't know the encoding of the certificate, can you figure it out on the fly? | ||