> On 27 Aug 2017, at 09:44, Thomas Hartwich <ceebor...@gmx.de> wrote: > > = >> The most comprehensive fix here is to do some history spelunking in >> PyOpenSSL to find out what the lowest version is that has this code block[1] >> in it, and then only execute the current ecCurve logic if that code block >> doesn’t appear to have worked. > I don't really get what implies this to me and how I can come around with > this issue. What do you mean with "only execute the current ecCurve > logic..."? How can this be done? > > I have the current versions of Twisted and pyOpenSSL running, so how can I > make sure that the latter loads the right curve properly?
You cannot, at least not using public APIs. This was a suggestion of an update to Twisted, not something you should be doing from your own code. Cory _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com https://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
