[stunnel-users] Segfault in stunnel

[Michal Trojnara]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm sorry.  I did not intend to send this email to the whole list.
Please ignore it.

Best regards,
	Mike

On 26.04.2015 18:21, Michal Trojnara wrote:
> Panie Mirku,
> 
> Bardzo proszę dać znać, gdyby potrzebował Pan pomocy w zebraniu 
> informacji o które prosiłem w poniższym mailu.  "error 4" w dmesgu 
> oznacza po ludzku, że aplikacja próbowała odczytać nieprzydzielony
> jej fragment pamięci.  Może to nic groźnego, ale wolę dmuchać na
> zimne.
> 
> Z poważaniem, Michał Trojnara (autor stunnela)
> 
> On 25.04.2015 11:15, Michal Trojnara wrote:
>> Hi Mirek,
> 
>> Please collect the stack backtrace as explained here: 
>> http://linux.bytesex.org/gdb.html
> 
>> Make sure to send the backtrace directly to me only, as your 
>> problem may have severe security implications.  I will work with 
>> you to solve it, and then I will provide a solution to the
>> mailing list subscribers.
> 
>> I may also need your custom stunnel 5.15 binary and the
>> generated core files, so please save them.
> 
>> Best regards, Mike
> 
>> On 25.04.2015 00:10, Miroslaw Pietrzyk wrote:
>>> Hi, I have a problem with one of the stunnel installation 
>>> (debian7). After some time of operation automatically turns 
>>> itself off with the message: (...) Apr 24 21:03:45 routerpri 
>>> kernel: [177332.400502] stunnel[34426]: segfault at 0 ip 
>>> 00007f1f99ca9e20 sp 00007f1f99c16c68 error 4 in 
>>> stunnel[7f1f99c94000+24000] (...) Apr 24 21:21:36 routerpri 
>>> kernel: [178402.360532] stunnel[34795]: segfault at 0 ip 
>>> 00007f84d6b8be20 sp 00007f84d6b49c68 error 4 in 
>>> stunnel[7f84d6b76000+24000] (...) Apr 24 21:23:31 routerpri 
>>> kernel: [178517.215345] stunnel[34908]: segfault at 0 ip 
>>> 00007f150c5b3e20 sp 00007f150c58cc68 error 4 in 
>>> stunnel[7f150c59e000+24000] (...)
> 
> 
>>> stunnel 5.15 on x86_64-unknown-linux-gnu platform 
>>> Compiled/running with OpenSSL 1.0.1e 11 Feb 2013
> 
>>> stunnel.conf: pid = /var/run/stunnel.pid socket =
>>> l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 7 output =
>>> /var/log/stunnel.log syslog = yes client = no fips = no verify
>>> = 0 CAfile = /etc/stunnel/SubCA2.crt CRLfile =
>>> /etc/stunnel/SubCA2_CRL.pem
> 
>>> [service_1] accept = 192.168.1.10:1000 connect = 
>>> 192.168.1.10:1234 cert = /etc/stunnel/cert1.crt key = 
>>> /etc/stunnel/cert1_key.pem ciphers = 
>>> HIGH:!SSLv2:!ADH:!Exp:!aNULL:!eNULL:!NULL sslVersion = TLSv1.2
> 
>>> When I use the lower level of encryption for example SSLv3, 
>>> problem occurs after a longer period of normal operation. I
>>> will only add that the problem has also appeared on the
>>> previous version 4.54, which I was updating to the newest. Do
>>> you have any idea what could be causing the problem.
> 
>>> Regards Mirek
> 
> 
>>> _______________________________________________ stunnel-users 
>>> mailing list stunnel-users at stunnel.org 
>>> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
> 
> 
> 
> _______________________________________________ stunnel-users
> mailing list stunnel-users at stunnel.org 
> https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJVPRD8AAoJEC78f/DUFuAUjAEQAJF27jGLLM3HuNykideEVmPz
gD4X4BXRxpNfGkai1kWCGwao6JBrxOrkMmz4XWwUEg73o7NNsOdEPiMH6iyAGB5G
WtI/R98KRCtTOdfwq8tw4lmXNMm24CclP8Uer7mJ1WYpluHcxjF7wMqRO4jwWSyR
WRL72GOW4/nRxIcZKMVeck7LEu9Tolc46NOWZUXcIgAWoYWXSuwtPJNPp4P9ryuV
iRnT42PCR89Bt2o3rjrp7zycIl7R26rMXKLjkSijOE1NkNGY4A6l8HzKKAGIXnUD
d5u/ZCer1gC4e+cxSmt5L62urNUugvdDet6+wpsYbB4n3tYEyvU3+MTuGk6N5o6X
NGCleMRxLPZMQuvULj1cT7MxHVS5YsVPK2g0LBDPJh96vKM9UAAq0M3V4rlzHOjb
1EXWT4CH2l6awi3EKBZnC0B7TrNjKoOUIqd3kbRHWo9lCQysyZ32F4ioEH+zP5Fq
gxzkNLHWJeRLqI83i4AN1gmwPrPmmTkwJ9Jhy0SVPeAtJnJTpJn9O80MTfe12QB9
bA748cJ7U3/8IaeH2+ZoWKFUURPHFRWgp0P9FwxrwpnQfhkqB6u9hy9oUmVfwMOH
bd5rMfzLENMmAT4j8yBHtItiiM9IBhDf/WEevUH1wzgwyyNxtYitlZdkNyuCZ54M
iDX7t+fvj4d+o3C9A6lt
=3cZa
-----END PGP SIGNATURE-----