bastelfreak
10/21/2025, 11:28 AMcsharpsteen
10/21/2025, 1:45 PMlocalhost -> * likely requires a full restart in order to re-bind the port. That is pretty disruptive, so having Postgres listen on * by default makes it easy to build out a Standard install into a Large or XL without disrupting in-flight operations.
The default configuration does have VERY tight security for what communication is accepted on port 5432. Incoming connections MUST present a certificate signed by the Puppet CA that is also listed in the Postgres pg_ident.conf as granting access to the database role.
Sure, there is a theoretical risk of some 0-day exploit that bypasses auth. Blocking port 5432 with a firewall rule would mitigate that.bastelfreak
10/21/2025, 1:46 PM