@bagder

Thanks so much for the clear & exemplary communications about this!

@bagder I have been waiting for this, thank you, Daniel!

@bagder
You are only human. But you're a pretty good human.

Thanks for the clear and detailed write up.

@bagder it was DNS :)

@bagder great explainer. You mention the hackerone report at the end - maybe worth linking it? I had to google it.

@bagder refactoring is always risky. Kinda wonder what an exploit scenario would look like though; it has to be a malicious server, the user has to be intentionally trying to reach it via SOCKS, and they must have some kind of ongoing service relationship for the server to have fingerprinted the client well enough to push an effective payload.

@bagder nice writeup!

@bagder Tell the truth, you actually found it in the Bard

@bagder I wonder if the upcoming bounds checked c rfc features from Apple in clang would be helpful at the very least as a defensive measure. but they also seem to be moving fairly slowly :(