Remote MySQL Connection
9 Replies
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 localhost:mysql *:* LISTEN
tcp 0 0 localhost:874 *:* LISTEN
tcp 0 0 *:sunrpc *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 localhost:smtp *:* LISTEN
tcp6 0 0 [::]:www [::]:* LISTEN
tcp6 0 0 [::]:ssh [::]:* LISTEN
udp 0 0 *:bootpc *:*
udp 0 0 *:sunrpc *:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 11272 /var/run/mysqld/mysqld.sock
I assumed that you wanted me to run "netstat -l"
And no, I don't have a firewall running.
Thanks!
Just put a # in front of this to comment it out and restart MySQL.
This setting is forcing it to listen only on localhost.
The my.cnf might be in a different location.
I'm not going to lecture much but running without a firewall or connecting to MySql remotely like this is a big security risk, but I am also paranoid.
And with the security thing, I would be more careful but I'm not doing anything that is important. This is just for fun for me. If this was my job or something, I would take security more seriously.
Thanks for your help so far.
I have never connected remotely so I do not know what to do, but that might be the next place to look.
Google for mysql remote root and try the first result.
Before I started using VPS I've used a lot of major shared hosts where your mysql server was mysql.domain.com, and usually tied to another IP (since it sat on their dedicated mysql servers).
If you have it open to listen on outside connections, and you know there's only one, maybe even two other IPs that are going to be connecting to MySQL and you firewall off everything outside of those addresses, I don't see where the risk lies?
I mean the obvious is that if there's no potential to connect to it at all, it is definitely more secure. But if you properly set your firewall…