We talk about ECC all the time, but let’s be honest. It can all seem a little bit abstract, which is probably not helping its adoption-rate. The majority of the SSL/TLS certificates being issued today use RSA public key encryption. We know because we sell a lot of them. And as far as I can tell, a large part of that can be attributed to the fact that people still think that Elliptic Curve-based cryptosystems still aren’t widely supported by end users’ browsers and operating systems. Well, that’s not true. So today we’re going to talk a bit about the
There is an app available on Adroid called VPN Client Pro which fully supports SSTP VPN and allows you to connect to a Windows Server 2008 – 2019 environment running RRAS. Use the button below to download the apk install file. You may need to click on the reCAPTCHA prior to clicking Download. [sdm_download id=”4591″ fancy=”0″] Full disclosure: The app is cracked but has been scanned and found to be virus-free. Please make sure to support my site by clicking on an advertisement if you’ve found this site helpful in any way. If you have only a single
Often when you’re working in heterogeneous environments you will be needing to convert the standard Linux format x509/PEM SSL certificate files to the Windows native PFX/p12 format, or vise-versa. The following OpenSSL commands are able to do just about every type of certificate conversion imaginable. DID YOU KNOW? “pem”, “cer”, and “crt” are all the same certificate formats called x509. The only difference is cosmetic via different extensions. A full certificate chain = public certificate + intermediate certificate + root certificate contained in a single file. OpenSSL Convert X509/PEM Convert PEM & Private Key to PFX/P12: openssl pkcs12 -export -out certificate.pfx
Chances are this is not the first website you’ve come to after breaking SSL on your Nginx box, but I promise it will be the last. The problem is actually a very simple one, and the Nginx error log tells you verbatim what is wrong with the config, although nginx -t will yield success. Nginx reads and runs the sites in alphabetical order, therefore this issue can be fixed by finding and fixing the site config which is listening on port 443 and using ssl without any ssl certificate declarations which is causing your site further down the alphabetical line to fail HTTPS. In my case it was a Nginx site config called stub_status.conf causing SSL to fail in blog.travisrunyard.us.conf even though I did have SSL correctly setup.