> The mistake here is a MongoDB that didn't require authentication, not that docker's clunky iptables setup exposed it to the internet. If you're backing up di

> The mistake here is a MongoDB that didn't require authentication, not that docker's clunky iptables setup exposed it to the internet. If you're backing up diligently, have a problem, go to restore backup, and discover that the backups are unusable due to an issue caused by the backup software's default configuration, you could say "the mistake here is you relying on a single backup system, pardner, not the backup software's bad default configuration," and in the sense that it's good advice to have multiple backup strategies, sure, you're technically correct. But that doesn't excuse the backup software from having a dangerously bad default configuration. That would be relatively trivial to fix. That they've apparently known about for years.