This is not good news….
$ ssh-vulnkey
COMPROMISED: 2048 b0:39:fe:46:51:0f:6b:87:24:db:af:c0:fa:d7:63:d3
and this is only my laptop…. I’m (we’re?) screwed…
I recently developed a website that has a real SSL area protected by a real valid SSL certificate.
However, I was getting complaints that, under SSL, browsers croaked about some parts being sent over an insecure connection.
I dug on the situation and found that because I was using Google Analytics, the <script> URL is HTTP under the SSL area. To get it working under SSL areas just change the URL:
Under SSL:
<script src="https://ssl.google-analytics.com/urchin.js" ...
Out of SSL:
<script src="http://www.google-analytics.com/urchin.js" ...
solved :-)