"Fossies" - the Fresh Open Source Software Archive

Member "barbican-12.0.0/releasenotes/source/locale/en_GB/LC_MESSAGES/releasenotes.po" (14 Apr 2021, 25620 Bytes) of package /linux/misc/openstack/barbican-12.0.0.tar.gz:


As a special service "Fossies" has tried to format the requested source page into HTML format using (guessed) PO translation source code syntax highlighting (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 # Andi Chandler <andi@gowling.com>, 2017. #zanata
    2 # Andi Chandler <andi@gowling.com>, 2018. #zanata
    3 # Andi Chandler <andi@gowling.com>, 2019. #zanata
    4 # Andi Chandler <andi@gowling.com>, 2020. #zanata
    5 # Andi Chandler <andi@gowling.com>, 2021. #zanata
    6 msgid ""
    7 msgstr ""
    8 "Project-Id-Version: Barbican Release Notes\n"
    9 "Report-Msgid-Bugs-To: \n"
   10 "POT-Creation-Date: 2021-01-19 13:43+0000\n"
   11 "MIME-Version: 1.0\n"
   12 "Content-Type: text/plain; charset=UTF-8\n"
   13 "Content-Transfer-Encoding: 8bit\n"
   14 "PO-Revision-Date: 2021-01-29 03:00+0000\n"
   15 "Last-Translator: Andi Chandler <andi@gowling.com>\n"
   16 "Language-Team: English (United Kingdom)\n"
   17 "Language: en_GB\n"
   18 "X-Generator: Zanata 4.3.3\n"
   19 "Plural-Forms: nplurals=2; plural=(n != 1)\n"
   20 
   21 msgid ""
   22 "(For deployments overriding default policies) After upgrading, please review "
   23 "Barbican policy files and ensure that you port any rules tied to `order:put` "
   24 "are remapped to `orders:put`."
   25 msgstr ""
   26 "(For deployments overriding default policies) After upgrading, please review "
   27 "Barbican policy files and ensure that you port any rules tied to `order:put` "
   28 "are remapped to `orders:put`."
   29 
   30 msgid "1.0.0-5"
   31 msgstr "1.0.0-5"
   32 
   33 msgid "10.0.0"
   34 msgstr "10.0.0"
   35 
   36 msgid "10.0.0-5"
   37 msgstr "10.0.0-5"
   38 
   39 msgid "11.0.0"
   40 msgstr "11.0.0"
   41 
   42 msgid "11.0.0-24"
   43 msgstr "11.0.0-24"
   44 
   45 msgid "11.0.0-4"
   46 msgstr "11.0.0-4"
   47 
   48 msgid "2.0.0"
   49 msgstr "2.0.0"
   50 
   51 msgid "3.0.0"
   52 msgstr "3.0.0"
   53 
   54 msgid "4.0.0"
   55 msgstr "4.0.0"
   56 
   57 msgid "5.0.0"
   58 msgstr "5.0.0"
   59 
   60 msgid "6.0.0"
   61 msgstr "6.0.0"
   62 
   63 msgid "6.0.1-12"
   64 msgstr "6.0.1-12"
   65 
   66 msgid "7.0.0"
   67 msgstr "7.0.0"
   68 
   69 msgid "7.0.0-17"
   70 msgstr "7.0.0-17"
   71 
   72 msgid "8.0.0"
   73 msgstr "8.0.0"
   74 
   75 msgid "9.0.1-3"
   76 msgstr "9.0.1-3"
   77 
   78 msgid ""
   79 "Added new options to the PKCS#11 Cryptographic Plugin configuration to "
   80 "enable the use of different encryption and hmac mechanisms. Added support "
   81 "for `CKM_AES_CBC` encryption in the PKCS#11 Cryptographic Plugin."
   82 msgstr ""
   83 "Added new options to the PKCS#11 Cryptographic Plugin configuration to "
   84 "enable the use of different encryption and HMAC mechanisms. Added support "
   85 "for `CKM_AES_CBC` encryption in the PKCS#11 Cryptographic Plugin."
   86 
   87 msgid "Added new tool ``barbican-status upgrade check``."
   88 msgstr "Added new tool ``barbican-status upgrade check``."
   89 
   90 msgid ""
   91 "Added two new subcommands to `barbican-manage hsm` that can query the HSM to "
   92 "check if a MKEK or HMAC key with the given label already exists.  See "
   93 "`barbican-manage hsm check_mkek --help` and `barbican-manage hsm check_hmac "
   94 "--help` for details."
   95 msgstr ""
   96 "Added two new subcommands to `barbican-manage hsm` that can query the HSM to "
   97 "check if a MKEK or HMAC key with the given label already exists.  See "
   98 "`barbican-manage hsm check_mkek --help` and `barbican-manage hsm check_hmac "
   99 "--help` for details."
  100 
  101 msgid ""
  102 "Added two options for the PKCS#11 Crypto Plugin: `[p11_crypto_plugin]/"
  103 "token_serial_number` and `[p11_crypto_plugin]/token_label`.  Both are "
  104 "optional and can be used instead of `[p11_crypto_plugin]/slot_id` to "
  105 "identify the Token to be used by the PKCS#11 plugin.  When either one of the "
  106 "new options is defined the plugin will search all slots on the PKCS#11 "
  107 "device for a token that matches the given value.  `token_serial_number` has "
  108 "the highest precendence and other values will be ignored when this value is "
  109 "set.  If `token_serial_number` is not set, then `token_label` has the next "
  110 "highest precedence and `slot_id` will be ignored. `slot_id` will be used "
  111 "when neither one of the new options is set."
  112 msgstr ""
  113 "Added two options for the PKCS#11 Crypto Plugin: `[p11_crypto_plugin]/"
  114 "token_serial_number` and `[p11_crypto_plugin]/token_label`.  Both are "
  115 "optional and can be used instead of `[p11_crypto_plugin]/slot_id` to "
  116 "identify the Token to be used by the PKCS#11 plugin.  When either one of the "
  117 "new options is defined the plugin will search all slots on the PKCS#11 "
  118 "device for a token that matches the given value.  `token_serial_number` has "
  119 "the highest precedence and other values will be ignored when this value is "
  120 "set.  If `token_serial_number` is not set, then `token_label` has the next "
  121 "highest precedence and `slot_id` will be ignored. `slot_id` will be used "
  122 "when neither one of the new options is set."
  123 
  124 msgid "Barbican Release Notes"
  125 msgstr "Barbican Release Notes"
  126 
  127 msgid "Bug Fixes"
  128 msgstr "Bug Fixes"
  129 
  130 msgid ""
  131 "By default barbican checks only the algorithm and the bit_length when "
  132 "creating a new secret. The xts-mode cuts the key in half for aes, so for "
  133 "using aes-256 with xts, you have to use a 512 bit key, but barbican allows "
  134 "only a maximum of 256 bit. A check for the mode within the "
  135 "_is_algorithm_supported method of the class SimpleCryptoPlugin was added to "
  136 "allow 512 bit keys for aes-xts in this plugin."
  137 msgstr ""
  138 "By default Barbican checks only the algorithm and the bit_length when "
  139 "creating a new secret. The xts-mode cuts the key in half for AES, so for "
  140 "using AES-256 with xts, you have to use a 512 bit key, but barbican allows "
  141 "only a maximum of 256 bit. A check for the mode within the "
  142 "_is_algorithm_supported method of the class SimpleCryptoPlugin was added to "
  143 "allow 512 bit keys for AES-XTS in this plugin."
  144 
  145 msgid "CAs"
  146 msgstr "CAs"
  147 
  148 msgid "Certificate Orders"
  149 msgstr "Certificate Orders"
  150 
  151 msgid "Contents:"
  152 msgstr "Contents:"
  153 
  154 msgid "Critical Issues"
  155 msgstr "Critical Issues"
  156 
  157 msgid "Current Series Release Notes"
  158 msgstr "Current Series Release Notes"
  159 
  160 msgid ""
  161 "Default for auto_db_create has been changed to False (was True). This is a "
  162 "change compared to the previous behavior, but required to protect production "
  163 "deployments from performing upgrades without control. If you wish to keep "
  164 "the auto db creation/upgrade behavior, change this to True in your "
  165 "configuration."
  166 msgstr ""
  167 "Default for auto_db_create has been changed to False (was True). This is a "
  168 "change compared to the previous behaviour, but required to protect "
  169 "production deployments from performing upgrades without control. If you wish "
  170 "to keep the auto db creation/upgrade behaviour, change this to True in your "
  171 "configuration."
  172 
  173 msgid ""
  174 "Deprecated the `generate_iv` option name.  It has been renamed to "
  175 "`aes_gcm_generate_iv` to reflect the fact that it only applies to the "
  176 "CKM_AES_GCM mechanism."
  177 msgstr ""
  178 "Deprecated the `generate_iv` option name.  It has been renamed to "
  179 "`aes_gcm_generate_iv` to reflect the fact that it only applies to the "
  180 "CKM_AES_GCM mechanism."
  181 
  182 msgid ""
  183 "Deprecated the `p11_crypto_plugin:algoritm` option. Users should update "
  184 "their configuration to use `p11_crypto_plugin:encryption_mechanism` instead."
  185 msgstr ""
  186 "Deprecated the `p11_crypto_plugin:algoritm` option. Users should update "
  187 "their configuration to use `p11_crypto_plugin:encryption_mechanism` instead."
  188 
  189 msgid "Deprecation Notes"
  190 msgstr "Deprecation Notes"
  191 
  192 msgid "Fixed Story # 2007732: Migrations broken on MySQL 8.x."
  193 msgstr "Fixed Story # 2007732: Migrations broken on MySQL 8.x."
  194 
  195 msgid ""
  196 "Fixed Story #2004734:  Added a new option `always_set_cka_sensitive` to fix "
  197 "a regression that affected Safenet HSMs.  The option defaults to `True` as "
  198 "required by Safenet HSMs.  Other HSMs may require it be set to `False`."
  199 msgstr ""
  200 "Fixed Story #2004734:  Added a new option `always_set_cka_sensitive` to fix "
  201 "a regression that affected Safenet HSMs.  The option defaults to `True` as "
  202 "required by Safenet HSMs.  Other HSMs may require it be set to `False`."
  203 
  204 msgid ""
  205 "Fixed Story #2004734: Added a new option 'hmac_keywrap_mechanism' to make "
  206 "the mechanism used to calculate a HMAC from an wrapped PKEK configurable. "
  207 "This was introduced because of an problem with Utimaco HSMs which throw an "
  208 "'CKR_MECHANISM_INVALID' error, e.g. when a new PKEK is generated. For "
  209 "Utimaco HSMs, 'hmac_keywrap_mechanism' should be set to 'CKM_AES_MAC' in "
  210 "barbican.conf."
  211 msgstr ""
  212 "Fixed Story #2004734: Added a new option 'hmac_keywrap_mechanism' to make "
  213 "the mechanism used to calculate a HMAC from an wrapped PKEK configurable. "
  214 "This was introduced because of an problem with Utimaco HSMs which throw an "
  215 "'CKR_MECHANISM_INVALID' error, e.g. when a new PKEK is generated. For "
  216 "Utimaco HSMs, 'hmac_keywrap_mechanism' should be set to 'CKM_AES_MAC' in "
  217 "barbican.conf."
  218 
  219 msgid ""
  220 "Fixed Story #2006978:  An admin user now can delete other users secrets by "
  221 "adjust the policy file."
  222 msgstr ""
  223 "Fixed Story #2006978:  An admin user now can delete other users secrets by "
  224 "adjust the policy file."
  225 
  226 msgid ""
  227 "Fixed the response code for invalid subroutes for individual secrets.  The "
  228 "API was previously responding with the incorrect code \"406 - Method not "
  229 "allowed\", but now responds correctly with \"404 - Not Found\"."
  230 msgstr ""
  231 "Fixed the response code for invalid subroutes for individual secrets.  The "
  232 "API was previously responding with the incorrect code \"406 - Method not "
  233 "allowed\", but now responds correctly with \"404 - Not Found\"."
  234 
  235 msgid ""
  236 "If you are upgrading from previous version of barbican that uses the PKCS#11 "
  237 "Cryptographic Plugin driver, you will need to run the migration script"
  238 msgstr ""
  239 "If you are upgrading from previous version of barbican that uses the PKCS#11 "
  240 "Cryptographic Plugin driver, you will need to run the migration script"
  241 
  242 msgid ""
  243 "It is now possible for barbican-keystone-listener to listen on the same "
  244 "standard notification topic without interfering with other services by using "
  245 "the notification listener pools feature of oslo.messaging. To use it, set "
  246 "the new ``[keystone_notifications]pool_name`` option to some unique value "
  247 "(but the same for all instances of barbican-keystone-listener service). This "
  248 "feature is available only for those messaging transports of oslo.messaging "
  249 "that support it. At the moment those are rabbitmq and kafka. For more "
  250 "details see `oslo.messagind docs <https://docs.openstack.org/oslo.messaging/"
  251 "latest/reference/notification_listener.html>`_"
  252 msgstr ""
  253 "It is now possible for barbican-keystone-listener to listen on the same "
  254 "standard notification topic without interfering with other services by using "
  255 "the notification listener pools feature of oslo.messaging. To use it, set "
  256 "the new ``[keystone_notifications]pool_name`` option to some unique value "
  257 "(but the same for all instances of barbican-keystone-listener service). This "
  258 "feature is available only for those messaging transports of oslo.messaging "
  259 "that support it. At the moment those are RabbitMQ and Kafka. For more "
  260 "details see `oslo.messagind docs <https://docs.openstack.org/oslo.messaging/"
  261 "latest/reference/notification_listener.html>`_"
  262 
  263 msgid "Known Issues"
  264 msgstr "Known Issues"
  265 
  266 msgid "Liberty Series Release Notes"
  267 msgstr "Liberty Series Release Notes"
  268 
  269 msgid ""
  270 "Maintain the policy rules in code and add an oslo.policy CLI script in tox "
  271 "to generate policy sample file. The script can be called like \"oslopolicy-"
  272 "sample-generator --config-file=etc/oslo-config-generator/policy.conf\" and "
  273 "will generate a policy.yaml.sample file with the effective policy."
  274 msgstr ""
  275 "Maintain the policy rules in code and add an oslo.policy CLI script in tox "
  276 "to generate policy sample file. The script can be called like \"oslopolicy-"
  277 "sample-generator --config-file=etc/oslo-config-generator/policy.conf\" and "
  278 "will generate a policy.yaml.sample file with the effective policy."
  279 
  280 msgid "Mitaka Series Release Notes"
  281 msgstr "Mitaka Series Release Notes"
  282 
  283 msgid "New Features"
  284 msgstr "New Features"
  285 
  286 msgid ""
  287 "New feature to support multiple secret store plugin backends. This feature "
  288 "is not enabled by default. To use this feature, the relevant feature flag "
  289 "needs to be enabled and supporting configuration needs to be added in the "
  290 "service configuration. Once enabled, a project adminstrator will be able to "
  291 "specify one of the available secret store backends as a preferred secret "
  292 "store for their project secrets. This secret store preference applies only "
  293 "to new secrets (key material) created or stored within that project. "
  294 "Existing secrets are not impacted. See http://docs.openstack.org/developer/"
  295 "barbican/setup/plugin_backends.html for instructions on how to setup "
  296 "Barbican multiple backends, and the API documentation for further details."
  297 msgstr ""
  298 "New feature to support multiple secret store plugin backends. This feature "
  299 "is not enabled by default. To use this feature, the relevant feature flag "
  300 "needs to be enabled and supporting configuration needs to be added in the "
  301 "service configuration. Once enabled, a project administrator will be able to "
  302 "specify one of the available secret store backends as a preferred secret "
  303 "store for their project secrets. This secret store preference applies only "
  304 "to new secrets (key material) created or stored within that project. "
  305 "Existing secrets are not impacted. See http://docs.openstack.org/developer/"
  306 "barbican/setup/plugin_backends.html for instructions on how to setup "
  307 "Barbican multiple backends, and the API documentation for further details."
  308 
  309 msgid ""
  310 "New framework for ``barbican-status upgrade check`` command is added. This "
  311 "framework allows adding various checks which can be run before a Barbican "
  312 "upgrade to ensure if the upgrade can be performed safely."
  313 msgstr ""
  314 "New framework for ``barbican-status upgrade check`` command is added. This "
  315 "framework allows adding various checks which can be run before a Barbican "
  316 "upgrade to ensure if the upgrade can be performed safely."
  317 
  318 msgid "Newton Series Release Notes"
  319 msgstr "Newton Series Release Notes"
  320 
  321 msgid ""
  322 "Now within a single deployment, multiple secret store plugin backends can be "
  323 "configured and used. With this change, a project adminstrator can pre-define "
  324 "a preferred plugin backend for storing their secrets. New APIs are added to "
  325 "manage this project level secret store preference."
  326 msgstr ""
  327 "Now within a single deployment, multiple secret store plugin backends can be "
  328 "configured and used. With this change, a project administrator can pre-"
  329 "define a preferred plugin backend for storing their secrets. New APIs are "
  330 "added to manage this project level secret store preference."
  331 
  332 msgid "Ocata Series Release Notes"
  333 msgstr "Ocata Series Release Notes"
  334 
  335 msgid ""
  336 "Operator can now use new CLI tool ``barbican-status upgrade check`` to check "
  337 "if Barbican deployment can be safely upgraded from N-1 to N release."
  338 msgstr ""
  339 "Operator can now use new CLI tool ``barbican-status upgrade check`` to check "
  340 "if Barbican deployment can be safely upgraded from N-1 to N release."
  341 
  342 msgid "Other Notes"
  343 msgstr "Other Notes"
  344 
  345 msgid "Pike Series Release Notes"
  346 msgstr "Pike Series Release Notes"
  347 
  348 msgid ""
  349 "Port existing policy RuleDefault objects to the newer, more verbose "
  350 "DocumentedRuleDefaults."
  351 msgstr ""
  352 "Port existing policy RuleDefault objects to the newer, more verbose "
  353 "DocumentedRuleDefaults."
  354 
  355 msgid "Prelude"
  356 msgstr "Prelude"
  357 
  358 msgid ""
  359 "Python 2.7 support has been dropped. Last release of Barbican to support "
  360 "python 2.7 is OpenStack Train. The minimum version of Python now supported "
  361 "by Barbican is Python 3.6."
  362 msgstr ""
  363 "Python 2.7 support has been dropped. Last release of Barbican to support "
  364 "python 2.7 is OpenStack Train. The minimum version of Python now supported "
  365 "by Barbican is Python 3.6."
  366 
  367 msgid "Queens Series Release Notes"
  368 msgstr "Queens Series Release Notes"
  369 
  370 msgid ""
  371 "Remap the `order:put` to `orders:put` to align with language in the orders "
  372 "controller."
  373 msgstr ""
  374 "Remap the `order:put` to `orders:put` to align with language in the orders "
  375 "controller."
  376 
  377 msgid ""
  378 "Removed application/pkix media type because Barbican will not be using media "
  379 "types for format conversion."
  380 msgstr ""
  381 "Removed application/pkix media type because Barbican will not be using media "
  382 "types for format conversion."
  383 
  384 msgid "Rocky Series Release Notes"
  385 msgstr "Rocky Series Release Notes"
  386 
  387 msgid "Start using reno to manage release notes."
  388 msgstr "Start using reno to manage release notes."
  389 
  390 msgid "Stein Series Release Notes"
  391 msgstr "Stein Series Release Notes"
  392 
  393 msgid ""
  394 "The 'barbican-db-manage' script is deprecated.  Use the new 'barbican-"
  395 "manage' utility instead."
  396 msgstr ""
  397 "The 'barbican-db-manage' script is deprecated.  Use the new 'barbican-"
  398 "manage' utility instead."
  399 
  400 msgid ""
  401 "The 'barbican-manage' tool can be used to manage database schema changes as "
  402 "well as provision and rotate keys in the HSM backend."
  403 msgstr ""
  404 "The 'barbican-manage' tool can be used to manage database schema changes as "
  405 "well as provision and rotate keys in the HSM backend."
  406 
  407 msgid ""
  408 "The 'http_proxy_to_wsgi' middleware can be used to help barbican respond "
  409 "with the correct URL refs when it's put behind a TLS proxy (such as "
  410 "HAProxy). This middleware is disabled by default, but can be enabled via a "
  411 "configuration option in the oslo_middleware group."
  412 msgstr ""
  413 "The 'http_proxy_to_wsgi' middleware can be used to help Barbican respond "
  414 "with the correct URL refs when it's put behind a TLS proxy (such as "
  415 "HAProxy). This middleware is disabled by default, but can be enabled via a "
  416 "configuration option in the oslo_middleware group."
  417 
  418 msgid ""
  419 "The 'pkcs11-kek-rewrap' script is deprecated.  Use the new 'barbican-manage' "
  420 "utility instead."
  421 msgstr ""
  422 "The 'pkcs11-kek-rewrap' script is deprecated.  Use the new 'barbican-manage' "
  423 "utility instead."
  424 
  425 msgid ""
  426 "The 'pkcs11-key-generation' script is deprecated.  Use the new 'barbican-"
  427 "manage' utility instead."
  428 msgstr ""
  429 "The 'pkcs11-key-generation' script is deprecated.  Use the new 'barbican-"
  430 "manage' utility instead."
  431 
  432 msgid ""
  433 "The Metadata API requires an update to the Database Schema. Existing "
  434 "deployments that are being upgraded to Mitaka should use the 'barbican-"
  435 "manage' utility to update the schema."
  436 msgstr ""
  437 "The Metadata API requires an update to the Database Schema. Existing "
  438 "deployments that are being upgraded to Mitaka should use the 'barbican-"
  439 "manage' utility to update the schema."
  440 
  441 msgid ""
  442 "The Mitaka release includes a new API to add arbitrary user-defined metadata "
  443 "to Secrets."
  444 msgstr ""
  445 "The Mitaka release includes a new API to add arbitrary user-defined metadata "
  446 "to Secrets."
  447 
  448 msgid ""
  449 "The barbican-api-paste.ini configuration file for the paste pipeline was "
  450 "updated to add the http_proxy_to_wsgi middleware."
  451 msgstr ""
  452 "The barbican-api-paste.ini configuration file for the paste pipeline was "
  453 "updated to add the http_proxy_to_wsgi middleware."
  454 
  455 msgid ""
  456 "The hsm subcommand for the barbican-manage command line tool no longer "
  457 "requires any parameters at run time.  If any value used by the PKCS#11 value "
  458 "is needed it will be taken from /etc/barbican/barbican.conf. You may "
  459 "continue to specify any values on the command line, and those will take "
  460 "precedence over the values specified in barbican.conf, so any existing "
  461 "scripts that use barbican-manage should continue to work as expected."
  462 msgstr ""
  463 "The hsm subcommand for the barbican-manage command line tool no longer "
  464 "requires any parameters at run time.  If any value used by the PKCS#11 value "
  465 "is needed it will be taken from /etc/barbican/barbican.conf. You may "
  466 "continue to specify any values on the command line, and those will take "
  467 "precedence over the values specified in barbican.conf, so any existing "
  468 "scripts that use barbican-manage should continue to work as expected."
  469 
  470 msgid ""
  471 "The service will encounter errors if you attempt to run this new release "
  472 "using data stored by a previous version of the PKCS#11 Cryptographic Plugin "
  473 "that has not yet been migrated for this release.  The logged errors will "
  474 "look like"
  475 msgstr ""
  476 "The service will encounter errors if you attempt to run this new release "
  477 "using data stored by a previous version of the PKCS#11 Cryptographic Plugin "
  478 "that has not yet been migrated for this release.  The logged errors will "
  479 "look like"
  480 
  481 msgid "This release adds http_proxy_to_wsgi middleware to the pipeline."
  482 msgstr "This release adds http_proxy_to_wsgi middleware to the pipeline."
  483 
  484 msgid ""
  485 "This release includes a new command line utility 'barbican-manage' that "
  486 "consolidates and supersedes the separate HSM and database management scripts."
  487 msgstr ""
  488 "This release includes a new command line utility 'barbican-manage' that "
  489 "consolidates and supersedes the separate HSM and database management scripts."
  490 
  491 msgid ""
  492 "This release includes significant improvements to the performance of the "
  493 "PKCS#11 Cryptographic Plugin driver.  These changes will require a data "
  494 "migration of any existing data stored by previous versions of the PKCS#11 "
  495 "backend."
  496 msgstr ""
  497 "This release includes significant improvements to the performance of the "
  498 "PKCS#11 Cryptographic Plugin driver.  These changes will require a data "
  499 "migration of any existing data stored by previous versions of the PKCS#11 "
  500 "backend."
  501 
  502 msgid ""
  503 "This release notify that we will remove Certificate Orders and CAs from API."
  504 msgstr ""
  505 "This release notify that we will remove Certificate Orders and CAs from the "
  506 "API."
  507 
  508 msgid "Train Series Release Notes"
  509 msgstr "Train Series Release Notes"
  510 
  511 msgid "Upgrade Notes"
  512 msgstr "Upgrade Notes"
  513 
  514 msgid "Ussuri Series Release Notes"
  515 msgstr "Ussuri Series Release Notes"
  516 
  517 msgid "Victoria Series Release Notes"
  518 msgstr "Victoria Series Release Notes"
  519 
  520 msgid ""
  521 "Why are we deprecating Certificate Issuance? There are a few reasons that "
  522 "were considered for this decision.  First, there does not seem to be a lot "
  523 "of interest in the community to fully develop the Certificate Authority "
  524 "integration with Barbican.  We have a few outstanding blueprints that are "
  525 "needed to make Certificate Issuance fully functional, but so far no one has "
  526 "committed to getting the work done.  Additionally, we've had very little buy-"
  527 "in from public Certificate Authorities.  Both Symantec and Digicert were "
  528 "interested in integration in the past, but that interest didn't materialize "
  529 "into robust CA plugins like we hoped it would. Secondly, there have been new "
  530 "developments in the space of Certificate Authorities since we started "
  531 "Barbican.  The most significant of these was the launch of the Let's Encrypt "
  532 "public CA along with the definition of the ACME protocol for certificate "
  533 "issuance.  We believe that future certificate authority services would do "
  534 "good to implement the ACME standard, which is quite different than the API "
  535 "the Barbican team had developed. Lastly, deprecating Certificate Issuance "
  536 "within Barbican will simplify both the architecture and deployment of "
  537 "Barbican.  This will allow us to focus on the features that Barbican does "
  538 "well -- the secure storage of secret material."
  539 msgstr ""
  540 "Why are we deprecating Certificate Issuance? There are a few reasons that "
  541 "were considered for this decision.  First, there does not seem to be a lot "
  542 "of interest in the community to fully develop the Certificate Authority "
  543 "integration with Barbican.  We have a few outstanding blueprints that are "
  544 "needed to make Certificate Issuance fully functional, but so far no one has "
  545 "committed to getting the work done.  Additionally, we've had very little buy-"
  546 "in from public Certificate Authorities.  Both Symantec and Digicert were "
  547 "interested in integration in the past, but that interest didn't materialise "
  548 "into robust CA plugins like we hoped it would. Secondly, there have been new "
  549 "developments in the space of Certificate Authorities since we started "
  550 "Barbican.  The most significant of these was the launch of the Let's Encrypt "
  551 "public CA along with the definition of the ACME protocol for certificate "
  552 "issuance.  We believe that future certificate authority services would do "
  553 "good to implement the ACME standard, which is quite different than the API "
  554 "the Barbican team had developed. Lastly, deprecating Certificate Issuance "
  555 "within Barbican will simplify both the architecture and deployment of "
  556 "Barbican.  This will allow us to focus on the features that Barbican does "
  557 "well -- the secure storage of secret material."
  558 
  559 msgid ""
  560 "Will Barbican still be able to store Certificates? Yes, absolutely!  The "
  561 "only thing we're deprecating is the plugin interface that talks to "
  562 "Certificate Authorities and associated APIs. While you will not be able to "
  563 "use Barbican to issue a new certificate, you will always be able to securely "
  564 "store any certificates in Barbican, including those issued by public CAs or "
  565 "internal CAs."
  566 msgstr ""
  567 "Will Barbican still be able to store Certificates? Yes, absolutely!  The "
  568 "only thing we're deprecating is the plugin interface that talks to "
  569 "Certificate Authorities and associated APIs. While you will not be able to "
  570 "use Barbican to issue a new certificate, you will always be able to securely "
  571 "store any certificates in Barbican, including those issued by public CAs or "
  572 "internal CAs."
  573 
  574 msgid ""
  575 "``'P11CryptoPluginException: HSM returned response code: 0xc0L "
  576 "CKR_SIGNATURE_INVALID'``"
  577 msgstr ""
  578 "``'P11CryptoPluginException: HSM returned response code: 0xc0L "
  579 "CKR_SIGNATURE_INVALID'``"
  580 
  581 msgid "``python barbican/cmd/pkcs11_migrate_kek_signatures.py``"
  582 msgstr "``python barbican/cmd/pkcs11_migrate_kek_signatures.py``"
  583 
  584 msgid ""
  585 "default value of 'control_exchange' in 'barbican.conf' has been changed to "
  586 "'keystone'."
  587 msgstr ""
  588 "default value of 'control_exchange' in 'barbican.conf' has been changed to "
  589 "'keystone'."
  590 
  591 msgid ""
  592 "oslo-config-generator is now used to generate a barbican.conf.sample file"
  593 msgstr ""
  594 "oslo-config-generator is now used to generate a barbican.conf.sample file"