The page at http://wiki.debuntu.org/wiki/OpenSSL#Retrieving_certificate_informations lists the command lines for that (and printing out the relevant information). From that page and some of the man pages, it seems like what you want is (for bash): openssl s_client -connect <host>:<port> < /dev/null 2>/dev/null | openssl x509 -fingerprint -noout -in /dev/stdin If you want the whole certificate, leave … Read more
I was trying to create Let’s Encrypt certificate using certbot for my sub-domain and had the following issue. Command: ubuntu@localhost:~$ certbot –nginx -d my_subdomain.website.com -d my_subdomain2.website.com Issue: The requested Nginx plugin does not appear to be installed Solution: Ubuntu 20+ ubuntu@localhost:~$ sudo apt-get install python3-certbot-nginx Earlier Versions ubuntu@localhost:~$ sudo apt-get install python-certbot-nginx
It works from here with same OpenSSL version, but a newer version of wget (1.15). Looking at the Changelog there is the following significant change regarding your problem: 1.14: Add support for TLS Server Name Indication. Note that this site does not require SNI. But www.coursera.org requires it. And if you would call wget with … Read more
There is no standard about that, but port 8443 is sometimes known as the https-alt, and it seems the only one being popularly used as alternative HTTPS port. It may have become popular because of mod_nss (an HTTPD module alternative to mod_ssl) using it on its default configuration.
I ran into this problem with HTTPS, but not HTTP. For some reason IE would continue through the different font options, ignoring 200 OK responses. In my case, the problem was the HTTP header Cache-Control: no-cache for the font. While this will work fine with HTTP, over HTTPS it causes Internet Explorer to ignore the … Read more
On Heroku, it’s slightly tricky to determine the fact that the request came in over http. https is handled at a heroku routing layer and it passes along the request to the node app on http). This post got me unstuck http://jaketrent.com/post/https-redirect-node-heroku/
Yes your URL would be safe from sniffing; however, one hole that is easily overlooken is if your page references any third party resources such as Google Analytics, Add Content anything, your entire URL will be sent to the third party in the referer. If its really sensitive it doesn’t belong in the query string. … Read more
Your spring configuration should be agnostic to the used protocol. If you use something like “requires-channel”, you’ll run into problems sooner or later, especially if you want to deploy the same application to a development environment without https. Instead, consider to configure your tomcat properly. You can do this with RemoteIpValve. Depending on which headers … Read more
When you know that you ARE export compliant you can put this in your Info.plist: <key>ITSAppUsesNonExemptEncryption</key> <false/> This will prevent App Store Connect from asking you questions about export compliance.
Use window.location.protocol to check if it is https: function isSecure() { return window.location.protocol == ‘https:’; } Alternatively you can omit specifying “window” if you don’t have a locally scoped location. function isSecure() { return location.protocol == ‘https:’; }