{section: How to enable pool password authentication}
-If would like to enable a simple method for authenticating daemon-to-daemon communication, pool password is very straightforward. However, it will not work if you have flocking (in or out) enabled.
+If would like to enable a simple method for authenticating daemon-to-daemon communication, pool password is very straightforward. Upon setting up pool password authentication, your HTCondor daemons will only trust other HTCondor daemons that are able to read a secret password that is stored on on each machine in a file that is readable only by the system. This will effectively prevent unauthorized machines from joining your pool, and also prevent users from starting their own HTCondor daemons on machines authorized with host-based (IP address) authentication. However, pool password authentication may not be a good idea if you are federating HTCondor pools across administrative domains via flocking (in or out), since it requires all machines to share the same secret password file.
*INSTRUCTIONS FOR LINUX*
