ICA HW token missing after the package update

Bug #1850294 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
Medium
Dimitri John Ledkov
opencryptoki (Ubuntu)
Fix Released
Undecided
Skipper Bug Screeners
Bionic
Invalid
Undecided
Unassigned
Disco
Won't Fix
Undecided
Unassigned
Eoan
Won't Fix
Undecided
Unassigned
Focal
Fix Released
Undecided
Skipper Bug Screeners

Bug Description

SRU Justification:
------------------

[Impact]

 * The libica (actually libica3) needs to be referred by it's "so name" (libica.so.3) to avoid situations where the ICA HW token is missing after a package update.

[Fix]

 * 73f05eb53f12197f081fd7ec75619c6ea3a39b2c "ICA: Refer libica by its so name"

 * 7f4113ba8653b8b18a6f1af6ab1d8eb90987626d "EP11: Refer libica by its so name"

[Test Case]

 * A s390x system (LPAR or z/VM) is needed with at least one crypto domain online.

 * Install opencryptoki package from bionic/universe.

 * Initialize a token and assign it to a certain slot, like with pkcsconf -I -c 1

 * Notice that the user that executes this command needs to be part of group 'pkcs11' and that the pkcsslotd.service is enabled and started.

 * Display the token (or all tokens) with pkcsconf -t

 * Perform an update (and make sure pkcsslotd.service got restarted) and display again using pkcsconf -t

[Regression Potential]

 * The regression potential can be considered as low, since:

 * it's just a one line change (in two files) of a #define in a way that it points to "libica.so.3" instead of "libica.so", so the diff is minimal

 * and bionic already ships libica3 today.

[Other Info]

 * This didn't happend yet to any Ubuntu user (afawk), but occurred at IBM tests and/or other distros, hence this is a 'preventive fix'.
__________

Please integrate proactive following 2 git commits

ICA: Refer libica by its so name :
https://github.com/opencryptoki/opencryptoki/commit/73f05eb53f12197f081fd7ec75619c6ea3a39b2c

EP11: Refer libica by its so name
https://github.com/opencryptoki/opencryptoki/commit/7f4113ba8653b8b18a6f1af6ab1d8eb90987626d

bugproxy (bugproxy)
tags: added: architecture-s39064 bugnameltc-182121 severity-high targetmilestone-inin1804
Changed in ubuntu:
assignee: nobody → Skipper Bug Screeners (skipper-screen-team)
affects: ubuntu → opencryptoki (Ubuntu)
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Dimitri John Ledkov (xnox)
Frank Heimes (fheimes)
Changed in opencryptoki (Ubuntu):
status: New → Confirmed
Changed in ubuntu-z-systems:
status: Triaged → Confirmed
Frank Heimes (fheimes)
no longer affects: ubuntu-z-systems/ubuntu-19.04
no longer affects: ubuntu-z-systems/ubuntu-19.10
no longer affects: ubuntu-z-systems/ubuntu-20.04
Frank Heimes (fheimes)
description: updated
Revision history for this message
Frank Heimes (fheimes) wrote :

Since Ubuntu 19.04 / Disco reached it's end-of-life on January the 23rd:
https://lists.ubuntu.com/archives/ubuntu-announce/2020-January/000253.html
the entry that marks this ticket as affecting 'Disco' is changed to 'Won't Fix'.

Changed in opencryptoki (Ubuntu Disco):
status: New → Won't Fix
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package opencryptoki - 3.12.1+dfsg-0ubuntu1

---------------
opencryptoki (3.12.1+dfsg-0ubuntu1) focal; urgency=medium

  * New upstream release LP: #1854148, LP: #1852089, LP: #1850294

 -- Dimitri John Ledkov <email address hidden> Thu, 06 Feb 2020 14:59:50 +0000

Changed in opencryptoki (Ubuntu Focal):
status: Confirmed → Fix Released
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Confirmed → In Progress
Revision history for this message
Frank Heimes (fheimes) wrote :

Changing the Eoan entry to Won't Fix, since Eoan reached it's EOL: https://lists.ubuntu.com/archives/ubuntu-announce/2020-July/000258.html

Changed in opencryptoki (Ubuntu Eoan):
status: New → Won't Fix
tags: added: fr-1013
Revision history for this message
Frank Heimes (fheimes) wrote :

Looks to me that the two commits do not fit to the bionic version of opencryptoki, which is:
opencryptoki | 3.9.0+dfsg-0ubuntu1.3 | bionic-updates/universe
because the two files (ica_s390_stdll/ica_specific.c, ep11_stdll/ep11_specific.c) do not come with an define "libica.so" line at all
and at github one can see that the patches landed only in v3.15.1 v3.15.0 v3.14.0 v3.13.0 v3.12.1 v3.12.0.
Hence I assume that the problem reported here does not affect bionic, is that correct?

Changed in opencryptoki (Ubuntu Bionic):
status: New → Incomplete
Changed in ubuntu-z-systems:
status: In Progress → Incomplete
Revision history for this message
Matthieu Clemenceau (mclemenceau) wrote :

Thanks @Frank, Can we confirm if this problem affects bionic indeed?

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2021-01-19 05:54 EDT-------
The fixes are not needed for 3.9

Revision history for this message
Frank Heimes (fheimes) wrote :

Hi Patrick,
thx for confirming.
Since 3.9.0 is the version that's in bionic/18.04, I'll remove the bionic entry, adjust the targetmilestone tag and close this ticket.

tags: added: targetmilestone-inin2004
removed: targetmilestone-inin1804
Changed in opencryptoki (Ubuntu Bionic):
status: Incomplete → Invalid
Changed in ubuntu-z-systems:
status: Incomplete → Fix Released
bugproxy (bugproxy)
tags: added: targetmilestone-inin1804
removed: targetmilestone-inin2004
bugproxy (bugproxy)
tags: added: targetmilestone-inin2004
removed: targetmilestone-inin1804
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2021-01-19 08:59 EDT-------
IBM Bugzilla status->closed, Fix Released by all requested Distros

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.