upass

upass. Console UI for pass.

Info:This is the README file for upass.
Author:Chris Warrick <chris@chriswarrick.com>
Copyright:© 2015-2018, Chris Warrick.
Date:2018-08-28
Version:0.3.0
https://chriswarrick.com/galleries/upass/directory-listing.png

INSTALLATION

pip install upass

There are also AUR packages available.

USAGE

Run upass and use the friendly console interface.

CONFIGURATION

upass stores its config in ~/.config/kwpolska/upass/upass.ini (but it respects XDG_CONFIG_HOME if you changed it). Available options:

  • keys — keybinding configuration. * help, display, copy, refresh, search, quit — set key bindings for commands,

    space-separated (eg. quit=q f10 will make q and f10 keybindings for quit)

    • uplevel_h — on/off, use the h key as a back button, make sure to change your help key bindings
    • downlevel_l — on/off, use the l key to open directory/password

Appendix A. Contribution rules

Info:Those are the contribution rules for upass.
Copyright:© 2012-2018, Chris Warrick.
License:3-clause BSD

Do you want to contribute to this project? Great! I’d love to see some help, but you must comply with some rules.

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.

Issue reporting

GitHub Issues are the recommended way to report an issue.

When pasting console sessions, you must paste them fully, prompt-to-prompt, to see all the messages and your input. Trim only stuff that you are 1000% sure that is not related to the project in question.

General preparations, rules and pull process

Prepare

A GitHub account is recommended. Patches by e-mail are accepted, but I’d prefer to work via GitHub.

Rules

  1. Commits must have short, informative and logical messages. Signoffs and long messages are recommended. “Fix #xxx” is required if an issue exists.
  2. The following fancy Unicode characters should be used when needed: — “ ” ‘ ’. … should not appear in console output, but may appear elsewhere.
  3. For Python code, use the PEP 8 coding style and PEP 257 documentation style. For other languages, K&R style applies. Braces are mandatory in all blocks (even one-line blocks). Braces are on the same lines as class names and function signatures. Use 4-space indents.

Request a Pull

Done? Go hit the Pull Request button over on GitHub! Your request should be accepted shortly (assuming there are no major errors).

Appendix B. License for upass

Info:This is the license for upass.
Author:Chris Warrick <chris@chriswarrick.com>
Copyright:© 2015-2018, Chris Warrick.
License:BSD (see /LICENSE or Appendix B.)
Date:2018-08-28
Version:0.3.0

Copyright © 2015-2018, Chris Warrick. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the following disclaimer in the documentation and/or other materials provided with the distribution.
  3. Neither the name of the author of this software nor the names of contributors to this software may be used to endorse or promote products derived from this software without specific prior written consent.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Appendix C. Changelog

Info:This is the changelog for upass.
Author:Chris Warrick <chris@chriswarrick.com>
Copyright:© 2015-2018, Chris Warrick.
License:BSD (see /LICENSE or Appendix B.)
Date:2018-08-28
Version:0.3.0

GitHub holds releases, too

More information can be found on GitHub in the releases section.

Version History

0.3.0
  • Add password generation (by Patrick Schneeweis)
0.2.1
  • Also show “no passwords” error message if only dotfiles exist (fix #19)
0.2.0
More granular copying features: users can now choose between copying the first line (old default), copying the entire text, or copying specific fields that are separated with ``: `` (colon, space).
0.1.10
  • Respect PASSWORD_STORE_DIR environment variable (if it’s set)
0.1.9
  • Include missing data files
0.1.8
  • Universal color scheme (for dark and light terminals)
  • Restore Python 2 compatibility
0.1.7
  • Fix mouse support (Issue #13)
0.1.6
  • fix setup.py/MANIFEST.in
0.1.5
  • Warn if store is empty or does not exist (Issue #5)
0.1.4
  • Add j/k support for moving in the list (Issue #4)
0.1.3
  • Don’t show copied passwords (Issue #3)
0.1.2
  • Add mouse wheel support.
0.1.1
  • Fix search form
  • Fix top-level passwords appearing twice
  • Fix d/s/c for directory listings
  • Allow d/s/c keys in password display mode
  • Copy only the first line of multiline passwords
0.1.0
Initial release.

Indices and tables