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
Hi, thanks for all the work you're doing to improve sslscan. While you're at it, I have a weird problem with sslscan both with the original version and with your fork. When I try to check mail.swissmail.org on port 25, it reports that STARTTLS is not supported. But it is, the problem (I did some strace'ing) seems to be that somehow sslscan doesn't seem to read the entire response to the EHLO command with this server, but only the first line. After sending the STARTTLS command, instead of getting the expected "220 ready to start TLS" or similar, it gets "250-STARTTLS", which is still part of the EHLO response. When I add a second "recv" command before sending STARTTLS, it works for this server, but of course it hangs for all other servers because there is nothing to receive. If you have any ideas how to fix this properly, I'd be very thankful...
The text was updated successfully, but these errors were encountered:
Hi, thanks for all the work you're doing to improve sslscan. While you're at it, I have a weird problem with sslscan both with the original version and with your fork. When I try to check mail.swissmail.org on port 25, it reports that STARTTLS is not supported. But it is, the problem (I did some strace'ing) seems to be that somehow sslscan doesn't seem to read the entire response to the EHLO command with this server, but only the first line. After sending the STARTTLS command, instead of getting the expected "220 ready to start TLS" or similar, it gets "250-STARTTLS", which is still part of the EHLO response. When I add a second "recv" command before sending STARTTLS, it works for this server, but of course it hangs for all other servers because there is nothing to receive. If you have any ideas how to fix this properly, I'd be very thankful...
The text was updated successfully, but these errors were encountered: