SECURITY: server: don't allow local connections to adduser/deluser.

[disorder] / README.reload

diff --git a/README.reload b/README.reload
index 6c645ec81188411f028f310ea1c87907dfb113f2..f9fa4c7ad24a0e04089259e812fa2521f9189957 100644 (file)
--- a/README.reload
+++ b/README.reload
@@ -18,19 +18,28 @@ bug!
 This defines how aliases are inserted into the track database.  Need
 to think about how changing it will affect things.
 
 This defines how aliases are inserted into the track database.  Need
 to think about how changing it will affect things.
 

-** namepart
+** namepart (enforced at reload only)

 
 Probably affects alias construction.
 
 
 Probably affects alias construction.
 

-** stopword
+** stopword (enforced at reload only)

 
 

-The search database will have to be rebuilt from scratch.  This is
-do-able but AFAIK we don't detect it.
+The search database will have to be rebuilt from scratch.

 
 ** user (enforced at reload only)
 
 All the files will be owned by the wrong user!
 
 
 ** user (enforced at reload only)
 
 All the files will be owned by the wrong user!
 

+** Alias, search database, etc
+
+Rescan can regenerate aliases and the search and tag databases but we
+rather assume that they are either empty or good.  Therefore we need
+to store anything that can affect these values and erase them if they
+change.
+
+The solution is a global pref _dbparams which contains the hash of the
+alias, stopword and namepart data.
+

 * Options that must remain the same across reload
 
 Some things will just require a restart.  We should either enforce
 * Options that must remain the same across reload
 
 Some things will just require a restart.  We should either enforce