In the lucid version of libopencryptoki0, there's an /etc/ld.so.conf.d/opencryptoki-x86_64.conf that includes /usr/lib/opencryptoki/stdll. That's how the lucid version was able to find the backend modules.
This was removed in 2.3.1+dfsg-1. From the changelog:
* debian/rules:
- Do no install /etc/ld.so.conf.d/opencryptoki-i486.conf
- Creating instead soft-links in /usr/lib
The rules file does in fact create symlinks in /usr/lib. However, it creates symlinks for *.so.*, but pkcs11_startup creates configuration files that reference *.so. (Note the missing version in the filenames.)
A simple fix would be to make symlinks for *.so* in /usr/lib.
I think I found the problem.
In the lucid version of libopencryptoki0, there's an /etc/ld. so.conf. d/opencryptoki- x86_64. conf that includes /usr/lib/ opencryptoki/ stdll. That's how the lucid version was able to find the backend modules.
This was removed in 2.3.1+dfsg-1. From the changelog:
* debian/rules: so.conf. d/opencryptoki- i486.conf
- Do no install /etc/ld.
- Creating instead soft-links in /usr/lib
The rules file does in fact create symlinks in /usr/lib. However, it creates symlinks for *.so.*, but pkcs11_startup creates configuration files that reference *.so. (Note the missing version in the filenames.)
A simple fix would be to make symlinks for *.so* in /usr/lib.