[Bug 1561598] Comment bridged from LTC Bugzilla

[bugproxy]

------- Comment From Christian.Rund at de.ibm.com 2016-04-07 04:34 EDT-------
Due to the Easter break we had not been able until yesterday to internally discuss the topic, and we had all but ignored this defect - your asking one more time for info next time before closing a defect is highly appreciated. Thanks.

As to the outcomes of our discussion we found that:
1) In a development role a user would install 'libopencryptoki-dev' and be able to build and run an externally provided package (ok).

2) But how does 'distribution to production machines' work for open source
packages using the package's bootstrap, configure, make process?
When it comes to environments with a build machine and later distribution
of packages to production machines (production machines without devel packages installed!)
the build must occur using the soname of the libraries
Simple example: gcc test_ock.c -g -O0 -o test_ock /usr/lib/opencryptoki/libopencryptoki.so.0 -ldl  -I /root/opencryptoki/usr/include/pkcs11/
This might be well-documented and even well-known for Debian/Ubuntu systems -
is there documentation about this?

Please advise.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to opencryptoki in Ubuntu.
https://bugs.launchpad.net/bugs/1561598

Title:
  Missing link to opencryptoki library by libopencryptoki0 package

Status in opencryptoki package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  Summary
  =======
  The 'libopencryptoki0' package is missing a library link of /usr/lib/libopencryptoki.so -> opencryptoki/libopencryptoki.so.0

  Details
  =====
  The opencryptoki library is not found by dynamically linked executables if /usr/lib/libopencryptoki.so does not exist as link to the opencryptoki library.

  root at s8314007:~#  dpkg -L libopencryptoki0|grep libopencryptoki
  /usr/lib/opencryptoki/libopencryptoki.so.0.0.0
  ...
  /usr/lib/libopencryptoki.so.0
  /usr/lib/libopencryptoki.so.0.0.0
  /usr/lib/opencryptoki/libopencryptoki.so.0
  root at s8314007:~# ll /usr/lib/libopencryptoki.so.0
  lrwxrwxrwx 1 root root 33 Feb 24 12:57 /usr/lib/libopencryptoki.so.0 -> opencryptoki/libopencryptoki.so.0
  root at s8314007:~# ll /usr/lib/libopencryptoki.so.0.0.0
  lrwxrwxrwx 1 root root 37 Feb 24 12:57 /usr/lib/libopencryptoki.so.0.0.0 -> opencryptoki/libopencryptoki.so.0.0.0
  root at s8314007:~# ll /usr/lib/opencryptoki/libopencryptoki.so.0.0.0
  -rw-r--r-- 1 root root 80840 Feb 24 12:57 /usr/lib/opencryptoki/libopencryptoki.so.0.0.0

   
  ---uname output---
  Linux s8314007 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:07:12 UTC 2016 s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:  2964 Model:    702     N96 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Install the opencryptoki 3.4.1 package if not already installed/provided

  2) Bring up and initialize the EP11 Token:
      modprobe ap
      lszcrypt -VVV     // check for a CEX5P card to be available 'online'
      systemctl start pkcsslotd.service
      pkcsconf -t   // check for the EP11 Token slot number
      pkcsconf -c <SLOT> -I
      pkcsconf -c <SLOT> -P
      pkcsconf -c <SLOT> -u
      pkcsconf -c <SLOT> -p

  3) Copy the opencryptoki-3.4.1.tgz package to the system (mind
  opencryptoki 3.4.1 should be already provided but this package also
  contains the OC testcases.

  4) ./bootstrap.sh, ./configure --enable-testcases, make

  5) cd testcases/crypto; ./aes_tests -slot 4 (or whichever slot the
  EP11 token is)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/opencryptoki/+bug/1561598/+subscriptions