[issue27768] ssl: get CPU cap flags for AESNI and PCLMULQDQ

2017-09-05 Thread Antoine Pitrou
Antoine Pitrou added the comment: > Instead of making the cipher suite selection more complicated, we should > just rely on OpenSSL to provide sensible defaults. +1 ! -- ___ Python tracker

[issue27768] ssl: get CPU cap flags for AESNI and PCLMULQDQ

2017-09-05 Thread Christian Heimes
Christian Heimes added the comment: I'm retracting my patch. Instead of making the cipher suite selection more complicated, we should just rely on OpenSSL to provide sensible defaults. -- resolution: -> rejected stage: -> resolved status: open -> closed

[issue27768] ssl: get CPU cap flags for AESNI and PCLMULQDQ

2016-09-15 Thread Giampaolo Rodola'
Changes by Giampaolo Rodola' : -- nosy: -giampaolo.rodola ___ Python tracker ___ ___

[issue27768] ssl: get CPU cap flags for AESNI and PCLMULQDQ

2016-09-15 Thread Christian Heimes
Changes by Christian Heimes : -- assignee: -> christian.heimes components: +SSL ___ Python tracker ___

[issue27768] ssl: get CPU cap flags for AESNI and PCLMULQDQ

2016-08-26 Thread Christian Heimes
Christian Heimes added the comment: GPS, I no longer want a general API for CPU cap vector. The ssl module and 3rd party packages are only interested in two properties of the current hardware: are AESNI and PCLMULQDQ instructions available and enabled. I'm pretty sure ctypes won't work on