-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Your Redis instance may be publicly accessible. #214
Comments
TITLE TL;DR FAQ Through the Redis config file,
By default, the service listens to the localhost. This may have changed if you have since changed the Redis settings. If there are specific IPs you wish to add, you will need to add the address to the config through the same
|
NoSQL
? |
As in accessible via internet as opposed to a private connection. Does it not make sense? |
I would probably say "exposed over the internet" instead for greater clarity. |
Sure- let me update the block now |
Done |
TITLE TL;DR FAQ Because many default configurations of many Redis installations binds on all public network interfaces, there has been countless examples of Redis instances being publicly available over the internet, which in turn has lead to data leaks. If you don't need your Redis installation to be accessible over the network, we recommend that you re-configure Redis to only bind on the loopback/localhost interface to avoid this. If on the other hand you do need your Redis instance to be accessible over the network, we recommend that you create a firewall policy that only allows a select number of servers to talk to the Redis instance, while also setting a Redis password. To reconfigure Redis to only listen on localhost, edit the Redis config file (usually `/etc/redis/redis.conf`) and change the bind option to the following: ``` We would also recommend that you enabling password protection as well. You can do this by adding the following line to your configuration file: ``` Please note that you need to restart Redis in order for the changes to apply. You can do that by running: ``` If you need network access to Redis, you can create a firewall policy using the WoTT Dashboard. By default, Redis uses port 6379/tcp. Code Snippet None for now. |
@fshmcallister subtitle? |
We detected that a {service} instance on {devices} may be accessible remotely. Consider either blocking port {port} through the WoTT firewall management tool, or re-configure {service} to only listen on localhost. Part of #198
The text was updated successfully, but these errors were encountered: