Re: python2.7 SEGV in X509_verify_cert

[Thomas Klausner <wiz%NetBSD.org@localhost>]

On Sat, Jan 28, 2017 at 02:25:09AM +0100, Thomas Klausner wrote:
> On Sat, Jan 28, 2017 at 01:22:15AM +0100, Joerg Sonnenberger wrote:
> > On Sat, Jan 28, 2017 at 01:17:02AM +0100, Jesus Cea wrote:
> > > On 27/01/17 12:06, Paul Ripke wrote:
> > > > Core was generated by `python2.7'.
> > > > Program terminated with signal SIGSEGV, Segmentation fault.
> > > > #0  0x00007f7ff7e15f90 in ?? ()
> > > > (gdb) bt
> > > > #0  0x00007f7ff7e15f90 in ?? ()
> > > > #1  0x00007f7ff2ef09fe in ?? () from /usr/lib/libcrypto.so.8
> > > 
> > > I can NOT reproduce this in SmartOS, 2016Q4. In any case, seems to be a
> > > problem with OpenSSL library, not Python.
> > 
> > It is a problem in the cFFI usage of one of the crypto extension modules
> > outside the base distro.
> 
> I've filed an upstream bug report about this, see
> https://github.com/pyca/cryptography/issues/3372

After filing bug reports with four projects so far, this seems to be a
libffi issue.

libffi GIT on NetBSD/amd64 self tests look like this:

                === libffi Summary ===

# of expected passes            1465
# of unexpected failures        525

Do we have knowledgeable people for helping with libffi?
 Thomas