brew install pass\r\necho \"source \/usr\/local\/etc\/bash_completion.d\/password-store\" >> ~\/.bashrc<\/pre>\nSince I already installed pass on my Mac a while back I will be installing it on a Docker container with Ubuntu 16.04.<\/p>\n
root@0b415380eb80:\/# apt-get install -y pass<\/pre>\nAfter pass successfully installs, try running it<\/p>\n
root@0b415380eb80:\/# pass\r\nError: password store is empty. Try \"pass init\".\r\nroot@0b415380eb80:\/#<\/pre>\nWell that is pretty straight forward, it appears we need to initiliaze the db.<\/p>\n
root@0b415380eb80:\/# pass init\r\nUsage: pass init [--path=subfolder,-p subfolder] gpg-id...\r\nroot@0b415380eb80:\/#<\/pre>\nLooks like we need to provide ‘key’…can that be just anything?<\/p>\n
root@0b415380eb80:\/# pass init \"tuxlabs Password Key\"\r\nmkdir: created directory '\/root\/.password-store\/'\r\nPassword store initialized for tuxlabs Password Key\r\nroot@0b415380eb80:\/# pass\r\nPassword Store\r\nroot@0b415380eb80:\/#<\/pre>\nNow our password store looks initialized ! Let’s try inserting a password into the DB !<\/p>\n
root@0b415380eb80:\/# pass insert Gmail\/myemail\r\nmkdir: created directory '\/root\/.password-store\/Gmail'\r\nEnter password for Gmail\/myemail:\r\nRetype password for Gmail\/myemail:\r\ngpg: tuxlabs Password Key: skipped: No public key\r\ngpg: [stdin]: encryption failed: No public key\r\nroot@0b415380eb80:\/#<\/pre>\nUh oh what happened ? Well remember I said it uses GPG, and we not only don’t have a gpg key setup in our Docker container, but we initialized our Pass DB without using a GPG Key (the whole point) !<\/p>\n
root@0b415380eb80:\/# gpg --list-keys\r\nroot@0b415380eb80:\/#<\/pre>\nTo remedy this we need to create a GPG key<\/p>\n
Creating your GPG Key<\/h3>\nroot@0b415380eb80:\/# gpg --gen-key\r\ngpg (GnuPG) 1.4.20; Copyright (C) 2015 Free Software Foundation, Inc.\r\nThis is free software: you are free to change and redistribute it.\r\nThere is NO WARRANTY, to the extent permitted by law.\r\n\r\nPlease select what kind of key you want:\r\n (1) RSA and RSA (default)\r\n (2) DSA and Elgamal\r\n (3) DSA (sign only)\r\n (4) RSA (sign only)\r\nYour selection? 1\r\nRSA keys may be between 1024 and 4096 bits long.\r\nWhat keysize do you want? (2048) 4096\r\nRequested keysize is 4096 bits\r\nPlease specify how long the key should be valid.\r\n 0 = key does not expire\r\n <n> = key expires in n days\r\n <n>w = key expires in n weeks\r\n <n>m = key expires in n months\r\n <n>y = key expires in n years\r\nKey is valid for? (0)\r\nKey does not expire at all\r\nIs this correct? (y\/N) y\r\n\r\nYou need a user ID to identify your key; the software constructs the user ID\r\nfrom the Real Name, Comment and Email Address in this form:\r\n \"Heinrich Heine (Der Dichter) <heinrichh@duesseldorf.de>\"\r\n\r\nReal name: Tuxninja\r\nEmail address: tuxninja@tuxlabs.com\r\nComment: TuxLabs\r\nYou selected this USER-ID:\r\n \"Tuxninja (TuxLabs) <tuxninja@tuxlabs.com>\"\r\n\r\nChange (N)ame, (C)omment, (E)mail or (O)kay\/(Q)uit? O\r\nYou need a Passphrase to protect your secret key.\r\n\r\ngpg: gpg-agent is not available in this session\r\nWe need to generate a lot of random bytes. It is a good idea to perform\r\nsome other action (type on the keyboard, move the mouse, utilize the\r\ndisks) during the prime generation; this gives the random number\r\ngenerator a better chance to gain enough entropy.\r\n............+++++\r\n...................+++++\r\nWe need to generate a lot of random bytes. It is a good idea to perform\r\nsome other action (type on the keyboard, move the mouse, utilize the\r\ndisks) during the prime generation; this gives the random number\r\ngenerator a better chance to gain enough entropy.\r\n...+++++\r\n+++++\r\ngpg: key 5B2F89A5 marked as ultimately trusted\r\npublic and secret key created and signed.\r\n\r\ngpg: checking the trustdb\r\ngpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model\r\ngpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u\r\npub 4096R\/5B2F89A5 2016-12-14\r\n Key fingerprint = 5FF6 1717 4415 03FF D455 7516 CF8E 1BDC 5B2F 89A5\r\nuid Tuxninja (TuxLabs) <tuxninja@tuxlabs.com>\r\nsub 4096R\/EF0F232F 2016-12-14\r\n\r\nroot@0b415380eb80:\/#<\/pre>\nTo view your GPG key run<\/p>\n
root@0b415380eb80:\/# gpg --list-keys\r\n\/root\/.gnupg\/pubring.gpg\r\n------------------------\r\npub 4096R\/5B2F89A5 2016-12-14\r\nuid Tuxninja (TuxLabs) <tuxninja@tuxlabs.com>\r\nsub 4096R\/EF0F232F 2016-12-14\r\n\r\nroot@0b415380eb80:\/#<\/pre>\nNow we can see we have one GPG key, with the ID 5B2F89A5<\/p>\n
Let’s try re-initializing Pass.\u00a0<\/strong><\/p>\nroot@0b415380eb80:\/# pass init \"5B2F89A5\"\r\nPassword store initialized for 5B2F89A5\r\nroot@0b415380eb80:\/#<\/pre>\nBut we have a problem, re-initializing Pass doesn’t get rid of our previous insert into the db. As you can see here our Pass DB is effectively corrupt.<\/p>\n
root@0b415380eb80:~# pass\r\nPassword Store\r\n`-- Gmail\r\nroot@0b415380eb80:~# pass rm Gmail\r\nAre you sure you would like to delete Gmail? [y\/N] y\r\nrm: cannot remove '\/root\/.password-store\/Gmail': Is a directory\r\nroot@0b415380eb80:~# pass rm Gmail\/myemail\r\nError: Gmail\/myemail is not in the password store.\r\nroot@0b415380eb80:~#<\/pre>\nHmmm, what’s a guy to do….<\/p><\/blockquote>\n
root@0b415380eb80:~# rm -rf .password-store\/Gmail\/\r\nroot@0b415380eb80:~# pass\r\nPassword Store\r\nroot@0b415380eb80:~#<\/pre>\nYes it really was that simple, and that is one more reason why I love pass.<\/p>\n
You can also initialize your password store using git for version control, see the passwordstore.org website for more info !<\/p><\/blockquote>\n
Now let’s insert some good stuff.<\/p>\n
Inserting A Password into Pass<\/h3>\nroot@0b415380eb80:~# pass insert Gmail\/myemail\r\nEnter password for Gmail\/myemail:\r\nRetype password for Gmail\/myemail:\r\nroot@0b415380eb80:~# pass\r\nPassword Store\r\n`-- Gmail\r\n `-- myemail\r\nroot@0b415380eb80:~#<\/pre>\nThat seems to have worked. Let’s try to retrieve the pass.<\/p>\n