Tag Info

New answers tagged

1

It appears that the private key for your SSL certificate is password-protected. To test whether this is really the case, examine the beginning of your keyfile using the command head -3 your.key. This private key is encrypted: -----BEGIN RSA PRIVATE KEY----- Proc-Type: 4,ENCRYPTED DEK-Info: AES-128-CBC,C251E8A1254B933D763703EE1C364AB7 This file is not ...


0

sudo ufw allow 443/tcp And have a read through the docs on Ubuntu UFW interface on iptables. This should open it for your web application. Also make sure that your application is serving off the external IP as well as the internal. The app.js file there is usually a setting to specify a interface for it to run on. 0.0.0.0 should run it on both internal ...


1

They are NOT safe and that is why they are marked as Untrusted. These were bogus certificates. See this article on EFF: On March 15th, an HTTPS/TLS Certificate Authority (CA) was tricked into issuing fraudulent certificates that posed a dire risk to Internet security. Based on currently available information, the incident got close to — but was not ...


0

This is a mistake (note that this test is marked as "Experimental", so is probably still not reliable). CVE-2014-0224 was fixed in Ubuntu 12.04 in openssl 1.0.1-4ubuntu5.14.


2

Check System date time and timezone in Ubuntu. Provide Proper time and timezone and then try to browse https site. If you have wrong time in your system you will get Untrusted connection error while connecting to site that uses ssl.


1

Before you consider anything else, ask yourself "What's wrong with SSH?" a hundred times. It's secure, supports better authentication (omgwhy are you still using passwords?!) and doesn't result in a server-side language running in a capacity that can su up to a privileged account. That said, there are a number of options for providing web-access to a ...


0

It turns out that I had the intermediate certificates out of order. Web browsers and ssllabs were fine with that but, it appears that apt cares about the ordering of the intermediate certificates.


0

A simple fix that worked for me was to override SSL's default protocol: import ssl ssl.PROTOCOL_SSLv23 = ssl.PROTOCOL_TLSv1



Top 50 recent answers are included