601f5ec733
The PKCS#11 standard does not make any guarantees about
slot numbering, so the slot ID alone should not be used
to identify a token. Instead, the token's Serial Number
or Label should be used to ensure the correct token
is being used.
This patch adds two new config options to the p11_crypto
plugin: token_serial_number and token_label.
These new options allow for more flexibility in configuring
the PKCS#11 module. The config may include either the token's
serial number or its label.
Serial numbers should be unique, so they take higher precedence.
Some devices allow tokens to have the same label, so this patch
ensures that only one token with the specified label is present.
If both serial number and label are given, only the serial number
will be checked and an error will be raised if it is not found.
slot_id continues to work as expected, although its use is discouraged
and may be deprecated in a future patch. If the conf contains
only the slot_id, it will be used. If the serial number or
label are also provided, the new logic will ignore the slot_id
and search for the serial number or label instead.
Change-Id: I115cf1a7006a6c85f37c5e50ded13134a3dfd1a3
(cherry picked from commit
|
||
---|---|---|
api-guide/source | ||
barbican | ||
bin | ||
devstack | ||
doc | ||
etc | ||
functionaltests | ||
playbooks/legacy | ||
releasenotes | ||
.coveragerc | ||
.gitignore | ||
.gitreview | ||
.mailmap | ||
.stestr.conf | ||
.zuul.yaml | ||
HACKING.rst | ||
LICENSE | ||
README.rst | ||
apiary.apib | ||
babel.cfg | ||
bindep.txt | ||
lower-constraints.txt | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini |
README.rst
Team and repository tags
Barbican
Barbican is a REST API designed for the secure storage, provisioning and management of secrets. It is aimed at being useful for all environments, including large ephemeral Clouds.
Barbican is an OpenStack project developed by the Barbican Project Team with support from Rackspace Hosting <http://www.rackspace.com/>_, EMC, Ericsson, Johns Hopkins University, HP, Red Hat, Cisco Systems, and many more.
The full documentation can be found on the Barbican Developer Documentation Site.
If you have a technical question, you can ask it at Ask OpenStack with the barbican tag.
To file a bug, use our bug tracker on OpenStack Storyboard.
Release notes for the project can be found at https://docs.openstack.org/releasenotes/barbican.
For development questions or discussion, use the OpenStack-discuss mailing list at openstack-discuss@lists.openstack.org and let us know what you think, just add [barbican] to the subject. You can also join our IRC channel #openstack-barbican on Freenode.
Barbican began as part of a set of applications that make up the CloudKeep ecosystem. The other systems are:
- Postern <https://github.com/cloudkeep/postern>_ - Go based agent that provides access to secrets from the Barbican API.
- Palisade - AngularJS based web ui for the Barbican API.
- Python-barbicanclient -A convenient Python-based library to interact with the Barbican API.
Getting Started
Please visit our Users, Developers and Operators documentation for details.
Why Should You Use Barbican?
The current state of key management is atrocious. While Windows does have some decent options through the use of the Data Protection API (DPAPI) and Active Directory, Linux lacks a cohesive story around how to manage keys for application use.
Barbican was designed to solve this problem. The system was motivated by internal Rackspace needs, requirements from OpenStack and a realization that the current state of the art could use some help.
Barbican will handle many types of secrets, including:
- Symmetric Keys - Used to perform reversible encryption of data at rest, typically using the AES algorithm set. This type of key is required to enable features like encrypted Swift containers and Cinder volumes, encrypted Cloud Backups, etc.
- Asymmetric Keys - Asymmetric key pairs (sometimes referred to as public / private keys) are used in many scenarios where communication between untrusted parties is desired. The most common case is with SSL/TLS certificates, but also is used in solutions like SSH keys, S/MIME (mail) encryption and digital signatures.
- Raw Secrets - Barbican stores secrets as a base64 encoded block of data (encrypted, naturally). Clients can use the API to store any secrets in any format they desire. The Postern agent is capable of presenting these secrets in various formats to ease integration.
For the symmetric and asymmetric key types, Barbican supports full life cycle management including provisioning, expiration, reporting, etc. A plugin system allows for multiple certificate authority support (including public and private CAs).
Design Goals
- Provide a central secret-store capable of distributing secret / keying material to all types of deployments including ephemeral Cloud instances.
- Support reasonable compliance regimes through reporting and auditability.
- Application adoption costs should be minimal or non-existent.
- Build a community and ecosystem by being open-source and extensible.
- Improve security through sane defaults and centralized management of policies for all secrets.
- Provide an out of band communication mechanism to notify and protect sensitive assets.