delta/python-packages/cryptography.git/src/_cffi_src/openssl/callbacks.py, branch 1.6 github.com: pyca/cryptography.git C locking callback (#3226) 2016-11-13T20:55:22+00:00 Alex Gaynor alex.gaynor@gmail.com 2016-11-13T20:55:22+00:00 d862933de5c344fcdf99ab2f43f3bf8da65f3e41 * 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. 
* 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) 2016-07-29T06:45:42+00:00 Maximilian Hils git@maximilianhils.com 2016-07-29T06:45:42+00:00 6e9e489fd80424811d1b228d64f3b1b3d23de2a8 






remove the callbacks we don't use in cryptography
2016-01-08T05:08:57+00:00

Paul Kehrer
paul.l.kehrer@gmail.com

2016-01-08T05:08:57+00:00

90ad38fae043268e3bfe2844f1996707bfd0caf8












Port callbacks to new static callback
2016-01-07T19:38:34+00:00

Christian Heimes
christian@python.org

2015-11-19T15:18:04+00:00

830af271de1c9c3589bcce12cc08573850141f51

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>





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>