Takara
Takara is a secure secrets store. Takara differs from other secret stores in that it supports progressive usage. Secret stores need to be easy to use and easy to start with, but able to scale from easy local security all the way up to enterprise and military level security. If someone starts with something simple, it is optimal if it can scale all the way up.
Simple Usage Tutorial
Getting started with Takara is easy, it has a lot of options but you don’t need to know them! In fact you only need to know that takara stores encrypted data in a hierarchy, so data has a location, just like a file on a filesystem.
Install
We will just need to install the basic takara for this to work:
pip install takara
Create a Crypt Store
Takara stores encrypted data in units. This allows you to have separate units that store separate data, these unit can even be used to store data in different storage systems with different access systems.
But we don’t need to worry about that now! We just need to make our first unit! If you don’t tell it what to name the unit, then the unit will default to being called main. Lets make the main unit now:
takara create
This will create a secure store that is password protected. The command will prompt you for the password that you wish to use to secure the secrets.
Set a Value
Now that we have a unit set up we can set a value inside it. Just tell takara to chose a path for the unit to be stored and the data to be stored in said unit.
takara set -p my/secret -s 'The speed of an unladen swallow...'
Done! Now the encrypted secret is secure inside of takara.
Get the Value
Getting the value out is just as easy:
takara get -p my/secret
Now the plain text of the secret is presented back!
Metadata
Release files for takara 1.2
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 |
|---|---|---|---|---|
| takara-1.2.tar.gz | 10.8 kB | Without provenance | Details for takara-1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| takara-1.2-py3-none-any.whl | Python 3 | none | any | Details for takara-1.2-py3-none-any.whl |
Total release size: 26.5 kB
Release files / takara-1.2.tar.gz
| Download URL | takara-1.2.tar.gz |
|---|---|
| Size | 10.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
588b206acbeeb45cc2b544799f8130744cfe06404e568d5d5d2a603a4af6890d
|
|
BLAKE2b-256 checksum How to use checksums |
259a9bf5179edc955d2b3f24f0f2f8dfcced94dd63cecfb5aad9ed3b77499783
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Release files / takara-1.2-py3-none-any.whl
| Download URL | takara-1.2-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
661154b35e042d75951213d3f896b658693a77414b88d40ac1dadc4fff0ac6a8
|
|
BLAKE2b-256 checksum How to use checksums |
531e0dcbfea5e713c9c4731d51afb14e12627586009bd02baf4cdab1e6c1c5dc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/2.0.0 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.3 requests-toolbelt/0.9.1 tqdm/4.45.0 CPython/3.8.2
|
Security for takara 1.2
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.