From 8c2893d8eba1953731cdcd095828ac0c4dfaa161 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Douglas=20Mendiz=C3=A1bal?= Date: Thu, 17 Mar 2016 13:23:35 -0500 Subject: [PATCH] Add PKCS#11 upgrade release note Change-Id: Ic0b70f331ebe2dddada247615d8c64b32300c4b4 --- ...-backend-performance-f3caacbe9e1ab535.yaml | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 releasenotes/notes/pkcs11-backend-performance-f3caacbe9e1ab535.yaml diff --git a/releasenotes/notes/pkcs11-backend-performance-f3caacbe9e1ab535.yaml b/releasenotes/notes/pkcs11-backend-performance-f3caacbe9e1ab535.yaml new file mode 100644 index 000000000..4008bcbca --- /dev/null +++ b/releasenotes/notes/pkcs11-backend-performance-f3caacbe9e1ab535.yaml @@ -0,0 +1,30 @@ +--- +prelude: > + This release includes significant improvements to the performance + of the PKCS#11 Cryptographic Plugin driver. These changes will require + a data migration of any existing data stored by previous versions + of the PKCS#11 backend. +issues: + - > + The service will encounter errors if you attempt to run this new release + using data stored by a previous version of the PKCS#11 Cryptographic Plugin + that has not yet been migrated for this release. The logged errors + will look like + + ``'P11CryptoPluginException: HSM returned response code: 0xc0L CKR_SIGNATURE_INVALID'`` + +upgrade: + - > + If you are upgrading from previous version of barbican that uses the + PKCS#11 Cryptographic Plugin driver, you will need to run the migration + script + + ``python barbican/cmd/pkcs11_migrate_kek_signatures.py`` + +critical: + - > + If you are upgrading from previous version of barbican that uses the + PKCS#11 Cryptographic Plugin driver, you will need to run the migration + script + + ``python barbican/cmd/pkcs11_migrate_kek_signatures.py``