| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | C locking callback (#3226) | Alex Gaynor | 2016-11-13 | 1 | -1/+72 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove Python OpenSSL locking callback and replace it with one in C The Python OpenSSL locking callback is unsafe; if GC is triggered during the callback's invocation, it can result in the callback being invoked reentrantly, which can lead to deadlocks. This patch replaces it with one in C that gets built at compile time via cffi along with the rest of the OpenSSL binding. * fixes for some issues * unused * revert these changes * these two for good measure * missing param * sigh, syntax * delete tests that assumed an ability to mess with locks * style fixes * licensing stuff * utf8 * Unicode. Huh. What it isn't good for, absolutely nothing. | ||||
| * | disable static callbacks on Python 3.5 (refs #2970) (#3063) | Maximilian Hils | 2016-07-29 | 1 | -1/+4 |
| | | |||||
| * | remove the callbacks we don't use in cryptography | Paul Kehrer | 2016-01-07 | 1 | -61/+0 |
| | | |||||
| * | Port callbacks to new static callback | Christian Heimes | 2016-01-07 | 1 | -0/+111 |
| cffi 1.4.0 will introduce a new API to create static callbacks. Contrary to the old callback API, static callbacks no longer depend on libffi's dynamic code generation for closures. Static code has some benefits over dynamic generation. For example the code is faster. Also it doesn't need writeable and executable memory mappings, which makes it compatible with SELinux's deny execmem policy. The branch depends on PR #2488. https://bitbucket.org/cffi/cffi/issues/232/static-callbacks Closes: #2477 Signed-off-by: Christian Heimes <cheimes@redhat.com> | |||||
 |
index : cloud-email/cryptography | |
| python cryptography | James |
| aboutsummaryrefslogtreecommitdiffstats |