You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"HTTPS Custom Truststore Trusted" and "HTTPS Cert Chain Length" check results are null when specifying a port number with a URL. These should not be null, and should instead be representative of the actual values reflected.
To reproduce
Steps to reproduce the behavior:
Scan a normal website without a port number with a custom CA file: pshtt --timeout 2 --ca-file=custom_ca_file.pem google.com
Observe that these fields are not null
Scan the same website, but with the port number: pshtt --timeout 2 --ca-file=custom_ca_file.pem google.com:443
Observe that these fields are null
Scan any other website on any port specified: pshtt --timeout 2 --ca-file=custom_ca_file.pem example.com:9443
Observe that these fields are null
Expected behavior
These should not be null, and should instead be representative of the actual values reflected. SSLyze, for example, gets these values correct even when the port is provided, but PSHTT does not.
🐛 Summary
"HTTPS Custom Truststore Trusted" and "HTTPS Cert Chain Length" check results are
null
when specifying a port number with a URL. These should not benull
, and should instead be representative of the actual values reflected.To reproduce
Steps to reproduce the behavior:
pshtt --timeout 2 --ca-file=custom_ca_file.pem google.com
pshtt --timeout 2 --ca-file=custom_ca_file.pem google.com:443
pshtt --timeout 2 --ca-file=custom_ca_file.pem example.com:9443
Expected behavior
These should not be
null
, and should instead be representative of the actual values reflected. SSLyze, for example, gets these values correct even when the port is provided, but PSHTT does not.Any helpful log output or screenshots
Paste the results here:
The text was updated successfully, but these errors were encountered: