vaultlocker
Utility to store and retrieve dm-crypt keys in Hashicorp Vault.
Vault provides a nice way to manage secrets within complex software deployments.
vaultlocker provides a way to store and retrieve dm-crypt encryption keys in Vault, automatically retrieving keys and opening LUKS dm-crypt devices on boot.
vaultlocker is configured using /etc/vaultlocker/vaultlocker.conf:
[vault] url = https://vault.internal:8200 approle = 4a1b84d2-7bb2-4c07-9804-04d1683ac925 backend = secret
vaultlocker defaults to using a backend with the name secret.
A block device can be encrypted and its key stored in vault:
sudo vaultlocker encrypt /dev/sdd1
This will automatically create a new systemd unit which will automatically retrieve the key and open the LUKS/dm-crypt device on boot.
Unless a UUID is provided (using the optional –uuid flag) vaultlocker will generate a UUID to label and identify the block device during subsequent operations.
A block device can also be opened from the command line using its UUID (hint - the block device or partition will be labelled with the UUID):
sudo vaultlocker decrypt f65b9e66-8f0c-4cae-b6f5-6ec85ea134f2
Authentication to Vault is done using an AppRole with a secret_id; its assumed that a CIDR based ACL is in use to only allow permitted systems within the Data Center to login and retrieve secrets from Vault.
Free software: Apache license
Documentation: https://docs.openstack.org/vaultlocker/latest
Source: https://git.openstack.org/cgit/openstack/vaultlocker
Metadata
Release files for vaultlocker 1.0.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| vaultlocker-1.0.6.tar.gz | 26.3 kB | Without provenance | Details for vaultlocker-1.0.6.tar.gz |
Release files / vaultlocker-1.0.6.tar.gz
| Download URL | vaultlocker-1.0.6.tar.gz |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
20ba6dc3df6d300a623235a80645fac0efe57bc8d8bc3e1c49053711e167ff60
|
|
BLAKE2b-256 checksum How to use checksums |
54e8cc0b79a653be556e5a7881abe263cb31d1d0378240dac4b59bc643f679db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.4.2 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.8.2
|
Security for vaultlocker 1.0.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.