Simon Robinson

Coincidentally I just ran into something similar to this after using a patchy internet connection for a few weeks. The proxy got into a state where it worked fine when...

Just wondering whether this has happened again since the last update?

Good to know - let's hope it doesn't happen again, but if it does, feel free to reopen this issue so we have the context.

Thanks for following up – yes, you might as well share the corefile just in case (though there's probably only a slim chance it'll be useful). I don't really have...

I think you're on to something here – initially this was a feature submitted in #140 by an external contributor, but it happened in parallel to my own development, so...

Thanks for the detailed follow-ups. I agree with your conclusion that this is unrelated to the proxy, and is likely to be a problem whose root cause is somewhere else...

This comment is just a reminder to myself that this issue can be closed once glibc 2.40 is released ([scheduled for August 2024](https://sourceware.org/glibc/)). Thanks @jlevon for the [fascinating blog post](https://movementarian.org/blog/posts/its-always-dns/)...

I've just seen that glibc 2.40 [has been released](https://sourceware.org/pipermail/libc-alpha/2024-July/158467.html), so will close this issue now that the underlying bug has been resolved. Thanks again @jlevon for the dedication to fixing...

The proxy avoids anything like this as much as possible, and with the exception of setting the minimum TLS version to 1.2, it relies on Python's inbuilt SSL module for...

> One more question. I have an install of this and all seems to be fine - all 3 keys from Azure are in config etc, however in the log...