AnsweredAssumed Answered

CST HSM - Segmentation fault (core dumped)

Question asked by Tomas Klein on Sep 9, 2019
Latest reply on Nov 12, 2019 by Sherin Jasper

Like • Show 1 Like1
Comment • 5

Hello,

I have implemented solution to sign the u-boot and zImage with CST tool. Now I would like to implement CST tool to work with HSM module. I already have PKI tree generated on the HSM. I created the CST tool with back_end-hsm, create hsm.cfg file with path to the certificate and run CST tool. After a moment I get error Segmentation fault (core dumped). With cst tool located in /linux64/bin/cst there is no problem to sign the image, but with back_end-hsm I get segmentation fault. (CST 3.1.0 and also with CST 3.2.0)

EDIT:

I am using module libsc-hsm-pkcs11.so, error is on the line 589 (ENGINE_ctrl_cmd_string (eng, "MODULE_PATH", hsm_conf.module_path, 0);)

Thank you for any idea.

Best regards

Tomas Klein

Tomas Klein Oct 25, 2019 4:50 AM

Correct Answer

I solve the problem by moving the Engine constructor (ENGINE *engine_hsm (void); - e_hsm.c, line: 124), from C file to to e_hsm.h (files path: cst-3.1.0/release/code/back_end-hsm/src)

See the reply in context

No one else had this question

Outcomes

Yuri Muhin

Sep 23, 2019 10:10 PM

Hello,

Would You please provide more details how Your CST has been build;

what toolchain and OS were used?

Regards,

Yuri.

Actions

Tomas Klein Oct 25, 2019 4:50 AM

I solve the problem by moving the Engine constructor (ENGINE *engine_hsm (void); - e_hsm.c, line: 124), from C file to to e_hsm.h (files path: cst-3.1.0/release/code/back_end-hsm/src)

2 people found this helpful

Actions

Sherin Jasper @ Tomas Klein on Nov 11, 2019 4:54 AM

I did the same. But this doesn't work.

Does it have anything to do with version of openssl ? I am using the openssl 1.1.1 with Ubuntu18.04

Actions

Tomas Klein @ Sherin Jasper on Nov 12, 2019 2:39 AM

In our case, we also using openssl version 1.1.1, cst 3.1.0 and library to comunicate with HSM (GitHub - CardContact/sc-hsm-embedded: PKCS#11 and CSP-Minidriver library for the SmartCard-HSM and STARCOS based signatu… )

Actions

Sherin Jasper @ Tomas Klein on Nov 12, 2019 7:57 AM

Do u have any steps u had already followed. ?

This is the error i got after using cst-hsm compilation

cst[20371]: segfault at ffffffff8cdac980 ip 00007fa5b8c56fbc sp 00007ffc19f0f320 error 5 in libcrypto.so.1.1[7fa5b8b04000+29b000]

this is the configuration I am using. Even i tried static compilation of those.

ldd /usr/bin/openssl
   linux-vdso.so.1 (0x00007ffe39bd5000)
   libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007fdeefe05000)
   libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007fdeef93a000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fdeef71b000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdeef32a000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fdeef126000)
   /lib64/ld-linux-x86-64.so.2 (0x00007fdef0345000)

I solve the problem by moving the Engine constructor (ENGINE *engine_hsm (void); - e_hsm.c, line: 124), from C file to to e_hsm.h (files path: cst-3.1.0/release/code/back_end-hsm/src)

Where exactly you moved the line ?

Actions

5 Replies

Yuri Muhin Sep 23, 2019 10:10 PM
Mark Correct
Correct Answer
Hello,

Would You please provide more details how Your CST has been build;
what toolchain and OS were used?

Regards,
Yuri.
Like • Show 0 Likes0
Actions
Tomas Klein Oct 25, 2019 4:50 AM
Unmark Correct
Correct Answer
I solve the problem by moving the Engine constructor (ENGINE *engine_hsm (void); - e_hsm.c, line: 124), from C file to to e_hsm.h (files path: cst-3.1.0/release/code/back_end-hsm/src)
2 people found this helpful
Like • Show 1 Like1
Actions
- Sherin Jasper @ Tomas Klein on Nov 11, 2019 4:54 AM
  Mark Correct
  Correct Answer
  I did the same. But this doesn't work.
  
  Does it have anything to do with version of openssl ? I am using the openssl 1.1.1 with Ubuntu18.04
  Like • Show 0 Likes0
  Actions
  - Tomas Klein @ Sherin Jasper on Nov 12, 2019 2:39 AM
    Mark Correct
    Correct Answer
    In our case, we also using openssl version 1.1.1, cst 3.1.0 and library to comunicate with HSM (GitHub - CardContact/sc-hsm-embedded: PKCS#11 and CSP-Minidriver library for the SmartCard-HSM and STARCOS based signatu… )
    Like • Show 0 Likes0
    Actions
    - Sherin Jasper @ Tomas Klein on Nov 12, 2019 7:57 AM
      Mark Correct
      Correct Answer
      Do u have any steps u had already followed. ?
      
      This is the error i got after using cst-hsm compilation
      cst[20371]: segfault at ffffffff8cdac980 ip 00007fa5b8c56fbc sp 00007ffc19f0f320 error 5 in libcrypto.so.1.1[7fa5b8b04000+29b000]
      
      this is the configuration I am using. Even i tried static compilation of those.
      ldd /usr/bin/openssl
         linux-vdso.so.1 (0x00007ffe39bd5000)
         libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007fdeefe05000)
         libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007fdeef93a000)
         libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fdeef71b000)
         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fdeef32a000)
         libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fdeef126000)
         /lib64/ld-linux-x86-64.so.2 (0x00007fdef0345000)
      
      I solve the problem by moving the Engine constructor (ENGINE *engine_hsm (void); - e_hsm.c, line: 124), from C file to to e_hsm.h (files path: cst-3.1.0/release/code/back_end-hsm/src)
      
      Where exactly you moved the line ?
      Like • Show 0 Likes0
      Actions

CST HSM - Segmentation fault (core dumped)

Outcomes

Related Content

Recommended Content

Incoming Links