{section: How to Use Pool Passwords and CCB}
+
In the following scenario, you're running a submit node (collector, negotiator, schedd) on a local machine you control, and starting virtual machines on a cloud to provide cycles to your pool. We assume those VMs are behind a NAT -- that is, they have outbound but not inbound connectivity. We will configure these startds to use CCB (to allow full communications) and a pool password (for security).
In this scenario, a pool password is useful because it allows nodes to participate in secure communications without establishing any particular individual identity. Since you'll be creating many identical instances of your VM, this can very much simplify management. Conversely, you will be storing the (encrypted) pool password on the VM's disk, so anyone who can access your VM can simply run it in order to join your pool.
