3 ms·
I find it amusing that a page discussing passwords/security would throw a couple of SSL certificate warnings when loading it.
by endianswap 14y ago
I find it amusing that a page discussing passwords/security would throw a couple of SSL certificate warnings when loading it.
- cypherpunks01 14y agoIt's all green for me on chrome. What's causing the issue for you?
- grimboy 14y agoNot sure but perhaps it could be this: http://jimmyzimmerman.com/blog/2011/03/positivessl-untrusted-connection-in-firefox.html http://jimmyzimmerman.com/blog/2011/03/positivessl-untrusted... ?
- peterwwillis 14y agoOn top of that, the SSL server supports compression, session tickets and insecure ciphers, so that's three possible attacks to try. What's REALLY weird: my browser is showing a different cert than OpenSSL is. My browser shows it's signed by PositiveSSL, but when I connect with 'openssl s_client' I get this: depth=0 C = --, ST = SomeState, L = SomeCity, O = SomeOrganization, OU = SomeOrganizationalUnit, CN = ip-10-119-98-53, emailAddress = root@ip-10-119-98-53 verify error:num=18:self signed certificate verify return:1 depth=0 C = --, ST = SomeState, L = SomeCity, O = SomeOrganization, OU = SomeOrganizationalUnit, CN = ip-10-119-98-53, emailAddress = root@ip-10-119-98-53 verify error:num=10:certificate has expired notAfter=Feb 24 01:08:21 2012 GMT verify return:1 depth=0 C = --, ST = SomeState, L = SomeCity, O = SomeOrganization, OU = SomeOrganizationalUnit, CN = ip-10-119-98-53, emailAddress = root@ip-10-119-98-53 notAfter=Feb 24 01:08:21 2012 GMT Not only is it self-signed, it's expired. I actually don't know what the fuck is going on here.
- tedunangst 14y agoserver name indication?
- pharrington 14y agoThe self-signed cert is from alexsmolen.com, not nopassword.alexsmolen.com.
- peterwwillis 14y agoAh, so it's using the servername TLS extension. I forgot that some people use that now :)