Don't expose our OpenLDAP user management server to the public internet #80

New issue

Closed

opened 2021-12-20 22:43:52 +00:00 by a · 1 comment

a commented

2021-12-20 22:43:52 +00:00

Owner

Currently, we have port 389 which is used by OpenLDAP exposed to the internet, so that the hostname matches the one in the TLS certificate and so we can use the OpenLDAP server with a possible future VPS (for exovpn for instance). However, it's probably not good for security to export port 389 so one possible solution could be to resolve exozy.me to localhost in the /etc/hosts file.

Currently, we have port 389 which is used by OpenLDAP exposed to the internet, so that the hostname matches the one in the TLS certificate and so we can use the OpenLDAP server with a possible future VPS (for exovpn for instance). However, it's probably not good for security to export port 389 so one possible solution could be to resolve `exozy.me` to `localhost` in the `/etc/hosts` file.