handling https when using starttls=auto

[secworks]

There is a bug runnng --starttls=auto with https.

Example: python sslyze.py --certinfo=basic --regular --starttls=auto www.kirei.se:443

Result: Unhandled exception when processing --compression: exceptions.KeyError - 443

Unhandled exception when processing --reneg: exceptions.KeyError - 443

Unhandled exception when processing --certinfo: exceptions.KeyError - 443

Unhandled exception when processing --tlsv1_2: exceptions.IndexError - tuple index out of range

• Session Resumption : With Session IDs: Error (0 successful, 0 failed, 5 errors, 5 total attempts). Error #1: exceptions.KeyError - 443 Error #2: exceptions.KeyError - 443 Error #3: exceptions.KeyError - 443 Error #4: exceptions.KeyError - 443 Error #5: exceptions.KeyError - 443 With TLS Session Tickets: Error: exceptions.KeyError - 443

Unhandled exception when processing --sslv2: exceptions.IndexError - tuple index out of range

Unhandled exception when processing --tlsv1: exceptions.IndexError - tuple index out of range

Unhandled exception when processing --tlsv1_1: exceptions.IndexError - tuple index out of range

Unhandled exception when processing --sslv3: exceptions.IndexError - tuple index out of range

A lot of things that breaks for some reason. There is a new branc - auto_www_bug used to solve this.

[secworks]

Fixed in https://github.com/kirei/sslyze/commit/29084d9e1cea3930a9068289d4502d0d989764b5

Merging.