Adrian Vollmer

Yes, this can't work. Instead of the public IP, you should use the gateway (you can find it with `ip r|grep default`). Note that you use the same IP for...

Well, it should work all the same. The difference is that with public certs the user won't get a warning during regular usage. Then when you launch this attack the...

Looks the victim may have closed the connection... hard to tell without further investigation

For completeness: what's the output of `openssl ciphers`? Also, what Linux distribution are you using? I suspect your openssl does not support RC4 anymore. That may be a bit of...

If no data is returned, this means the peer has reset the connection. Maybe a pcap file of the connection could tell us more.

Can you please run it with `SETH_DEBUG=1 ./seth.sh ...` and post the output?

Hmmm everything looks fine. I increased verbosity with the latest commit. You could pull it and try again to see what it says. Also you may want to redact that...

No, because the SSL connection is successfully established and data is exchanged after the SSL handshake. For whatever reason the server closes the connection right before authentication. Unfortunately I'm clueless...

Actually, you may have been right. See http://fixmyitsystem.com/2011/08/rdp-rds-unexpected-server.html I'll have to come up with something

Hi, thanks for the very detailed bug report. I wish it was this detailed every time ;) So first of all, I never tested Seth with a non-Windows host, so...