This update for python-cffi, python-cryptography fixes the following issues: Security issue fixed: - CVE-2018-10903: Fixed GCM tag forgery via truncated tag in finalize_with_tag API . Non-security issues fixed: python-cffi was updated to 1.11.2 : - fixed a build failure on i586 - Salt was unable to highstate in snapshot 20171129 - Update pytest in spec to add c directory tests in addition to testing directory. - update to version 1.11.2: * Fix Windows issue with managing the thread-state on CPython 3.0 to 3.5 - Update pytest in spec to add c directory tests in addition to testing directory. - Omit test_init_once_multithread tests as they rely on multiple threads finishing in a given time. Returns sporadic pass/fail within build. - Update to 1.11.1: * Fix tests, remove deprecated C API usage * Fix for 3.6.0/3.6.1/3.6.2 giving incompatible binary extensions * Fix for 3.7.0a1+ - Update to 1.11.0: * Support the modern standard types char16_t and char32_t. These work like wchar_t: they represent one unicode character, or when used as charN_t * or charN_t[] they represent a unicode string. The difference with wchar_t is that they have a known, fixed size. They should work at all places that used to work with wchar_t . Note that with set_source, you need to make sure that these types are actually defined by the C source you provide . * Support the C99 types float _Complex and double _Complex. Note that libffi doesn"t support them, which means that in the ABI mode you still cannot call C functions that take complex numbers directly as arguments or return type. * Fixed a rare race condition when creating multiple FFI instances from multiple threads. * Windows: using callbacks can be messy because the CFFI internal error messages show up to stderr-but stderr goes nowhere in many applications. This makes it particularly hard to get started with the embedding mode. So what is new in CFFI is that now, on Windows CFFI will try to open a non-modal MessageBox . The MessageBox is only visible if the process stays alive: typically, console applications that crash close immediately, but that is also the situation where stderr should be visible anyway. * Progress on support for callbacks in NetBSD. * Functions returning booleans would in some case still return 0 or 1 instead of False or True. Fixed. * ffi.gc now takes an optional third parameter, which gives an estimate of the size of the object. So far, this is only used by PyPy, to make the next GC occur more quickly . In the future, this might have an effect on CPython too . * Add a note to the documentation: the ABI mode gives function objects that are slower to call than the API mode does. For some reason it is often thought to be faster. It is not! - Update to 1.10.1: * Fixed the line numbers reported in case of cdef errors. Also, I just noticed, but pycparser always supported the preprocessor directive # 42 foo.h to mean from the next line, we"re in file foo.h starting from line 42 ;, which it puts in the error messages. - update to 1.10.0: * Issue #295: use calloc directly instead of PyObject_Malloc+memset to handle ffi.new with a default allocator. Speeds up ffi.new where most of the time you never touch most of the array. * Some OS/X build fixes . * Improve a couple of error messages: when getting mismatched versions of cffi and its backend; and when calling functions which cannot be called with libffi because an argument is a struct that is too complicated ; . * Add support for some unusual compilers * Implemented the remaining cases for ffi.from_buffer. Now all buffer/memoryview objects can be passed. The one remaining check is against passing unicode strings in Python 2. * The C type _Bool or bool now converts to a Python boolean when reading, instead of the content of the byte as an integer. The potential incompatibility here is what occurs if the byte contains a value different from 0 and 1. Previously, it would just return it; with this change, CFFI raises an exception in this case. But this case means undefined behavior ; in C; if you really have to interface with a library relying on this, don"t use bool in the CFFI side. Also, it is still valid to use a byte string as initializer for a bool[], but now it must only contain \x00 or \x01. As an aside, ffi.string no longer works on bool[] . * ffi.buffer is now the name of cffi"s buffer type, and ffi.buffer works like before but is the constructor of that type. * ffi.addressof now works also in in-line mode, not only in out-of-line mode. This is useful for taking the address of global variables. * Issue #255: cdata objects of a primitive type are now compared and ordered by value. For example, lt;cdata "int" 42 gt; compares equal to 42 and lt;cdata "char" b"A" gt; compares equal to b"A". Unlike C, lt;cdata "int" -1 gt; does not compare equal to ffi.cast: it compares smaller, because -1 lt; 4294967295. * PyPy: ffi.new and ffi.new_allocator did not record memory pressure ;, causing the GC to run too infrequently if you call ffi.new very often and/or with large arrays. Fixed in PyPy 5.7. * Support in ffi.cdef for numeric expressions with + or -. Assumes that there is no overflow; it should be fixed first before we add more general support for arbitrary arithmetic on constants. - do not generate HTML documentation for packages that are indirect dependencies of Sphinx - update to 1.9.1 - Structs with variable-sized arrays as their last field: now we track the length of the array after ffi.new is called, just like we always tracked the length of ffi.new. This lets us detect out-of-range accesses to array items. This also lets us display a better repr, and have the total size returned by ffi.sizeof and ffi.buffer. Previously both functions would return a result based on the size of the declared structure type, with an assumed empty array. - Add support in cdef/set_source for unspecified-length arrays in typedefs: typedef int foo_t[...];. It was already supported for global variables or structure fields. - I turned in v1.8 a warning from cffi/model.py into an error: "enum xxx" has no values explicitly defined: refusing to guess which integer type it is meant to be . Now I"m turning it back to a warning again; it seems that guessing that the enum has size int is a 99%-safe bet. - Fix leaks in the code handling FILE * arguments. In CPython 3 there is a remaining issue that is hard to fix: if you pass a Python file object to a FILE * argument, then os.dup is used and the new file descriptor is only closed when the GC reclaims the Python file object-and not at the earlier time when you call close, which only closes the original file descriptor. If this is an issue, you should avoid this automatic convertion of Python file objects: instead, explicitly manipulate file descriptors and call fdopen from C . - When passing a void * argument to a function with a different pointer type, or vice-versa, the cast occurs automatically, like in C. The same occurs for initialization with ffi.new and a few other places. However, I thought that char * had the same property-but I was mistaken. In C you get the usual warning if you try to give a char * to a char ** argument, for example. Sorry about the confusion. This has been fixed in CFFI by giving for now a warning, too. It will turn into an error in a future version. - Issue #283: fixed ffi.new on structures/unions with nested anonymous structures/unions, when there is at least one union in the mix. When initialized with a list or a dict, it should now behave more closely like the { } syntax does in GCC. - CPython 3.x: experimental: the generated C extension modules now use the limited API ;, which means that, as a compiled .so/.dll, it should work directly on any version of CPython gt;= 3.2. The name produced by distutils is still version-specific. To get the version-independent name, you can rename it manually to NAME.abi3.so, or use the very recent setuptools 26. - Added ffi.compile, similar to python setup.py build --debug but defaulting to True if we are running a debugging version of Python itself. - Removed the restriction that ffi.from_buffer cannot be used on byte strings. Now you can get a char * out of a byte string, which is valid as long as the string object is kept alive. - PyPy 5.4 can now pass a byte string directly to a char * argument . This used to be a CPython-only optimization. - ffi.gc removes the destructor on an object previously created by another call to ffi.gc - bool now returns False if the value is zero , and True otherwise. Previously this would only return False for cdata objects of a pointer type when the pointer is NULL. - bytearrays: ffi.from_buffer is now supported. To call a C function with a char * argument from a buffer object-now including bytearrays-you write lib.foo. Additionally, this is now supported: p[0:length] = bytearray-object. The problem with this was that a iterating over bytearrays gives numbers instead of characters. - C++: compiling the generated C code with C++ was supposed to work, but failed if you make use the bool type . - help and help now give useful information, as well as dir where p is a struct or pointer-to-struct. - update for multipython build - disable negative left shift warning in test suite to prevent failures with gcc6, until upstream fixes the undefined code in question - Update to version 1.6.0: * ffi.list_types * ffi.unpack * extern Python+C ; * in API mode, lib.foo.__doc__ contains the C signature now. * Yet another attempt at robustness of ffi.def_extern against CPython"s interpreter shutdown logic. - Update in SLE-12 - Make this version of the package compatible with OpenSSL 1.1.1d, thus fixing bsc#1149792. - bsc#1101820 CVE-2018-10903 GCM tag forgery via truncated tag in finalize_with_tag API - Add proper conditional for the python2, the ifpython works only for the requires/etc - add missing dependency on python ssl - update to version 2.1.4: * Added X509_up_ref for an upcoming pyOpenSSL release. - update to version 2.1.3: * Updated Windows, macOS, and manylinux1 wheels to be compiled with OpenSSL 1.1.0g. - update to version 2.1.2: * Corrected a bug with the manylinux1 wheels where OpenSSL"s stack was marked executable. - fix BuildRequires conditions for python3 - update to 2.1.1 - Fix cffi version requirement. - Disable memleak tests to fix build with OpenSSL 1.1 - update to 2.0.3 - update to 2.0.2 - update to 2.0 - update to 1.9 - add python-packaging to requirements explicitly instead of relying on setuptools to pull it in - Switch to singlespec approach - update to 1.8.1 - Adust Requires and BuildRequires