sslyze 2.0 is pickier about types, and passing the port as a string here was causing sslyze to fail.
For HTTPS scanning the port is not specified (the default of 443 is used), so this bug was only impacting folks like me who are using sslyze against other ports.
sslyze 2.0 is pickier about types, and passing the port as a string here was causing sslyze to fail.
For HTTPS scanning the port is not specified (the default of 443 is used), so this bug was only impacting folks like me who are using sslyze against other ports.