Configuration¶
Passie configuration files are yaml files. Passpie supports local and global configuration files. To set a local database.
global passpie configuration files lives in ~/.passpierc while local configuration files lives in database directory as a .config file.
Examples¶
Full passpie configuration file¶
path: ~/.passpie
homedir: ~/.gnupg
autopull: null
autopush: null
copy_timeout: 0
extension: .pass
genpass_pattern: "[a-z]{5} [-_+=*&%$#]{5} [A-Z]{5}"
headers:
- name
- login
- password
- comment
aliases:
st: status
rm: remove
ls: list
colors:
login: green
name: yellow
key_length: 4096
recipient: null
repo: true
status_repeated_passwords_limit: 5
table_format: fancy_grid
Partial configuration file¶
recipient: marcwebbie@example.com
copy_timeout: 10
extension: .gpg
table_format: rst
Debugging¶
For debugging, it might be useful to check actual passpie configuration for your commands:
# Global configuration found on ~/.passpierc
passpie config global
# Local configuration found on $PASSPIE_DATABASE/.config
passpie config local
Current config¶
Current configuration with all overriden variables:
passpie config current
OR:
passpie config
Note
If you have pygments installed, to have colored output on the config:
passpie config | pygmentize -l YAML
Options¶
path¶
~/.passpiehomedir¶
~/.gnupgautopull¶
nullautopush¶
nullrecipient¶
nullextension¶
.passcopy_timeout¶
0genpass_pattern¶
"[a-z]{5} [-_+=*&%$#]{5} [A-Z]{5}"table_format¶
fancy_gridSupported table formats:
- plain
- simple
- grid
- fancy_grid
- pipe
- orgtbl
- jira
- psql
- rst
- mediawiki
- moinmoin
- html
- latex
- latex_booktabs
- textile
headers¶
[name, login, password, comments]colors¶
{login: green, name: yellow}Supported color names:
- black (might be a gray)
- red
- green
- yellow (might be an orange)
- blue
- magenta
- cyan
- white (might be light gray)
- reset (reset the color code only)
aliases¶
{}Example configuration:
aliases:
st: status
rm: remove
a: add
u: update
l: log
We can then run our configuration with the short commands:
passpie rm foo@bar
key_length¶
4096Warning
Use a strong primary key. Some people still have 1024-bit AES keys. You really should transition to a stronger bit-length and hashing algo. It is recommend to make a 2048 or 4096-bit key.
Also have a look at GnuPG documentation on keys
repo¶
truestatus_repeated_passwords_limit¶
5