Dustin Lundquist

It sounds like you may not have IPv6 connectivity to the site which the hostname resolves to. I would check your IPv6 connectivity and enable debug logging and see if...

@wang20150419 since your comfortable working with the source code. I would suggest adding some more debugging to `resolve_server_address()` and `resolv_cb()` to see what data in submitted and returned by the...

Good question, thanks for bringing this to my attention. Short of mounting a brute force attack or taking the https://xkcd.com/416/ approach, once the SNI extension is encrypted there isn't much...

Did anything get logged to syslog? Does your config reference anything that it would need root privileges for? You might try running sniproxy under strake to figure out what is...

It looks like you don’t have access to create a socket in /var/run. It looks like sniproxy tried to create the listening socket in /var/run first in the main process,...

You don’t have permission to create a socket in /var/run.

Are you able to reproduce this outside of EC2? Does sniproxy work outside of the test suite? From the test log it looks like something else is running on TCP...

It sounds like libudns wasn't detected when ./configure ran. I suggest reveiwing the output of the ./configure script. If you continue to have problems I would ensure libudns is regisistered...

While this sounds possible, I think a VPN would be a better solution. I would imagine a firewall could just as easily filter based on the server certificate, or the...

@Nefurtity I didn't analyze your TLS handshakes in detail, but my first through is to check that you updated the TLS record length, handshake length and extension length when you...