SegFault on startup

[Rx7TyreBurna]

Running on a Raspberry Pi Model B+

Openssl version -a: OpenSSL 1.0.1e 11 Feb 2013 built on: Wed Jul 30 04:35:10 UTC 2014 platform: debian-armhf options: bn(64,32) rc4(ptr,char) des(idx,cisc,16,long) blowfish(ptr) compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIO -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wa,--noexecstack -Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DAES_ASM -DGHASH_ASM OPENSSLDIR: "/usr/lib/ssl"

SSLSniff v0.8-3 (Pretty sure)

Generated a CA key / cert using Openssl.

Trying to start SSLSniff in authority mode, using the CA private key. As soon as I do, it segfaults.

Tried starting sslsniff in authority mode using the CA public key (cert, right?), and it starts, and runs, until a request is made, it then crashes.

Is there a way I can provide more information?

I've tried completely compiling from source, and have experienced the same issue.

[Rx7TyreBurna]

Segfault resolved by combining public key and private key into a single .pem. cat public.pem private.pem >> combined.pem

No longer getting a segfault. Maybe there needs to be a check in place for this? Error, instead of segfault.

Now getting: sslsniff 0.8 by Moxie Marlinspike running... terminate called after throwing an instance of 'boost::exception_detail::clone_implboost::exception_detail::error_info_injector' what(): boost::thread_resource_error Aborted

[Rx7TyreBurna]

Tried a few times, and it began working.

I suspect I had an incorrect rule in place for iptables nat rule.

This is a non-issue now. But, would like others to know, if they get segfault on startup, they may need to combine public and private.