knot-keystore
A tool to safely backup the knot kasp-db directory.
overview
usage: knot-keystore [-h] [--socket SOCKET]
[--plugins [{local,azure} [{local,azure} ...]]]
[--retrieve] [--config-file CONFIG_FILE] [-v]
optional arguments:
-h, --help show this help message and exit
--socket SOCKET, -s SOCKET
path to knotc control socket
--plugins [{local,azure} [{local,azure} ...]], -p [{local,azure} [{local,azure} ...]]
select archival plugins
--retrieve, -r retrieve archive
--config-file CONFIG_FILE, -c CONFIG_FILE
path to a configuration file
-v increase output verbosity
- tries to find the kasp-db path by reading
knotdconfig over the control socket. - plugins:
- create an xz-compressed archive and put it somewhere, safely encrypted (default)
- retrieve and decrypt the stored archive, ready to restore to the kasp-db
directory (with
--retrieve)
available plugins
local: create an encrypted copy of the archive and write it to disk along with the encryption key. Mostly useful for testing.azure: write the archive to an Azure storage blob, first encrypting it using "client-side-encryption" with a KEK stored in Azure Key Vault.
Metadata
Release files for knot-keystore 0.1.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 |
|---|---|---|---|---|
| knot_keystore-0.1.0.tar.gz | 9.2 kB | Without provenance | Details for knot_keystore-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| knot_keystore-0.1.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for knot_keystore-0.1.0-py2.py3-none-any.whl |
Total release size: 23.6 kB
Release files / knot_keystore-0.1.0.tar.gz
| Download URL | knot_keystore-0.1.0.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36de06cbb7d85246c7745085a0ef823abd5a6aa111accc67274eaddd871a2f69
|
|
BLAKE2b-256 checksum How to use checksums |
40c61ad64a3689f9c269ef8623a1c97435d9ae8defe8ae4833a26dfffd7b5921
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.9.1 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.12
|
Release files / knot_keystore-0.1.0-py2.py3-none-any.whl
| Download URL | knot_keystore-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 14.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
15b1d6131ead4b8968f9ea85ad7ec0e3294cf398196abb344349022001d2170c
|
|
BLAKE2b-256 checksum How to use checksums |
9c9fc89c4430d29d1fe1b44cb80fde0ca82a669af0dcd809f8a83654387811c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.9.1 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.2 CPython/2.7.12
|
Security for knot-keystore 0.1.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.
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.