openstack
/
deb-barbican
Code Issues Proposed changes
RETIRED, further work has moved to Debian project infrastructure
1,581 Commits 6 Branches 117 Tags 5 MiB
Go to file
Juan Antonio Osorio Robles a488cdd53d service_enabled instead of environment variable for dogtag 
This change also adds the dogtag installation functions into the
contrib/devstack/lib/barbican scripts, and enables the installation of
dogtag in the extras.d script making the calling of the dogtag
installation from the functional test pre-hook script not necessary.

Depends-on: I749539f387f163e829fdc8390b6bd16cf23c663b
Change-Id: I60ccfaaa43aa4aa68e99affb9837ecab48c36759
 		2015-06-10 13:18:59 +03:00
barbican Merge "Adding a new script to generate mkek and hmac" 2015-06-05 00:07:58 +00:00
bin Merge "Adding a new script to generate mkek and hmac" 2015-06-05 00:07:58 +00:00
contrib/devstack service_enabled instead of environment variable for dogtag 2015-06-10 13:18:59 +03:00
doc/source Adding documentation for ACLs operations. 2015-06-02 09:50:15 -07:00
docs Remove deprecated references to admin endpoint. 2015-05-04 15:12:12 -05:00
etc Removed per ACL operations and added support for PUT method. 2015-06-02 10:12:12 -07:00
functionaltests service_enabled instead of environment variable for dogtag 2015-06-10 13:18:59 +03:00
rpmbuild Adding keystone notification listener support 2014-10-07 16:09:09 -07:00
.coveragerc Add I18n-related unit tests (Part 3) 2015-01-05 16:41:08 -06:00
.gitignore hide the eggs 2015-03-11 18:23:00 +00:00
.gitreview Update .gitreview file for new repo name 2014-05-23 18:14:46 -04:00
.mailmap Add .mailmap file 2013-12-02 11:23:23 -05:00
.testr.conf Modifying testr conf to suppress output 2014-09-13 15:12:58 -05:00
HACKING.rst Deduplicate HACKING.rst with docs.openstack.org/developer/hacking/ 2014-09-24 14:35:44 -07:00
LICENSE Merge of previous project work into this project 2013-04-01 18:26:03 -05:00
MANIFEST.in Removed README.rst in favor of README.md 2013-11-15 13:31:22 -06:00
README.md Update README file 2015-03-17 01:50:12 -05:00
apiary.apib Add missing \n at the end of file 2014-10-09 22:11:23 +02:00
babel.cfg Merge of previous project work into this project 2013-04-01 18:26:03 -05:00
bandit.yaml Add Bandit security static analysis checking via tox 2015-04-08 20:24:38 -04:00
openstack-common.conf Add retry periodic task and worker-client logic 2015-03-20 16:51:09 -05:00
pylintrc Merge of previous project work into this project 2013-04-01 18:26:03 -05:00
requirements.txt Updated from global requirements 2015-06-03 17:41:49 +00:00
setup.cfg Fix snakeoil_ca plugin 2015-05-08 18:34:38 +02:00
setup.py Update to the latest global requirements versions 2014-10-06 10:53:48 -05:00
test-requirements-bandit.txt Add Bandit security static analysis checking via tox 2015-04-08 20:24:38 -04:00
test-requirements.txt Updated from global requirements 2015-06-04 20:06:21 +00:00
tox.ini Add Bandit security static analysis checking via tox 2015-04-08 20:24:38 -04:00

README.md

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, 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, or you can send an email to the OpenStack General mailing list at openstack@lists.openstack.org with the prefix [barbican] in the subject.

To file a bug, use our bug tracker on Launchpad.

For development questions or discussion, hop on the OpenStack-dev mailing list at openstack-dev@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 - 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 Getting Started wiki page 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

  1. Provide a central secret-store capable of distributing secret / keying material to all types of deployments including ephemeral Cloud instances.
  2. Support reasonable compliance regimes through reporting and auditability.
  3. Application adoption costs should be minimal or non-existent.
  4. Build a community and ecosystem by being open-source and extensible.
  5. Improve security through sane defaults and centralized management of policies for all secrets.
  6. Out of band communication mechanism to notify and protect sensitive assets.