derivepassphrase.git

1) # derivepassphrase(1)
2) 
3) ## NAME
4) 
5) derivepassphrase – derive a strong passphrase, deterministically, from
6) a master secret
7) 
8) ## SYNOPSIS
9) 
10) ````

11) derivepassphrase [SUBCOMMAND_ARGS]...

12) ````
13) 
14) ## DESCRIPTION
15) 

16) Using a master secret, derive a passphrase for a named service,
17) subject to constraints e.g. on passphrase length, allowed
18) characters, etc.  The exact derivation depends on the selected
19) derivation scheme.  For each scheme, it is computationally
20) infeasible to discern the master secret from the derived passphrase.
21) The derivations are also deterministic, given the same inputs, thus
22) the resulting passphrases need not be stored explicitly.  The
23) service name and constraints themselves also generally need not be
24) kept secret, depending on the scheme.

25) 

26) The currently implemented subcommands are <b>vault</b> (for the scheme
27) used by vault) and <b>export</b> (for exporting foreign configuration
28) data).  See the respective `--help` output for instructions.  If no
29) subcommand is given, we default to <b>vault</b>.

30) 

31) ## SUBCOMMANDS

32) 

33) [<b>export</b>][EXPORT_SUBCMD]
34) :   Export a foreign configuration to standard output.

35) 

36) [<b>vault</b>][VAULT_SUBCMD]
37) :   Derive a passphrase using the vault(1) derivation scheme.

38) 

39) ## DEPRECATION NOTICE

40) 

41) Defaulting to <b>vault</b> is deprecated.  Starting in v1.0, the
42) subcommand must be specified explicitly.

43) 
44) ## CONFIGURATION
45) 
46) Configuration is stored in a directory according to the

47) `$DERIVEPASSPHRASE_PATH` variable, which defaults to
48) `~/.derivepassphrase` on UNIX-like systems and
49) `C:\Users\<user>\AppData\Roaming\Derivepassphrase` on Windows.

50) 
51) ## SEE ALSO
52)