scanner doesn't actually support x448

[catharsis71]

1. Configure Apache with SSLOpenSSLConfCmd Curves X448 and no others

2. Verify with curl -I --curve x448 etc that server is accessible using X448 and nothing else

3. Run SSL scan

4. The scan will report "Failed to communicate with the secure server" because the scanner apparently doesn't actually support X448

even though browser support for X448 is lacking, OpenSSL 1.1.1 definitely supports it

if I switch Apache over to SSLOpenSSLConfCmd Curves X448:ffdhe8192 as a test so I can get a better look at the scan results, I can see that if falsely claims connection failure for OpenSSL

[naumanshah03]

Hi @catharsis71

Could you please share the domain name to investigate the issue?

Regards,
Nauman Shah