----------------------------------------
THIS IS AN EXPERIMENT. DO NOT USE IN PRODUCTION.
================================================
Prerequisites
=============
Python 3.4+.
Install
=======
You can install straight from `pip`.
pip install keystore
Before using it for the first time, you will need to setup a `~/.keystorerc` in
your home directory.
{
"keystore": "~/Dropbox/keystore",
"files": [
"~/.ssh",
"~/.gnupg/gpg-agent.conf",
"~/.gnupg/gpg.conf",
"~/.gnupg/private-keys-v1.d",
"~/.gnupg/pubring.gpg",
"~/.gnupg/secring.gpg",
"~/.gnupg/trustdb.gpg",
],
"verbose": true
}
Example usage
=============
**Saving keys:**
$ keystore-save
Inspecting ~/.ssh:
Adding /Users/spaxe/.ssh/id_rsa ...
Adding /Users/spaxe/.ssh/id_rsa.pub ...
Adding /Users/spaxe/.ssh/known_hosts ...
Added 3 key(s) to keystore.
This passphrase is used to decrypt your keystore. Please remember it.
Please enter a passphrase:
Please verify your passphrase:
Passphrase accepted. Encrypting ...
Keyring successfully created:
AwGd2MtDWRkOFdyJoRZTdFApvKnoBQ2PXsqqE
[...]
**Loading keys:**
$ keystore-load
Located encrypted keystore at ~/Dropbox/keystore:
Please enter the passphrase:
Keyring decrypted successfully.
File /Users/spaxe/.ssh/id_rsa exists. Are you sure you want to overwrite? (y)/n:
Writing key to /Users/spaxe/.ssh/id_rsa ...
File /Users/spaxe/.ssh/id_rsa.pub exists. Are you sure you want to overwrite? (y)/n:
Writing key to /Users/spaxe/.ssh/id_rsa.pub ...
File /Users/spaxe/.ssh/known_hosts exists. Are you sure you want to overwrite? (y)/n:
Writing key to /Users/spaxe/.ssh/known_hosts ...
Keyring loaded. Restored 3 keys.
**Loading keys to the same directory (useful for a new machine):**
$ mkdir keys
$ keystore-load --copy-to keys
Located encrypted keystore at ~/Dropbox/keystore:
Please enter the passphrase:
Keyring decrypted successfully.
Writing key to /Users/spaxe/keys/id_rsa ...
Writing key to /Users/spaxe/keys/id_rsa.pub ...
Writing key to /Users/spaxe/keys/known_hosts ...
Keyring loaded. Restored 3 keys.
**Running tests:**
python3 test.py
License
=======
© Xavier Ho <contact@xavierho.com>
License under MIT License.
Metadata
Release files for keystore 0.3.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 |
|---|---|---|---|---|
| keystore-0.3.0.tar.gz | 6.4 kB | Without provenance | Details for keystore-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| keystore-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for keystore-0.3.0-py3-none-any.whl |
Total release size: 16.1 kB
Release files / keystore-0.3.0.tar.gz
| Download URL | keystore-0.3.0.tar.gz |
|---|---|
| Size | 6.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60cae7e1f67bc829c201e07561cca700f5cf6beeb382463a8c8f02f0fbcdc147
|
|
BLAKE2b-256 checksum How to use checksums |
163dd81c59163cb2fbee0440a261ea3fe30489ab30a3a99f923fcd29937b4237
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / keystore-0.3.0-py3-none-any.whl
| Download URL | keystore-0.3.0-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56b8b9e25b23b260426b7f44654ab0059929283b9abb687af1a72fad853225ff
|
|
BLAKE2b-256 checksum How to use checksums |
23414f573e310f0b3afd51ee20f8fd22c01f4f322eb2daf25eb9a2c696e6fdab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for keystore 0.3.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.