3 ms·
As it was said in the "background section" this is not a problem with redis but a configuration/ops problem instead. Either way, you should always check the op
by dethos 11y ago
As it was said in the "background section" this is not a problem with redis but a configuration/ops problem instead.
Either way, you should always check the open ports and listening services in a given machine. In this case for a quick check you could use: https://www.isredisallsafe.com/ https://www.isredisallsafe.com/
- pixl97 11y ago>this is not a problem with redis but a configuration/ops problem instead. Default system wide failure is a redis problem. Any modern daemon should come with configuration files that a) don't allow the application to run as root unless uncommented by user action, and b) bind to localhost. Further configuration should be necessary to break the system as thoroughly as this user did.