MYPASS(1)

NAME
mypass - A secure password manager with command line interface

SYNOPSIS

        mypass [-h] {get,add,new,remove,rename,list,alias,changepw,lock} ...

USAGE
When you run most of the commands below, you will be prompted for the passhprase to decrypt/encrypt the credentials with. If the encrypted file doesn't exist yet, it will be created when you store any credentials for the first time. By default, a daemon is spawned and shuts down after 30 minutes of inactivity, so that you don't have to enter your passphrase again when performing multiple actions within that period.

  mypass add <context> [<username>] [<password>]
Stores credentials for the given context.

The context can be any unique keyword which you relate to these credentials. But if the credentials are for a website, it is recommended to use the corresponding domain as context, so that the browser extension finds the credentials, see below.

The username is optional, but specifying a username if there is any, allows you to store multiple username/password pairs for the same context. Also, if a username is given, it will be used by the browser extension when filling out web forms.

If password is omitted you will be prompted for the password. Passing the password on the command line is NOT recommeded, except for import scripts, as it will end up in your shell's history.

  mypass new <context> [<username>]
Same as mypass add, but stores a new random secure password and prints it.

  mypass get <context>
Prints the credentials for the given context.

  mypass list
Prints each context (one per line) that any credentials have been stored for. In order to filter the list, just pipe the output to programs like grep.

  mypass remove <context> [<username>]
Deletes credentials from the encrypted storage. If username is given, only this username and the associated password is removed. If username is omitted, the whole context is wiped.

  mypass rename --new-{context|username}=<newvalue> <context> [<username>]
Moves credentials around within the encrypted storage.

  Examples
Renaming a context:

        mypass rename --new-context=new.example.com old.example.com

Changing the username for example.com from john to rose:

        mypass rename --new-username=rose example.com john

Adding a username to a password which has been stored without an associated username:

        mypass rename --new-username=rose example.com

  mypass alias <context> <alias>
Creates a new context that refers to the credentials of an existing context.

Changes to the credentials performed under either context will be reflected when looking up the credentials for the other context. Removing either context doesn't remove the credentials as long as the other context exists.

  mypass changepw
Prompts you for a new passphrase. Existing credentials are re-encrypted using this passphrase.

  mypass lock
Forces the daemon to immediately shutdown, if it is running, so that you'd have to enter the passphrase again, from now on.

CONFIGURATION
Optionally, you can create a config file under ~/.config/mypass/config.ini, in order to override any of the following presets:

        [daemon]
        # Minutes of inactivity after which the daemon shuts down, and you have
        # to enter the passphrase, the credentials are encrypted with, again.
        timeout = 30
        # Path to log file any excpetions thrown by the daemon are written to.
        logfile = ~/.config/mypass/log
        [database]
        # Path to the encrypted file storing the credentials.
        path = ~/.config/mypass/db
        [password]
        # Length of newly generated passwords.
        length = 16

AUTHORS
Sebastian Noack <sebstian.noack@gmail.com>.