# Could not bind to the requested symbol name (OpenSSL)

**URL:** <https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377>\
**Category:** HSM\
**Created:** [August 29, 2022, 7:07am UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377 "2022-08-29T07:07:03Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![mSTYX](https://support.nitrokey.com/user_avatar/support.nitrokey.com/mstyx/32/1184_2.png) [@mSTYX](https://support.nitrokey.com/u/mSTYX)\
**Post date:** [August 29, 2022, 7:07am UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/1 "2022-08-29T07:07:03Z")

</div>

Heyho,

_new week, new problems …_

i can’t **create\_root\_cert.ini**

I use:

> openssl:  
> Installiert: 1.1.1n-0+deb11u3  
> Installationskandidat: 1.1.1n-0+deb11u3  
> Versionstabelle:  
> \*\*\* 1.1.1n-0+deb11u3 500  
> 500 [Index of /debian](http://deb.debian.org/debian) bullseye/main amd64 Packages  
> 500 [Index of /debian-security](http://security.debian.org/debian-security) bullseye-security/main amd64 Packages  
> 100 /var/lib/dpkg/status

I will do this command

> openssl req -config create\_root\_cert.ini -engine pkcs11 -keyform engine -key myverylongkey -new -x509 -days 3650 -sha512 -extensions v3\_ca -out …/certs/root.crt engine “pkcs11” set.

I get thus error:

> 139879345423680:error:2506406A:DSO support routines:dlfcn\_bind\_func:could not bind to the requested symbol name:…/crypto/dso/dso\_dlfcn.c:188:symname(EVP\_PKEY\_get\_base\_id): /usr/lib/x86\_64-linux-gnu/engines-1.1/pkcs11.so: undefined symbol: EVP\_PKEY\_get\_base\_id  
> 139879345423680:error:2506C06A:DSO support routines:DSO\_bind\_func:could not bind to the requested symbol name:…/crypto/dso/dso\_lib.c:186:

What do I have to do to get the missing symbols? I found some hints on “stackoverflow” but they were related to osX and others

Thanks in Advanced

---

<div class="post-metadata">

**Author:** ![sc-hsm](https://support.nitrokey.com/user_avatar/support.nitrokey.com/sc-hsm/32/304_2.png) [@sc-hsm](https://support.nitrokey.com/u/sc-hsm)\
**Post date:** [August 29, 2022, 7:42am UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/2 "2022-08-29T07:42:20Z")

</div>

I would recommend to use XCA instead, which is a frontend for OpenSSL that has PKCS#11 support integrated and that works well with the HSM.

I guess the problem is caused by a mismatch between OpenSSL and the installed OpenSC version. The OpenSSL package is progressing much faster than OpenSC and the API is frequently breaking.

That is the reason why we have a separate tooling in OpenSCDP and the PKI-as-a-Service Portal, which does not need complicated layers like PKCS#11 and engine-pkcs11.

---

<div class="post-metadata">

**Author:** ![mSTYX](https://support.nitrokey.com/user_avatar/support.nitrokey.com/mstyx/32/1184_2.png) [@mSTYX](https://support.nitrokey.com/u/mSTYX)\
**Post date:** [August 29, 2022, 9:04am UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/3 "2022-08-29T09:04:59Z")

</div>

thanks for your fast replay…

But, i don’t use a GUI. I have a “Server based” install (debian bullseye)  
i will try to find out more about the two “sturgeon packages” 😉

---

<div class="post-metadata">

**Author:** ![sc-hsm](https://support.nitrokey.com/user_avatar/support.nitrokey.com/sc-hsm/32/304_2.png) [@sc-hsm](https://support.nitrokey.com/u/sc-hsm)\
**Post date:** [August 29, 2022, 9:18am UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/4 "2022-08-29T09:18:30Z")

</div>

Then my recommendation is to compile matching releases of OpenSC and engine-pkcs11 locally. You might also find additional information in the [OpenSC project on Github](https://github.com/OpenSC/OpenSC).

---

<div class="post-metadata">

**Author:** ![saper](https://support.nitrokey.com/user_avatar/support.nitrokey.com/saper/32/493_2.png) [@saper](https://support.nitrokey.com/u/saper)\
**Post date:** [August 29, 2022, 9:40pm UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/5 "2022-08-29T21:40:39Z")

</div>

You didn’t tell us how did you get pkcs11 engine installed.

> [@mSTYX](#):
>
> could not bind to the requested symbol name:…/crypto/dso/dso\_dlfcn.c:188:symname(EVP\_PKEY\_get\_base\_id)

This is probably because your `pkcs11.so` engine has been compiled for new OpenSSL 3.x and you are using OpenSSL 1.1.1 or you are running into [Misleading error message(undefined symbol: EVP\_PKEY\_get\_base\_id) with engine load from OpenSSL1.1.1n · Issue #17962 · openssl/openssl · GitHub](https://github.com/openssl/openssl/issues/17962)

See [/docs/manmaster/man3/EVP\_PKEY\_get\_base\_id.html](https://beta.openssl.org/docs/manmaster/man3/EVP_PKEY_get_base_id.html#HISTORY) for more background.

---

<div class="post-metadata">

**Author:** ![mSTYX](https://support.nitrokey.com/user_avatar/support.nitrokey.com/mstyx/32/1184_2.png) [@mSTYX](https://support.nitrokey.com/u/mSTYX)\
**Post date:** [September 19, 2022, 12:25pm UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/6 "2022-09-19T12:25:59Z")

</div>

the same again… ok

---

<div class="post-metadata">

**Author:** ![saper](https://support.nitrokey.com/user_avatar/support.nitrokey.com/saper/32/493_2.png) [@saper](https://support.nitrokey.com/u/saper)\
**Post date:** [September 24, 2022, 11:36pm UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/7 "2022-09-24T23:36:32Z")

</div>

pardon?

---

<div class="post-metadata">

**Author:** ![mSTYX](https://support.nitrokey.com/user_avatar/support.nitrokey.com/mstyx/32/1184_2.png) [@mSTYX](https://support.nitrokey.com/u/mSTYX)\
**Post date:** [September 26, 2022, 5:34am UTC](https://support.nitrokey.com/t/could-not-bind-to-the-requested-symbol-name-openssl/4377/8 "2022-09-26T05:34:54Z")

</div>

Parlez-vous français ? ? 😉

Good Morning,

Sorry for being too brief here: I have produced the same problem again. I keep running into “incompatible packages” over and over again.

For the moment, we are consolidating again &Thanks for the support here, I’ll stay tuned!
