From 9d07117a020ff88591c72b07b93c91c4a7ffca4c Mon Sep 17 00:00:00 2001
From: rfjakob
Date: Sun, 8 Mar 2020 12:00:21 +0100
Subject: Backing up gocryptfs.conf is file when you have a strong password

---
 Best-Practices.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Best-Practices.md b/Best-Practices.md
index 170e546..0027688 100644
--- a/Best-Practices.md
+++ b/Best-Practices.md
@@ -1,10 +1,10 @@
 A collection of wisdom and best practices.  Use this after careful consideration!
 
-* Don't backup your `gocryptfs.conf` file to public sources.
+* Don't backup your `gocryptfs.conf` file to public sources unless you have a strong password.
 
-  See [Issue 50](https://github.com/rfjakob/gocryptfs/issues/50) for reasons.  In short, you should consider not saving this file in public cloud-style backups and instead make sure you have backed it up elsewhere and stored your master key (visible when you ran `gocryptfs -init`).
+  See [Issue 50](https://github.com/rfjakob/gocryptfs/issues/50) for details.
 
-* Do backup you `gocryptfs.diriv`
+* Do backup you `gocryptfs.diriv` along with all other encrypted files.
 
   This file isn't secret.  See [Issue 37](https://github.com/rfjakob/gocryptfs/issues/37).
 
-- 
cgit v1.2.3