Config file verifiedimportant

A read-only view of /etc/mailerq/config.txt with the vendor's comments intact, which makes it the fastest way to see what a node is actually configured with — including the directives Hub wrote during installation. The masking is inconsistent in a way that matters. database-address and rabbitmq-address are shown as postgresql://xxxx:xxxx@…, but www-auth is not masked at all. Anyone who reaches the console sees the password for it; where several accounts are configured — www-auth takes a comma-separated list — each of them sees everyone's. On a node without www-certificate that password also crosses the network in clear. The practical consequence for us is a rule rather than a fix: the console password Hub generates must be unique per node and used nowhere else, and closing the console is part of installation rather than hardening.