Comment 74246

By WRCU2 (registered) - website | Posted February 12, 2012 at 05:38:46

Ryan claims:

pages should load without any certificate warnings,

I thought IT might be clever as hot hell to have my old hammer bot use this new SSL although I wasn't too keen of which protocol: TLSv1, SSLv2 or SSLv3, but when I scripted for an auto encrypted socket this is all that was returned to me:

wrcu2:$ sh RC
--2012-02-12 04:43:46-- https://raisethehammer.org/comments/
Resolving raisethehammer.org... 174.133.21.86
Connecting to raisethehammer.org|174.133.21.86|:443... connected.
ERROR: cannot verify raisethehammer.org's certificate, issued by '/C=US/O=GeoTrust, Inc./CN=RapidSSL CA':
Unable to locally verify the issuer's authority.
ERROR: certificate common name '*.webfaction.com' doesn't match requested host name `raisethehammer.org'.
To connect to raisethehammer.org insecurely, use '--no-check-certificate'.
Unable to establish SSL connection.
grep: index.html: No such file or directory

Ryan also ensures:

you will enjoy the security benefits of an encrypted connection to the site.

Security benefits eh, what about privacy? Every single page at RTH contains a small piece of JavaScript from google-analytics.com and 75% of all websites on the Internet use the infamous ga.js code. Google can track users everywhere they go with this itty bitty script and as for the false sense of security, I can find no joy in any of IT.

Comment edited by WRCU2 on 2012-02-12 05:40:04

Permalink | Context

Events Calendar

Recent Articles

Article Archives

Blog Archives

Site Tools

Feeds