Planning to implement the roaming feature, I had some basic security questions.
I assume we want to put the ID file in the personal address book - seems like the most flexible setup. If so, is it advisable to:
-
encrypt the names.nsf db to avoid potential browsing of the ID file when a replica is left on the local system? Or is it advisable to encrypt it anyway?
-
tighten up the ACL on that DB - and if so what are the recommended settings? Is it okay to lock out everyone except the owner and the LocalDomainServers?
-
change the admin server for this db to the server where the roaming files are (currently no admin server is set)?
-
enforce consistent ACL?
Or is the ID file already suitably protected without any special measures?
Any other security pointers appreciated. TIA.
-Andy