CLVault uses Keyring to provide a command-line utility to safely store and retrieve passwords.
Install it using pip or the setup.py script:
$ python setup.py install $ pip install clvault
Once it’s installed, you will have three scripts installed in your Python scripts folder, you can use to list, store and retrieve passwords:
$ clvault-set blog
Set your password:
Set the associated username (can be blank): tarek
Set a description (can be blank): My blog password
Password set.
$ clvault-get blog
The username is "tarek"
The password has been copied in your clipboard
$ clvault-list
Registered services:
blog My blog password
clvault-set takes a service name then prompt you for a password, and some optional information about your service. The password is safely stored in a keyring while the description is saved in a .clvault file in your home directory. This file is created automatically the first time the command is used.
clvault-get copies the password for a given service in your clipboard, and displays the associated user if any.
clvault-list lists all registered services, with their description when given.
Project page: http://bitbucket.org/tarek/clvault
1 maintainer
Metadata
1 maintainer
Release files for CLVault 0.5
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 | |
|---|---|---|---|---|
| CLVault-0.5.tar.gz | 3.5 kB | Without provenance | Details |
Release files / CLVault-0.5.tar.gz
| Download URL | CLVault-0.5.tar.gz |
|---|---|
| Size | 3.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
243869905ed82fc47e7e5755660e4bc0f8f501aa4dd4ca1fe37068ee3a4363bf
|
|
BLAKE2b-256 checksum How to use checksums |
dc391ecdccc4fdf3f6c9a7a99537f623687daaa2858fadcf7d6bf8bcd0753569
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for CLVault 0.5
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.
