Sándor Oroszi
Sándor Oroszi
Two checks appear to be failing due to cryptography no longer allowing OpenSSL 1.0.2.
This appears to be a bug in `X509Store.set_time()`, caused by `vfy_time.strftime("%s")` (`vfy_time` is a datetime object) disregarding the timezone, therefore passing an incorrect timestamp to `X509_VERIFY_PARAM_set_time()`. The `"%s"` problem is...
... and apparently I'm not the first to figure this out. I just bumped into #798, which is basically the same issue, and #907 fixing them.
I was playing with that a little :smile:, strftime("%s") is evil... More about that at #798...
This issue is also fixed by #907, and documented in #952.
I had a Code 22 (Device disabled) issue on Windows 10 1803. The underlying cause appeared to be that the scanner got installed with the default localhost:6566 address, with no...
Somewhat updating my question in #469: Wouldn't fixing the tags in the build process with auditwheel to something like `cp37-abi3-manylinux_2_31_armv7l` for bullseye, and `cp37-abi3-manylinux_2_36_armv7l` for bookworm differentiate the built wheels...
I just performed a quick test. The 43.0.3 armv7l build (having `sha256=aa694873d3f46d2af4480573597b341f891acdeefe21f37b9112df7004e4cd3e`) appears to be linked against openssl3, and indeed it works on a bookworm based OS. This coincides with...