FTA: "Using a combination of proxies, modified DNS records, sslsplit and a new CA certificate installed in Windows, we were able to inspect all traffic, including HTTP and XMPP, in our test environment."<p>I have setup wireshark for troubleshooting. That's about it. What's the role of proxies, modified DNS records etc. in this setup? How can I duplicate this?<p>Thanks.
> This meant that by sending a ResponseKey message with an AES-encrypted <encoded> element of more than 1024 bytes, it was possible to overflow a heap buffer.<p>This is what I was looking for. Fundamental bug was an overflow of statically-allocated buffer leading to heap corruption.<p>We gotta get off memory-unsafe languages.
Although they don’t make it easy to find the link, you can use Zoom in a browser which is the best way of limiting the damage it can cause if you <i>have</i> to use it in the first place.