Keylocker CLI (YAML Edition)
A command-line interface (CLI) tool and Python library for managing secrets directly within YAML configuration files. Allows encrypting individual values using the !SEC tag and loading values from environment variables using the !ENV tag.
Encryption Key
Keylocker uses a Fernet key for encryption and decryption. The key is obtained in the following order of priority:
KEYLOCKER_SECRET_KEYEnvironment Variable: If this environment variable is set, its value is used directly as the Fernet key (it should be a valid base64 encoded key).storage.keyFile: If the environment variable is not set, Keylocker attempts to read the key from thestorage.keyfile in the current directory by default.
Use the keylocker init command to generate a storage.key file if you prefer file-based key storage. Note that if KEYLOCKER_SECRET_KEY is set, it will always take precedence over the file for encryption/decryption operations.
keylocker init creates storage.key readable by its owner only (mode 0600 on Linux/macOS). Never commit it or bake it into container images: add storage.key to both .gitignore and .dockerignore, and prefer KEYLOCKER_SECRET_KEY injected at runtime in CI and containers.
Installation
You can install the package using pip:
pip install keylocker
The package is available on PyPI: https://pypi.org/project/keylocker/
Runtime dependencies are declared in pyproject.toml and installed automatically
by pip. Pipfile and both requirements files use the same supported ranges;
Pipfile.lock records exact versions for reproducible development and CI.
Tests check these declarations for drift, and CI smoke-tests the built wheel
in a fresh virtualenv without Pipenv or an editable source install.
Example YAML file (config.yaml):
# config.yaml
database:
host: db.example.com
username: user
# Encrypted password using 'keylocker encrypt'
password: !SEC gAAAAABh...[rest of encrypted data]...
api:
endpoint: [https://api.example.com](https://api.example.com)
# Load key from the API_KEY environment variable
key: !ENV API_KEY
deployment:
region: us-east-1
# Another secret
ssh_key_pass: !SEC gAAAAABh...[another encrypted data]...
CLI Usage:
-
Initialization (create key file):
- Generates the
storage.keyfile (if it doesn't exist). This file is used only if theKEYLOCKER_SECRET_KEYenvironment variable is not set.
keylocker init [--force]
- Generates the
-
Encrypt value for YAML:
- Encrypts a string using the available key (Environment Variable or Key File) and prints the
!SECtag to stdout for you to copy into your YAML file. Hints and diagnostics go to stderr. - Without an argument the secret is read from stdin, or from a hidden prompt (entered twice) when run in a terminal. Avoid passing the secret as an argument: it ends up in shell history and is visible in the process list.
keylocker encrypt # Secret to encrypt: # Repeat secret: # Add the following line to your YAML file: # !SEC gAAAAABh...[encrypted data]... # Non-interactive (one trailing newline is stripped): printf '%s' "$DB_PASSWORD" | keylocker encrypt
- Encrypts a string using the available key (Environment Variable or Key File) and prints the
-
View decrypted YAML:
- Loads the specified YAML file, resolves
!ENVvariables, decrypts!SECvalues using the available key (Environment Variable or Key File), and prints the resulting YAML to standard output. Only YAML is written to stdout, so it can be piped intoyq. If any!SECvalue cannot be decrypted, nothing is printed and the command exits with code 1.
# Set environment variables if your YAML uses !ENV export API_KEY="your_actual_api_key" keylocker view config.yaml # Example output (values resolved/decrypted): # database: # host: db.example.com # username: user # password: my_secret_value # api: # endpoint: [https://api.example.com](https://api.example.com) # key: your_actual_api_key # deployment: # region: us-east-1 # ssh_key_pass: decrypted_pass
(Note: An
editcommand might be added in the future for interactive editing) - Loads the specified YAML file, resolves
Usage in Python Code:
import os
from keylocker import load_yaml_secrets, DecryptionError
# Set environment variables if your YAML uses !ENV
os.environ['API_KEY'] = 'your_actual_api_key_for_python'
# Set KEYLOCKER_SECRET_KEY if using env var for the encryption key
# os.environ['KEYLOCKER_SECRET_KEY'] = 'your_base64_encoded_fernet_key'
config_file = 'config.yaml'
# The key_file parameter acts as a fallback if KEYLOCKER_SECRET_KEY is not set
key_file_path = 'storage.key'
try:
# Load, resolve !ENV, and decrypt !SEC automatically
secrets = load_yaml_secrets(config_file, key_file_path)
if secrets:
db_password = secrets.get('database', {}).get('password')
api_key = secrets.get('api', {}).get('key')
print(f"Database Password (from Python): {db_password}")
print(f"API Key (from Python): {api_key}")
except DecryptionError as e:
# Raised when a !SEC value cannot be decrypted (no key, wrong key, corrupted value).
# Never fall back to a placeholder value: fail closed.
raise SystemExit(f"Cannot load secrets: {e}")
Writing YAML with keylocker_dumper() raises EncryptionError if a SecureString cannot be encrypted, so a secret is never written out in plaintext. Both exceptions inherit from KeylockerError.
Usage in Bash:
To extract specific values from the resolved/decrypted YAML for use in scripts.
#!/bin/bash
# Set environment variables if your YAML uses !ENV
export API_KEY="your_bash_api_key"
# Set KEYLOCKER_SECRET_KEY if using env var for the encryption key
# export KEYLOCKER_SECRET_KEY='your_base64_encoded_fernet_key'
# Get the decrypted YAML content
CONFIG_YAML=$(keylocker view config.yaml)
# Check if the command executed successfully
if [ $? -ne 0 ]; then
echo "Error executing keylocker view"
exit 1
fi
# Example extraction using yq (requires yq installation)
# DB_PASS=$(echo "$CONFIG_YAML" | yq e '.database.password' -)
# API_KEY_FROM_YAML=$(echo "$CONFIG_YAML" | yq e '.api.key' -)
# Example extraction using grep/awk (less robust)
DB_PASS=$(echo "$CONFIG_YAML" | grep -A 1 'database:' | grep 'password:' | awk '{print $2}')
API_KEY_FROM_YAML=$(echo "$CONFIG_YAML" | grep -A 1 'api:' | grep 'key:' | awk '{print $2}')
echo "Extracted DB Password (from Bash): $DB_PASS"
echo "Extracted API Key (from Bash): $API_KEY_FROM_YAML"
# Further use of variables in your script
# e.g., ./deploy_script.sh --db-password "$DB_PASS" --api-key "$API_KEY_FROM_YAML"
Source Code:
Metadata
Release files for keylocker 0.5.0
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 |
|---|---|---|---|---|
| keylocker-0.5.0.tar.gz | 8.1 kB | With provenance | Details for keylocker-0.5.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| keylocker-0.5.0-py3-none-any.whl | Python 3 | none | any | Details for keylocker-0.5.0-py3-none-any.whl |
Total release size: 17.2 kB
Release files / keylocker-0.5.0.tar.gz
| Download URL | keylocker-0.5.0.tar.gz |
|---|---|
| Size | 8.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ce8f7bab80abae10ed32739437890e585dac4e7132cf3743185f2d9324a94b6e
|
|
BLAKE2b-256 checksum How to use checksums |
19e2fb368a320781292cfb282176eaa363ac60846767349b043d09bc13213bbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logRelease files / keylocker-0.5.0-py3-none-any.whl
| Download URL | keylocker-0.5.0-py3-none-any.whl |
|---|---|
| Size | 9.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7317036cc9fb57c3f8cd1ac37b2f1c7b978ac1422de6c13c7631aa9e004af4ab
|
|
BLAKE2b-256 checksum How to use checksums |
654f132d9df619274124f1a57630e37657b3953d9020a82efae8ca8e3d69a695
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logSecurity for keylocker 0.5.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for keylocker-0.5.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 31, 2026.
Transparency logA 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.