** Description changed:
- To be able to switch modules at runtime via configuration file change the
default module from opensc-pkcs11 to p11-proxy module, which by default loads
opensc-pkcs11 module unless configured by administrator to use something else.
- This also allows configuration where multiple modules can be used together
through the p11-proxy module.
+ [Impact]
- This aligns Ubuntu closer with other distributions, and allows using the
- same builds of opensc in embedded configurations on Ubuntu Core with
+ * To be able to switch modules at runtime via configuration file change
+ the default module from opensc-pkcs11 to p11-proxy module, which by
+ default loads opensc-pkcs11 module unless configured by administrator to
+ use something else.
+
+ * This also allows configuration where multiple modules can be used
+ together through the p11-proxy module.
+
+ * This aligns Ubuntu closer with other distributions, and allows using
+ the same builds of opensc in embedded configurations on Ubuntu Core with
specialized modules
- ProblemType: Bug
- DistroRelease: Ubuntu 20.04
- Package: opensc 0.20.0-3
- ProcVersionSignature: Ubuntu 5.4.0-107.121-generic 5.4.174
- Uname: Linux 5.4.0-107-generic aarch64
- NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp prl_fs_freeze
prl_fs prl_tg
- ApportVersion: 2.20.11-0ubuntu27.21
- Architecture: arm64
- Date: Thu Apr 7 14:50:08 2022
- InstallationDate: Installed on 2021-11-08 (150 days ago)
- InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release arm64
(20210824)
- SourcePackage: opensc
- UpgradeStatus: No upgrade log present (probably fresh install)
+ [Test Plan]
+
+ * detailed instructions how to reproduce the bug
+
+ * these should allow someone who is not familiar with the affected
+ package to reproduce the bug and verify that the updated package fixes
+ the problem.
+
+ * if other testing is appropriate to perform before landing this update,
+ this should also be described here.
+
+ [Where problems could occur]
+
+ * Think about what the upload changes in the software. Imagine the change is
+ wrong or breaks something else: how would this show up?
+
+ * It is assumed that any SRU candidate patch is well-tested before
+ upload and has a low overall risk of regression, but it's important
+ to make the effort to think about what ''could'' happen in the
+ event of a regression.
+
+ * This must '''never''' be "None" or "Low", or entirely an argument as to why
+ your upload is low risk.
+
+ * This both shows the SRU team that the risks have been considered,
+ and provides guidance to testers in regression-testing the SRU.
+
+ [Other Info]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
+ * and address these questions in advance
** Changed in: opensc (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: libp11 (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968175
Title:
Allow runtime configuration of pkcs11 modules through config file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libp11/+bug/1968175/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
