News for hackers. Stuff that matters.
Re:NoPassword by peterwwillis on Tuesday September 25, 2012 @11:51AM (#4570986)
On 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.
Re:NoPassword by pharrington on Tuesday September 25, 2012 @12:51PM (#4571327)
The self-signed cert is from alexsmolen.com, not nopassword.alexsmolen.com.
Re:NoPassword by peterwwillis on Tuesday September 25, 2012 @01:27PM (#4571522)
Ah, so it's using the servername TLS extension. I forgot that some people use that now :)
Re:NoPassword by tedunangst on Tuesday September 25, 2012 @12:36PM (#4571241)
server name indication?