Tree @lintian-fixes/main (Download .tar.gz)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 | [<img src="https://gitlab.com/uploads/-/system/project/avatar/3157196/logo.png" align="right" height="110"/>][github-link] # pass tomb [![][travis]][travis-link] [![][gitlab]][gitlab-link] [![][coverage]][coverage-link] [![][quality]][quality-link] [![ ][release]][release-link] **A [pass] extension that helps to keep the whole tree of password encrypted inside a [Tomb]** ## Description Due to the structure of `pass`, file- and directory names are not encrypted in the password store. `pass-tomb` provides a convenient solution to put your password store in a [Tomb][github-tomb] and then keep your password tree encrypted when you are not using it. It uses the same GPG key to encrypt passwords and tomb, therefore you don't need to manage more key or secret. Moreover, you can ask pass-tomb to automatically close your store after a given time. **The new workflow is the following:** * Create a password tomb with `pass tomb` - Create a new tomb and open it in `~/.password-store` - Initialise the password store with the same GPG key * Use tomb as usual * When finished, close the password tomb: `pass close` * To use pass again, you need to open the password tomb: `pass open` ## Usage ``` pass tomb 1.3 - A pass extension that helps to keep the whole tree of password encrypted inside a tomb. Usage: pass tomb [-n] [-t time] [-f] [-p subfolder] gpg-id... Create and initialise a new password tomb Use gpg-id for encryption of both tomb and passwords pass open [subfolder] [-t time] [-f] Open a password tomb pass close [store] Close a password tomb pass timer [store] Show timer status Options: -n, --no-init Do not initialise the password store -t, --timer Close the store after a given time -p, --path Create the store for that specific subfolder -f, --force Force operation (i.e. even if swap is active) -q, --quiet Be quiet -v, --verbose Be verbose -d, --debug Print tomb debug messages --unsafe Speed up tomb creation (for testing only) -V, --version Show version information. -h, --help Print this help message and exit. More information may be found in the pass-tomb(1) man page. ``` See `man pass-tomb` for more information. ## Examples **Create a new password tomb** ``` $ pass tomb <gpg-id> (*) Your password tomb has been created and opened in ~/.password-store. (*) Password store initialized for <gpg-id> . Your tomb is: ~/.password.tomb . Your tomb key is: ~/.password.key.tomb . You can now use pass as usual. . When finished, close the password tomb using 'pass close'. ``` **Open a password tomb** ``` $ pass open (*) Your password tomb has been opened in ~/.password-store. . You can now use pass as usual. . When finished, close the password tomb using 'pass close'. ``` **Close a password tomb** ``` $ pass close (*) Your password tomb has been closed. . Your passwords remain present in ~/.password.tomb. ``` **Create a new password tomb and set a timer** ``` $ pass tomb <gpg-id> --timer=1h (*) Your password tomb has been created and opened in ~/.password-store. (*) Password store initialized for <gpg-id> . Your tomb is: ~/.password.tomb . Your tomb key is: ~/.password.key.tomb . You can now use pass as usual. . This password store will be closed in 1h ``` ``` $ pass open (*) Your password tomb has been opened in ~/.password-store. . You can now use pass as usual. . This password store will be closed in 1h ``` **Open a password store and set a timer** ``` $ pass open --timer=10min (*) Your password tomb has been opened in ~/.password-store. . You can now use pass as usual. . This password store will be closed in 10min ``` ## Import existing password repository In order to use pass-tomb with your existing password repository you can: 1. Move your password repository: `mv ~/.password-store ~/.password-store-backup` 2. Create and open a new password tomb: `pass tomb <gpgid>` 3. Move all the content of your password repository in the new password tomb: ``` mv ~/.password-store-backup/ ~/.password-store` ``` ## Environment Variables * `PASSWORD_STORE_TOMB`: path to `tomb` executable * `PASSWORD_STORE_TOMB_FILE`: path to the password tomb (default: `~/.password.tomb`) * `PASSWORD_STORE_TOMB_KEY`: path to the password tomb key file (default: `~/.password.key.tomb`) * `PASSWORD_STORE_TOMB_SIZE`: password tomb size in MB (default: `10`) ## Multiple password tombs It is possible to create multiple pass tomb and open them separately. You only need to set the tomb file, key and the password store directory manually using the environment variables: **Create a tomb** ```sh PASSWORD_STORE_TOMB_FILE=<tomb_path> PASSWORD_STORE_TOMB_KEY=<key_path> PASSWORD_STORE_DIR=<dir_path> pass tomb <gpgid> ``` **Open/Close a tomb** ```sh PASSWORD_STORE_TOMB_FILE=<tomb_path> PASSWORD_STORE_TOMB_KEY=<key_path> PASSWORD_STORE_DIR=<dir_path> pass open PASSWORD_STORE_TOMB_FILE=<tomb_path> PASSWORD_STORE_TOMB_KEY=<key_path> PASSWORD_STORE_DIR=<dir_path> pass close ``` If you always need a second password store, you can create a pass alias, `pass2` that will manage the second store with in `.bashrc`: ```sh alias pass2='PASSWORD_STORE_TOMB_FILE=<tomb_path> PASSWORD_STORE_TOMB_KEY=<key_path> PASSWORD_STORE_DIR=<dir_path> pass' ``` ## Advanced use Using `tomb` to store your password repository, you can take advantage of the tomb advanced feature like *steganography* and *private cloud storage*. The [tomb website][Tomb] provide a good presentation of the features available with Tomb. Moreover, you can read my guide on how to use [Tomb with GPG keys][pujol.io-tomb]. pass-tomb is not compatible with Android, but it should not be an issue for you. If you consider it is safe to put your password-store on Android then, it probably mean you attacker model does not require the need of pass-tomb. ## Installation **Requirements** * `pass 1.7.0` or greater. * `tomb 2.4` or greater. * A `systemd` based linux distribution is required to use the timer feature. **ArchLinux** `pass-tomb` is available in the [Arch User Repository][aur]. ```sh yay -S pass-tomb # or your preferred AUR install method ``` **Debian** ```sh apt install pass-extension-tomb ``` **NixOS** ```sh nix-env -iA nixos.passExtensions.pass-tomb ``` **OSX** > **pass-tomb is based on dm-crypt and therefore it is not compatible with Mac systems.** **From git** ```sh git clone https://github.com/roddhjav/pass-tomb/ cd pass-tomb sudo make install ``` **Stable version** ```sh wget https://github.com/roddhjav/pass-tomb/releases/download/v1.3/pass-tomb-1.3.tar.gz tar xzf pass-tomb-1.3.tar.gz cd pass-tomb-1.3 sudo make install ``` [Releases][releases] and commits are signed using [`06A26D531D56C42D66805049C5469996F0DF68EC`][keys]. You should check the key's fingerprint and verify the signature: ```sh wget https://github.com/roddhjav/pass-tomb/releases/download/v1.3/pass-tomb-1.3.tar.gz.asc gpg --recv-keys 06A26D531D56C42D66805049C5469996F0DF68EC gpg --verify pass-tomb-1.3.tar.gz.asc ``` ## Contribution Feedback, contributors, pull requests are all very welcome. ## License Copyright (C) 2017-2019 Alexandre PUJOL This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. [github-link]: https://github.com/roddhjav/pass-tomb [travis]: https://img.shields.io/travis/roddhjav/pass-tomb/master.svg?style=flat-square [travis-link]: https://travis-ci.com/roddhjav/pass-tomb [gitlab]: https://gitlab.com/roddhjav/pass-tomb/badges/master/pipeline.svg?style=flat-square [gitlab-link]: https://gitlab.com/roddhjav/pass-tomb/pipelines [coverage]: https://img.shields.io/coveralls/roddhjav/pass-tomb/master.svg?style=flat-square [coverage-link]: https://coveralls.io/github/roddhjav/pass-tomb [quality]: https://img.shields.io/codacy/grade/1c58ea63487a4b82874b05220d500c60/master.svg?style=flat-square [quality-link]: https://www.codacy.com/app/roddhjav/pass-tomb [release]: https://img.shields.io/github/release/roddhjav/pass-tomb.svg?maxAge=600&style=flat-square [release-link]: https://github.com/roddhjav/pass-tomb/releases/latest [pass]: https://www.passwordstore.org/ [Tomb]: https://www.dyne.org/software/tomb/ [github-tomb]: https://github.com/dyne/Tomb [pujol.io-tomb]: https://pujol.io/blog/tomb-with-gpg-keys/ [keys]: https://pujol.io/keys [aur]: https://aur.archlinux.org/packages/pass-tomb [releases]: https://github.com/roddhjav/pass-tomb/releases [keybase]: https://keybase.io/roddhjav |
Commit History @lintian-fixes/main
0
»»
- Updating vcs in control. David Kunz 2 years ago
- Updating Standards-Version to 4.6.0. David Kunz 2 years ago
- Updating copyright. David Kunz 2 years ago
- Adding watch file. David Kunz 2 years ago
- Merging upstream version 1.3. David Kunz 2 years ago
- Adding debian version 1.2-1. David Kunz 2 years ago
- Merging upstream version. David Kunz 2 years ago
- Adding debian version 1.1-4.1. David Kunz 2 years ago
- Adding debian version 1.1-4. David Kunz 2 years ago
- Adding debian version 1.1-3. David Kunz 2 years ago
- Adding debian version 1.1-2. David Kunz 2 years ago
- Adding debian version 1.1-1. David Kunz 2 years ago
- Adding upstream version 1.1. David Kunz 2 years ago
- Initial commit. David Kunz 2 years ago
0
»»