This tool provides shell access to Keystok from Linux, OS X and other UNIX-like operating systems. It can be used e.g. inside Docker containers to access Keystok keys.
Installation
To install the Python client, run this in your shell:
pip install keystok
You can do it inside a virtualenv if needed.
Usage
Run “keystok -h” for help on the available commands and options.
Specifying the access token
To configure the access token, first run this in the shell:
export KEYSTOK_ACCESS_TOKEN=<access token from keystok.com>
Alternatively you can also specify the token in each command using:
keystok -a <token>
In Dockerfiles you might want to use the convenient ENV directive:
ENV KEYSTOK_ACCESS_TOKEN <access token from keystok.com>
Or to keep it out of the Dockerfile, specify it with docker run instead:
docker run -e KEYSTOK_ACCESS_TOKEN=<access token>
It’s also possible to place the access token in one of these files:
./.keystok/access_token (under current directory) ~/.keystok/access_token (under home directory)
Commands
To list all keys associated with the application:
keystok ls
To retrieve a key and output it into stdout:
keystok get <keyid>
To automatically retrieve ssh keys and generate a ssh configuration:
keystok [-f] sshautoconfig (the -f option will force-overwrite any existing SSH keys)
1 maintainer
Metadata
1 maintainer
Release files for keystok 0.1.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 | |
|---|---|---|---|---|
| keystok-0.1.6.tar.gz | 5.6 kB | Without provenance | Details |
Release files / keystok-0.1.6.tar.gz
| Download URL | keystok-0.1.6.tar.gz |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ccdf099d7b28625c9302c46d4fdb0690dc77bfe5dfda3c3c3df34ece552759a
|
|
BLAKE2b-256 checksum How to use checksums |
10525c703e4c0a0ddf7a162af0eca145e4f523e6dbb77ddc943f502e266d3dd1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for keystok 0.1.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.
