From d3a037ebc8aebcb8e2a91d1a66e9d7a1ab57104b Mon Sep 17 00:00:00 2001 From: Asif Bacchus Date: Sun, 21 Oct 2018 17:08:44 -0600 Subject: [PATCH] readme: updated borg details protection section --- README.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7d4fc26..9e628d0 100644 --- a/README.md +++ b/README.md @@ -49,6 +49,10 @@ ## Environment notes addition, it reads easy to edit external plain-text files for borg settings so you don't have to weed through the script code to supply things like passwords. +**This script autodetects the location of your Mailcow configuration file. If +you have multiple files with the same name on your system, the script will +likely get confused and exit with an error** + ## Why this script must be run as root This script must be run by the root user and will exit with an error if you try @@ -181,9 +185,12 @@ ### Protect your borg details file This file contains information on how to access and decrypt your borg repo, therefore, you **must** protect it. You should lock it out for everyone but your root user. Putting it in your root folder is not enough! Run the following -commands to restrict access to the root user only (assuming filename is and -mc_borg.details root:roo and mc_borg.detailsowner chmod 60 and mc_borg.detailss -to root only (read/write) +commands to restrict access to the root user only (assuming filename is +*mc_borg.details*): + +```Bash +chown root:root mc_borg.details # make root the owner of this file +chmod 600 mc_borg.details # only grant access to root user (read/write) ``` ### borg specific entries (lines 1-4)