➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients bkabrda, christian.heimes, dholth, dmalcolm, doughellmann, jpokorny, lukecarrier, pitrou, rbcollins, rpetrov, yolanda.robla
Date 2017-01-17.20:19:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1484684340.8.0.616410570777.issue9216@psf.upfronthosting.co.za>
In-reply-to
Content 
The separate module idea is an interesting one, though I wonder if it aligns with users' goals.  Perhaps some users simply want to set the OPENSSL_FORCE_FIPS_MODE environment variable and then run existing Python code with it to ensure that code is FIPS-compliant.  A separate module assumes that the developer is the one who makes the decision of running in FIPS compliance mode or not.
History
Date User Action Args
2017-01-17 20:19:00pitrousetrecipients: + pitrou, christian.heimes, rbcollins, rpetrov, doughellmann, dmalcolm, dholth, jpokorny, bkabrda, lukecarrier, yolanda.robla
2017-01-17 20:19:00pitrousetmessageid: <1484684340.8.0.616410570777.issue9216@psf.upfronthosting.co.za>
2017-01-17 20:19:00pitroulinkissue9216 messages
2017-01-17 20:19:00pitroucreate