Closed buchdag closed 7 years ago
Yeah, the stack trace indicates that acme is making the offending call. My inclination is just to wait for acme to release that fix; this doesn't look like it's our bug.
The patch is included in the 0.19.0 milestone, which is due in about two weeks.
Should we just wait or install pyOpenSSL<17.3.0
/ pyOpenSSL==17.2.0
in the interval ?
I just pushed a patch that adds a version bound, seems to have fixed the CI. I'm going to tag a release in the next couple days, was waiting for PRs to land and now that they have...
Quoting Nicolas Duchon (2017-09-18 05:47:03)
The patch is included in the 0.19.0 milestone, which is due in about two weeks.
Should we just wait or install pyOpenSSL<17.3.0 in the interval ?
-- You are receiving this because you commented. Reply to this email directly, [1]view it on GitHub, or [2]mute the thread.
Verweise
Fixed by #72
https://pypi.python.org/pypi/pyOpenSSL
I don't know if it is breaking anything else, I'll test asap.
edit: in fact it breaks parts of acme / certbot