borg/docs/usage/change-passphrase.rst.inc

.. _borg_change-passphrase:

borg change-passphrase
----------------------
::

    usage: borg change-passphrase [-h] [-v] [--debug] [--lock-wait N] [--show-rc]
                                  [--no-files-cache] [--umask M]
                                  [--remote-path PATH]
                                  [REPOSITORY]
    
    Change repository key file passphrase
    
    positional arguments:
      REPOSITORY
    
    optional arguments:
      -h, --help            show this help message and exit
      -v, --verbose, --info
                            enable informative (verbose) output, work on log level
                            INFO
      --debug               enable debug output, work on log level DEBUG
      --lock-wait N         wait for the lock, but max. N seconds (default: 1).
      --show-rc             show/log the return code (rc)
      --no-files-cache      do not load/update the file metadata cache used to
                            detect unchanged files
      --umask M             set umask to M (local and remote, default: 0077)
      --remote-path PATH    set remote path to executable (default: "borg")
    
Description
~~~~~~~~~~~

The key files used for repository encryption are optionally passphrase
protected. This command can be used to change this passphrase.
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384 2015-11-13 15:42:16 +00:00			`.. _borg_change-passphrase:`

			`borg change-passphrase`
			`----------------------`
			`::`

ran build_usage 2015-12-08 09:21:20 +00:00			`usage: borg change-passphrase [-h] [-v] [--debug] [--lock-wait N] [--show-rc]`
			`[--no-files-cache] [--umask M]`
			`[--remote-path PATH]`
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384 2015-11-13 15:42:16 +00:00			`[REPOSITORY]`

			`Change repository key file passphrase`

			`positional arguments:`
			`REPOSITORY`

			`optional arguments:`
ran build_usage 2015-12-08 09:21:20 +00:00			`-h, --help show this help message and exit`
			`-v, --verbose, --info`
			`enable informative (verbose) output, work on log level`
			`INFO`
			`--debug enable debug output, work on log level DEBUG`
			`--lock-wait N wait for the lock, but max. N seconds (default: 1).`
			`--show-rc show/log the return code (rc)`
			`--no-files-cache do not load/update the file metadata cache used to`
			`detect unchanged files`
			`--umask M set umask to M (local and remote, default: 0077)`
			`--remote-path PATH set remote path to executable (default: "borg")`
commit usage files directly into git the generation of those files was causing us way too much pain to justify automatically generating them all the time. those will have to be re-generated with `build_api` or `build_usage` as appropriate, for example when function signatures or commandline flags change. see #384 2015-11-13 15:42:16 +00:00
			`Description`
			`~~~~~~~~~~~`

			`The key files used for repository encryption are optionally passphrase`
			`protected. This command can be used to change this passphrase.`