no dummy wildcard SSL certs about mitmproxy

[cortesi]

This is a good idea, and definitely something that could be targeted for 0.8. I'd want to make it optional, though, because I can think of testing situations where the Host header heuristic is better. We already cache certificates, so we can simply initiate a connection upstream when we first see a connection to a host, grab the upstream cert, do the local generation, and from that point on the cached cert will be used instead.

I'll leave this ticket open as a feature request

[cortesi]

I'm working on something like this in the upstream-cert branch, which will find its way into 0.8. It pulls not only the CN but also the Subject Alternative Names, and uses them in the generated certs. Please feel free to check it out and help test.

[sektoid0]

thanks a lot! did some tests, works fine.