From: Simon Ruderich <simon@ruderich.org>
Date: Tue, 25 Jun 2019 08:07:45 +0000 (+0200)
Subject: README: mention why write bits are removed from generated files
X-Git-Tag: 0.1~42
X-Git-Url: https://ruderich.org/simon/gitweb/?p=nsscash%2Fnsscash.git;a=commitdiff_plain;h=1416d64c367cb29c3ca459b66ac9ffd57413fb43

README: mention why write bits are removed from generated files
---

diff --git a/README b/README
index ee1088a..f559110 100644
--- a/README
+++ b/README
@@ -28,8 +28,8 @@ Nsscash is very careful when deploying the changes:
   when all operations were successful.
 - To prevent unexpected permissions, `nsscash` does not create new files. The
   user must create them first and `nsscash` will then re-use the permissions
-  (without the write bits) and owner/group when updating the file (see
-  examples below).
+  (without the write bits to discourage manual modifications) and owner/group
+  when updating the file (see examples below).
 - To prevent misconfigurations, empty files (no users/groups) are not
   permitted and will not be written to disk. This is designed to prevent the
   accidental loss of all users/groups on a system.