[qdigidocclient] Crash on Ubuntu Oneiric Beta when updating Server Access Certificate

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run qdigidocclient
2. Choose to sign a document
3. Accept downloading Server Access Certificate
4. Insert PIN1 to confirm

What is the expected output? What do you see instead?

Expect success, see Segmentation Fault

What version of the product are you using? On what operating system?

Ubuntu Oneiric Beta 2, latest Oneiric test packages from 
https://launchpad.net/~boamaod/+archive/esteid-test

Original issue reported on code.google.com by boamaod on 9 Oct 2011 at 8:16

Attachments:

• Esteid_Oneric_Qdigidocclient.txt

[GoogleCodeExporter]

It appears to crash somewhere in openssl code after calling SSL_CTX_new() from 
qdigidoc (sslConnect.cpp:223):

    sctx = SSL_CTX_new( SSLv23_client_method() );

My guess would be that you are hitting an openssl bug. For what it's worth, I 
can't reproduce the crash in Fedora.

Original comment by kalevlember@gmail.com on 10 Oct 2011 at 10:02

[GoogleCodeExporter]

Using opensc 0.12.5361.429-ubuntu-11-04 from 
http://ftp.id.eesti.ee/pub/id/signed_repository/ubuntu/pool/main/o/opensc/ 
fixes the issue.

Original comment by boamaod on 12 Oct 2011 at 10:31

[GoogleCodeExporter]

Using opensc 0.12.2-2 from http://packages.debian.org/wheezy/opensc does not 
fix the issue.

Original comment by boamaod on 12 Oct 2011 at 10:55

[GoogleCodeExporter]

What version of opensc did you get the crash with?

Original comment by kalevlember@gmail.com on 12 Oct 2011 at 10:56

[GoogleCodeExporter]

The initial crash was produced using 0.12.1-1ubuntu1 which is default in 
Oneiric and can be downloaded from http://packages.ubuntu.com/oneiric/opensc.

Original comment by boamaod on 12 Oct 2011 at 11:02

[GoogleCodeExporter]

This is bizarre. I wonder if the backtrace would reveal anything interesting 
with openssl debug symbols installed.

Are you able to build from opensc git? Finding a specific commit that caused 
the regression might help. Could try bisecting from git between r5361 and 
0.12.1 to find out what change caused it, and then filing a ticket with opensc 
upstream trac.

Original comment by kalevlember@gmail.com on 12 Oct 2011 at 9:40

[GoogleCodeExporter]

Instead of using pre-built packages, please verify if the source versions, when 
compiled against the same OpenSSL with the same compiler, actually trigger the 
same result.

Original comment by martin.paljak on 18 Oct 2011 at 9:20

[GoogleCodeExporter]

I built OpenSC 0.12.2 with LibSSL 1.0.0e and this resulted the same bug. I also 
built OpenSC 0.12.2 with LibSSL 0.9.8o and this seemed to work all right, the 
bug did not appear.

Any further directions? Should I create any more backtraces with OpenSC and 
LibSSL debug symbols turned on?

Original comment by boamaod on 22 Oct 2011 at 8:25

[GoogleCodeExporter]

I add backtrace with LibSSL debug symbols enabled. It's OpenSC 0.12.1 and 
LibSSL 1.0.0e I believe (the default combination in Oneiric).

Original comment by boamaod on 23 Oct 2011 at 8:05

Attachments:

• qdigidoc_with_ssl_debug_symbols.txt

[GoogleCodeExporter]

The latest official OpenSC tarball packaged for Ubuntu Oneiric 
(0.12.2-2~esteid5) can be found in Estobuntu PPA at 
https://launchpad.net/~estobuntu/+archive/ppa

If you have the problems indicated in this bug report, I believe this is the 
most adequate package at the market to solve them.

Original comment by boamaod on 25 Oct 2011 at 9:02

[GoogleCodeExporter]

The problem is still there in current Precise alpha release. We could fix it 
for Precise the same way, but this is kind of inconvenient, since the packages 
for Precise will be uploaded to Ubuntu official repositories and we it's not 
possible to build OpenSC with an old LibSSL in that context.

Original comment by boamaod on 11 Jan 2012 at 10:37

[GoogleCodeExporter]

Tried with libssl1.0.0 (ver 1.0.0e-2ubuntu4.2, compiled with -DPURIFY, hope I 
did it correctly, see http://www.openssl.org//support/faq.html#PROG14) on 
Ubuntu Oneiric using Valgrind. It didn't crash, but produced and enormous log 
(attached).

Any further ideas?

Original comment by boamaod on 3 Apr 2012 at 9:33

Attachments:

• qdigidoclient.valgrind.verbose2.log

[GoogleCodeExporter]

I'm pretty certain I'm running into this exact thing on Gentoo.

Tested with dev-libs/openssl-1.0.0g and j

gdb thread apply all bt full attached.

Original comment by LKooglizmus on 5 Jul 2012 at 7:18

Attachments:

• qdigidoc-sigsegv-openssl-debug-full.txt

[GoogleCodeExporter]

app-crypt/qdigidoc-0.4.1

Original comment by LKooglizmus on 5 Jul 2012 at 7:19