Merge pull request #3760 from ThomasWaldmann/rel1012

Release 1.0.12

docs/changes.rst

@@ -128,8 +128,8 @@ The best check that everything is ok is to run a dry-run extraction::
 Changelog
 =========
 
-Version 1.0.12 (not released yet)
----------------------------------
+Version 1.0.12 (2018-04-08)
+---------------------------
 
 Bug fixes:
 

docs/usage/change-passphrase.rst.inc

@@ -38,3 +38,8 @@ Description
 
 The key files used for repository encryption are optionally passphrase
 protected. This command can be used to change this passphrase.
+
+Please note that this command only changes the passphrase, but not any
+secret protected by it (like e.g. encryption/MAC keys or chunker seed).
+Thus, changing the passphrase after passphrase and borg key got compromised
+does not protect future (nor past) backups to the same repository.

docs/usage/create.rst.inc

@@ -116,3 +116,6 @@ If this is not possible, consider creating a bind mount to a stable location.
 
 See the output of the "borg help patterns" command for more help on exclude patterns.
 See the output of the "borg help placeholders" command for more help on placeholders.
+
+Borg respects the nodump flag. Files flagged nodump will be marked as excluded (x)
+in ``--list`` output.

docs/usage/key_export.rst.inc

@@ -43,6 +43,9 @@ Description
 
 If repository encryption is used, the repository is inaccessible
 without the key. This command allows to backup this essential key.
+Note that the backup produced does not include the passphrase itself
+(i.e. the exported key stays encrypted). In order to regain access to a
+repository, one needs both the exported key and the original passphrase.
 
 There are two backup formats. The normal backup format is suitable for
 digital storage as a file. The ``--paper`` backup format is optimized