derivepassphrase.git

1) # derivepassphrase-vault(1)
2) 
3) ## NAME
4) 

5) derivepassphrase-vault – derive a passphrase using the vault derivation scheme

6) 
7) ## SYNOPSIS
8) 

9) <pre>
10) <code><b>derivepassphrase vault</b> [--phrase | --key] [--length <var>n</var>] [--repeat <var>n</var>] [--lower <var>n</var>] [--upper <var>n</var>] [--number <var>n</var>] [--space <var>n</var>] [--dash <var>n</var>] [--symbol <var>n</var>] <var>SERVICE</var></code>
11) <code><b>derivepassphrase vault</b> {--phrase | --key | … | --symbol <var>n</var>} … --config [--unset <var>setting</var> …] [--overwrite-existing | --merge-existing] [<var>SERVICE</var>]</code>
12) <code><b>derivepassphrase vault</b> {--notes <var>SERVICE</var> | --delete <var>SERVICE</var> | --delete-globals | --clear}</code>
13) <code><b>derivepassphrase vault</b> [--export-as {json | sh}] {--import <var>PATH</var> | --export <var>PATH</var>}</code>
14) </pre>

15) 
16) ## DESCRIPTION
17) 

18) Using a master passphrase or a master SSH key, derive a passphrase for <var>SERVICE</var>, subject to length, character and character repetition constraints, in a manner compatible with James Coglan's <i>vault</i>(1).

19) 

20) The derivation is cryptographically strong, meaning that even if a single passphrase is compromised, guessing the master passphrase or a different service's passphrase is computationally infeasible.
21) The derivation is also deterministic, given the same inputs, thus the resulting passphrase need not be stored explicitly.
22) 
23) The service name and constraints themselves also need not be kept secret; the latter are usually stored in a world-readable file.

24) 
25) ## OPTIONS
26) 

27) ### Passphrase generation
28) 
29) The passphrase generation options can be divided into "passphrase source" options (`--phrase`, `--key`) and "passphrase constraint" options (all others).
30) The passphrase source options are mutually exclusive --- you may only specify one of them --- while the passphrase constraint options may be combined in any way.
31) The <var>SERVICE</var> is mandatory (see synopsis #1), unless the `--config` option is specified (see synopsis #2).
32) All character constraints refer to ASCII printable characters only (space (`U+0020`) to tilde (`U+007E`), excluding the grave accent (`U+0060`)).

33) 
34) <b>-p</b>, <b>-</b><b>-phrase</b>

35) :   Prompt for a passphrase.
36) 
37)     See also ["Configuration"](#configuration) for how this interacts with a stored passphrase or SSH key.

38) 
39) <b>-k</b>, <b>-</b><b>-key</b>

40) :   Select an SSH key.
41) 
42)     An SSH agent such as OpenSSH’s <i>ssh-agent</i>(1) or PuTTY’s <i>pageant</i>(1) must be running and accessible, and have the desired key loaded.
43)     The SSH key must also be <i>suitable</i> for this purpose; see ["SSH KEY SUITABILITY"](#ssh-key-suitability) for details.

44) 

45)     See also ["Configuration"](#configuration) for how this interacts with a stored passphrase or SSH key.

46) 

47) <b>-l</b> <var>n</var>, <b>-</b><b>-length</b> <var>n</var>
48) :   Force the passphrase to have the length <var>n</var>.
49)     Defaults to the length <b>20</b> if not specified, or if explicitly specified as <code>0</code>.

50) 

51) <b>-r</b> <var>n</var>, <b>-</b><b>-repeat</b> <var>n</var>
52) :   Permit only runs of up to <var>n</var> consecutive occurrences of the same character.
53)     Alternatively, forbid immediate additional repetitions of length <var>n</var> (or more) for any character in the derived passphrase.
54)     Setting <var>n</var> = `0` disables repetition constraints, which is the default.

55) 

56) <b>-</b><b>-lower</b> <var>n</var>
57) :   Include at least <var>n</var> lowercase characters in the derived passphrase.
58)     Setting <var>n</var> = `0` forbids these characters entirely.
59)     The default is to not constrain the occurrences in any manner.

60) 

61) <b>-</b><b>-upper</b> <var>n</var>
62) :   Include at least <var>n</var> uppercase characters in the derived passphrase.
63)     Setting <var>n</var> = `0` forbids these characters entirely.
64)     The default is to not constrain the occurrences in any manner.

65) 

66) <b>-</b><b>-number</b> <var>n</var>
67) :   Include at least <var>n</var> digits in the derived passphrase.
68)     Setting <var>n</var> = `0` forbids these characters entirely.
69)     The default is to not constrain the occurrences in any manner.

70) 

71) <b>-</b><b>-space</b> <var>n</var>
72) :   Include at least <var>n</var> spaces in the derived passphrase.
73)     Setting <var>n</var> = `0` forbids these characters entirely.
74)     The default is to not constrain the occurrences in any manner.

75) 

76) <b>-</b><b>-dash</b> <var>n</var>
77) :   Include at least <var>n</var> "dashes" (`-` or `_`) in the derived passphrase.
78)     Setting <var>n</var> = `0` forbids these characters entirely.
79)     The default is to not constrain the occurrences in any manner.

80) 

81) <b>-</b><b>-symbol</b> <var>n</var>
82) :   Include at least <var>n</var> symbols (any of `!"#$%&'()*+,./:;<=>?@[\]^{|}~-_`) in the derived passphrase.
83)     Setting <var>n</var> = `0` forbids these characters entirely, effectively also implying `--dash 0`.
84)     The default is to not constrain the occurrences in any manner.

85) 
86) ### Configuration
87) 

88) The configuration options directly modify the stored settings: default settings, known services, and service-specific settings.
89) They are mutually exclusive; you may only specify one of them.
90) The <var>SERVICE</var> is mandatory for `--notes` and `--delete`, optional for `--config`, and forbidden for `--delete-globals` and `--clear` (see synopsis #2 and synopsis #3).
91) 

92) <b>-n</b>, <b>-</b><b>-notes</b>

93) :   Spawn an editor to edit notes for <var>SERVICE</var>.
94)     Use the `VISUAL` or `EDITOR` environment variables to configure the spawned editor.

95) 
96) <b>-c</b>, <b>-</b><b>-config</b>

97) :   Save the given settings for <var>SERVICE</var> (if given), or save the given settings as global default settings.
98) 
99)     See the ["Passphrase generation"](#passphrase-generation) and ["Compatibility and extension options"](#compatibility-and-extension-options) sections for other options compatible with `--config`.
100) 
101)     !!! danger
102) 
103)         Do **not** use the `--phrase` and `--config` options together.
104)         The configuration is assumed to *not contain sensitive contents*, and is *not encrypted*.

105) 
106) <b>-x</b>, <b>-</b><b>-delete</b>

107) :   Delete all stored settings for <var>SERVICE</var>.

108) 
109) <b>-</b><b>-delete-globals</b>

110) :   Delete all stored global default settings.

111) 
112) <b>-X</b>, <b>-</b><b>-clear</b>

113) :   Delete all stored settings.

114) 
115) ### Storage management
116) 

117) The storage management options deal with importing and exporting the stored settings.
118) They are mutually exclusive; you may only specify one of them.
119) Using `-` as <var>PATH</var> for standard input/standard output is supported.
120) 
121) <b>-e</b> <var>PATH</var>, <b>-</b><b>-export</b> <var>PATH</var>
122) :   Export all saved settings into file <var>PATH</var>.

123) 

124) <b>-i</b> <var>PATH</var>, <b>-</b><b>-import</b> <var>PATH</var>
125) :   Import saved settings from file <var>PATH</var>.

126) 

127) ### Compatibility and extension options
128) 
129) By default, <b>derivepassphrase vault</b> behaves in a manner compatible with <i>vault</i>(1).
130) The compatibility and extension options modify the behavior to enable additional functionality, or specifically to force compatibility.
131) 
132) <i>vault</i>(1) supports none of these options, and behaves as if the option had not been given or had been left in its default state.
133) 
134) <b>-</b><b>-overwrite-existing</b> / <b>-</b><b>-merge-existing</b>
135) :   When importing a configuration via `--import`, or configuring the settings via `--config`, overwrite or merge (<em>default</em>) the existing configuration.
136) 
137)     If overwriting the configuration, then the whole configuration (for `--import`) or the respective section (service-specific or global, for `--config`), will be written from scratch.
138)     If merging, then each section (service-specific or global, for `--import`) or each singular setting (for `--config`) will be overwritten, but other unaffected settings/sections will not.
139) 
140)     (<i>vault</i>(1) behaves as if `--merge-existing` were always given.)
141) 
142) <b>-</b><b>-unset</b> <var>setting</var>
143) :   When configuring via `--config`, also unset the specified <var>setting</var>, where <var>setting</var> is one of the passphrase generation settings (<code>phrase</code>, <code>key</code>, <code>lower</code>, …).
144)     May be specified multiple times.
145)     Must not overlap with any of the settings being set afterwards.
146) 
147)     (vault(1) does not support this option.)
148) 
149) <b>-</b><b>-export-as</b> \{ <b>json</b> | <b>sh</b> \}
150) :   When exporting the configuration via `--export`, export as JSON (default) or as a shell script in <i>sh</i>(1) format.
151) 
152)     The JSON format is compatible with <i>vault</i>(1).
153)     For the shell script format, see the ["SHELL SCRIPT EXPORT FORMAT"](#shell-script-export-format) section for details.
154) 
155)     (vault(1) behaves as if `--export-as json` were always given.)

156) 
157) ### Other Options
158) 

159) <b>-</b><b>-version</b>

160) :   Show the version and exit.
161) 
162) <b>-h</b>, <b>-</b><b>-help</b>

163) :   Show a help message and exit.
164) 
165) ## SHELL SCRIPT EXPORT FORMAT
166) 
167) If the shell script export format is selected, the configuration will be exported as a POSIX <i>sh</i>(1) script, containing calls to <b>derivepassphrase vault</b> to reconstruct the current configuration from scratch.
168) The script assumes a conforming <i>sh</i>(1), with support for "here" documents.
169) 
170) !!! danger
171) 
172)     **Do not run these emitted shell scripts directly without double-checking their output first!**
173) 
174) ## SSH KEY SUITABILITY
175) 
176) An SSH key is <dfn>suitable</dfn> for use with <b>derivepassphrase vault</b> if the SSH agent guarantees that signatures produced with this key will be <em>deterministic</em>, given the same message to be signed.
177) This is a property specific to the key type, and sometimes the agent used:
178) 
179)   * RSA, Ed25519 and Ed448 keys are always suitable.
180)     OpenSSH’s <i>ssh-agent</i>(1) supports only these keys as suitable keys.
181) 
182)   * DSA and ECDSA keys are suitable if the SSH agent supports deterministic DSA signatures, e.g. by implementing RFC 6979.
183)     PuTTY’s <i>pageant</i>(1) supports this, in addition to the always-suitable keys mentioned above.
184) 
185) ## ENVIRONMENT
186) 
187) `VISUAL`, `EDITOR`
188) :   <b>derivepassphrase vault</b> uses this editor to edit service notes when called with `--notes`.
189)     `VISUAL` has higher precedence than `EDITOR`.

190) 

191) `DERIVEPASSPHRASE_PATH`
192) :   <b>derivepassphrase</b> stores its configuration files and data in this directory.
193)     Defaults to `~/.derivepassphrase`.

194) 

195) ## FILES

196) 

197) `$DERIVEPASSPHRASE_PATH/vault.json`
198) :   The stored configuration for <b>derivepassphrase vault</b>: the default passphrase generation settings, the known service names, and the service-specific settings.
199)     This file is <em>not</em> intended for the user to edit.
200) 
201) ## SECURITY
202) 
203) !!! danger
204) 
205)       * There is **no way** to retrieve the generated passphrases if the master passphrase, the SSH key, or the exact passphrase settings are lost, short of trying out all possible combinations.
206)         You are **strongly** advised to keep independent backups of the settings and the SSH key, if any.
207) 
208)       * The configuration is **not** encrypted, and you are **strongly** discouraged from using a stored passphrase.
209) 
210)       * You are **strongly** advised to avoid the (shell script) configuration export format if possible, and use the JSON format instead.
211)         If you *must* use the shell script format, then **always** validate the export before attempting to interpret or run it.
212) 
213) ## EXAMPLES
214) 
215) ??? example "`derivepassphrase vault --phrase email`"
216) 
217)     Prompt for a master passphrase, then generate a standard passphrase (length 20, no character or repetition constraints) for the "email" service.
218) 
219) ??? example "`derivepassphrase vault --key --upper 9 --lower 9 example.com`"
220) 
221)     Select an SSH key from the available suitable SSH keys in the running SSH agent, then generate a passphrase for the `example.com` service using the previously selected SSH key.
222)     The passphrase will have (standard) length 20, and at least nine characters will be uppercase characters and at least another nine characters will be lowercase characters.
223) 
224) ??? example "`derivepassphrase example.com vault --key --upper 9 --lower 9 --number 9`"
225) 
226)     Attempt to generate a passphrase as in the previous example.
227)     This example will <em>error out</em>, because the passphrase constraints require at least 27 characters and the standard passphrase length 20 cannot accomodate this.
228) 
229) ??? example "`derivepassphrase --config vault --key --upper 9 --lower 9 --space 2`"
230) 
231)     After selecting an SSH key, configure the default settings to use exactly nine uppercase characters, nine lowercase characters, and two spaces for each generated passphrase.
232)     (The specific service settings, or the command-line invocation, can still override these settings.)
233) 
234) ??? example "`derivepassphrase vault example.com`"
235) 
236)     Because of the previous setting, the generated passphrase for the `example.com` service will behave as if `--key --upper 9 --lower 9 --space 2` had been specified during invocation (with the SSH key already having been selected).
237)     In particular, it is neither necessary to specify `--phrase` or `--key` nor is it necessary to actually select an SSH key or to type in a master passphrase.
238) 
239) ## DIAGNOSTICS
240) 
241) The derivepassphrase vault utility exits 0 on success, and >0 if an error occurs.
242) 

243) ### Fatal error messsages on standard error
244) 
245) (`%s` indicates a variable part of the message.)
246) 
247) ??? failure "`%s is mutually exclusive with %s.`"
248) 
249)     The two indicated options must not be used at the same time.
250) 
251) ??? failure "`%s requires a SERVICE or --config.`"
252) 
253)     Using the indicated passphrase generation option requires the <var>SERVICE</var> argument or the `--config` option.
254) 
255) ??? failure "`%s requires a SERVICE.`"
256) 
257)     Using the indicated option requires the <var>SERVICE</var> argument.
258) 
259) ??? failure "`%s does not take a SERVICE argument.`"
260) 
261)     The indicated option must not be specified together with the <var>SERVICE</var> argument.
262) 
263) ??? failure "`Cannot load vault settings: %s.`"
264) 
265)     There was a fatal problem loading the stored vault configuration data.
266)     Further details are contained in the variable part of the message.
267) 
268) ??? failure "`Cannot store vault settings: %s.`"
269) 
270)     There was a fatal problem saving the vault configuration data.
271)     Further details are contained in the variable part of the message.
272) 
273) ??? failure "`Cannot import vault settings: %s.`"
274) 
275)     There was a fatal problem loading the imported vault configuration data.
276)     Further details are contained in the variable part of the message.
277) 
278) ??? failure "`Cannot export vault settings: %s.`"
279) 
280)     There was a fatal problem saving the exported vault configuration data.
281)     Further details are contained in the variable part of the message.
282) 
283) ??? failure "`Cannot load user config: %s.`"
284) 
285)     There was a fatal problem loading the central user configuration file.
286)     Further details are contained in the variable part of the message.
287) 
288) ??? failure "`The user configuration file is invalid.`"
289) 
290)     (Exactly what it says.)
291) 
292) ??? failure "`No usable SSH keys were found`"
293) 
294)     The running SSH agent does not contain any suitable SSH keys.
295) 
296) ??? failure "`No valid SSH key selected`"
297) 
298)     We requested that an SSH key be selected, but we got an invalid selection.
299) 
300) ??? failure "`The requested SSH key is not loaded into the agent.`"
301) 
302)     The running SSH agent does not contain the necessary SSH key.
303) 
304) ??? failure "`Cannot find any running SSH agent because SSH_AUTH_SOCK is not set.`"
305) 
306)     We require a running SSH agent, but cannot locate its communication channel, which is normally indicated by the `SSH_AUTH_SOCK` environment variable.
307) 
308) ??? failure "`Cannot connect to an SSH agent because this Python version does not support UNIX domain sockets.`"
309) 
310)     This Python installation does not support the communication mechanism necessary to talk to SSH agents.
311) 
312) ??? failure "`Cannot connect to the SSH agent: %s.`"
313) 
314)     We cannot connect to the SSH agent indicated by the `SSH_AUTH_SOCK` environment variable.
315)     Further details are contained in the variable part of the message.
316) 
317) ??? failure "`The SSH agent failed to complete the request`"
318) 
319)     The SSH agent---while responsive in principle---failed to or refused to supply a list of loaded keys.
320) 
321) ??? failure "`Error communicating with the SSH agent`"
322) 
323)     There was a system error communicating with the SSH agent.
324) 
325) ??? failure "`Not saving any new notes: the user aborted the request.`"
326) 
327)     (Exactly what it says.)
328) 
329) ??? failure "`Cannot update %s settings without actual settings.`"
330) 
331)     Using `--config` requires at least one of the `--phrase`, `--key`, `--length`, etc. options.
332) 
333) ??? failure "`Attempted to unset and set %s at the same time.`"
334) 
335)     While handling `--config`, the same configuration setting was passed as an option and as an argument to `--unset`.
336) 
337) ??? failure "`Generating a passphrase requires a SERVICE.`"
338) 
339)     (Exactly what it says.)
340) 
341) ??? failure "`No passphrase or key was given in the configuration.`"
342) 
343)     <b>derivepassphrase vault</b> does not know whether to use a master SSH key or a master passphrase.
344) 
345) ??? failure "`No passphrase was given: the user aborted the request.`"
346) 
347)     (Exactly what it says.)
348) 
349) ??? failure "`No SSH key was selected: the user aborted the request.`"
350) 
351)     (Exactly what it says.)
352) 
353) ### Non-fatal warning and info messages on standard error
354) 
355) (`%s` indicates a variable part of the message.)
356) 
357) ??? warning "`The %s passphrase is not %s-normalized.`"
358) 
359)     The indicated passphrase---as a Unicode string---is not properly normalized according to the preferred Unicode normalization form (as specified in the central configuration file).
360)     It is therefore possible that the passphrase---as a byte string---is not the same byte string as you expect it to be (even though it *looks* correct), and that the derived passphrases thus do not match their expected values either.
361)     Please double-check.
362) 
363) ??? warning "`An empty SERVICE is not supported by vault(1).`"
364) 
365)     <i>vault</i>(1) does not support the empty string as a value for <var>SERVICE</var>; it will treat the <var>SERVICE</var> as missing.
366)     For compatibility, <b>derivepassphrase vault</b> will do the same.
367)     In particular, if the empty service is imported in a configuration via `--import`, then this service cannot be accessed via the <b>derivepassphrase vault</b> command-line.
368) 
369) ??? warning "`Replacing invalid value %s for key %s with %s.`"
370) 
371)     When importing a configuration, the indicated invalid value has been replaced with the indicated replacement value.
372)     (The "interpretation" of the configuration doesn’t change).
373) 
374) ??? warning "`Removing ineffective setting %s = %s.`"
375) 
376)     When importing a configuration, the indicated ineffective setting has been removed.
377)     (The "interpretation" of the configuration doesn’t change).
378) 
379) ??? warning "`Setting a %s passphrase is ineffective because a key is also set.`"
380) 
381)     The configuration (global or key-specific) contains both a stored master passphrase and an SSH key.
382)     The master passphrase will not take effect.
383) 
384) ??? warning "`A subcommand will be required in v1.0.`"
385) 
386)     [Since v0.2.0, until v1.0.]
387)     This command now requires a subcommand.
388)     For compatibility, it currently defaults to "vault".
389) 
390) ??? warning "`Using deprecated v0.1-style config file %s, instead of v0.2-style %s.`"
391) 
392)     [Since v0.2.0, until v1.0.]
393)     A configuration file has been renamed.
394)     <b>derivepassphrase vault</b> will attempt to rename the file itself (`Successfully migrated to %s.`), or complain if it cannot rename it (`Failed to migrate to %s: %s`).
395) 

396) ## COMPATIBILITY
397) 
398) ### With other software
399) 
400) <b>derivepassphrase vault</b> is <em>almost</em> drop-in compatible with James Coglan’s <i>vault</i>(1), version 0.3.0 (including "storeroom" support), meaning that each tool supports the same file formats and command-line arguments/options as the other one.
401) 
402) Exceptions:
403) 
404)   * <i>vault</i>(1) does not support the ["Compatibility and extension options"](#compatibility-and-extension-options) listed above.
405) 
406)   * <b>derivepassphrase vault</b> can import and generate configuration exports in the same format as <i>vault</i>(1), but it cannot <em>natively</em> read or write <i>vault</i>(1)'s configuration file (non-storeroom) or configuration directory (storeroom).
407)     (The sister command <i>derivepassphrase-export</i>(1) can read both these formats and export the contents.)
408) 
409) ### Forward and backward compatibility
410) 
411)   * [Since v0.2.0.]
412)     In v1.0, the commands <b>derivepassphrase</b> and <b>derivepassphrase export</b> will require an explicit subcommand name.
413)     Both default to the subcommand <b>vault</b>.
414)   * [Since v0.2.0.]
415)     In v1.0, the configuration data file for the <b>vault</b> subcommand will be named `vault.json`, instead of `config.json`.
416)   * [Since v0.2.0, to be removed in v1.0.]
417)     An existing configuration data file `config.json` will be attempted to be renamed to `vault.json`.

418) 
419) ## SEE ALSO
420)