4 ms·
Or there just should've been a password. This whole incident would've been prevented and hopefully eventually rectified if they'd put auth on the localhost int
by XorNot 5y ago
Or there just should've been a password.
This whole incident would've been prevented and hopefully eventually rectified if they'd put auth on the localhost interface as well.
Let your tools save passwords, but it's insanity to have anything just blindly accept requests - you're one mis-directed script away from people wiping out your prod DB, let alone dedicated hackers.
- nickjj 5y agoYeah, passwords are good. I remember back in 2016 I had a similar issue with Redis. I ran it with -p 6379:6379 with no password and someone got into my Redis container back when "crackit"[0] was a thing. But I never blamed Docker or Redis. I blamed myself because I was careless for not fully understanding the implications of what -p did at the time. [0]: http://antirez.com/news/96 http://antirez.com/news/96