Re: securing MySQL: easiest/best ways?

2012-05-09 Thread Peter Vereshagin
Hello. 2012/05/08 21:51:49 +0100 Matthew Seaman => To freebsd-questions@freebsd.org : MS> data dir shared between two servers. Keeping the configs with the data MS> does have a few advantages. I know yet another reason to do this. In common case this isn't mysql-specific. There may be a 'chr

Re: securing MySQL: easiest/best ways?

2012-05-08 Thread Jerry
On Tue, 08 May 2012 21:51:49 +0100 Matthew Seaman articulated: >On 08/05/2012 20:55, Jerry wrote: >> On Tue, 08 May 2012 15:34:02 +0100 >> Matthew Seaman articulated: >> >>> >Sounds almost as if the my.cnf you've been editing is not the >>> >my.cnf that your mysql instance is using. IIRC there w

Re: securing MySQL: easiest/best ways?

2012-05-08 Thread Andre Goree
On Tue, 08 May 2012 15:55:36 -0400, Jerry wrote: On Tue, 08 May 2012 15:34:02 +0100 Matthew Seaman articulated: Sounds almost as if the my.cnf you've been editing is not the my.cnf that your mysql instance is using. IIRC there was some talk about moving from the usual BSD-ish /var/db/mysql/m

Re: securing MySQL: easiest/best ways?

2012-05-08 Thread Matthew Seaman
On 08/05/2012 20:55, Jerry wrote: > On Tue, 08 May 2012 15:34:02 +0100 > Matthew Seaman articulated: > >> >Sounds almost as if the my.cnf you've been editing is not the my.cnf >> >that your mysql instance is using. IIRC there was some talk about >> >moving from the usual BSD-ish /var/db/mysql/my.

Re: securing MySQL: easiest/best ways?

2012-05-08 Thread Jerry
On Tue, 08 May 2012 15:34:02 +0100 Matthew Seaman articulated: >Sounds almost as if the my.cnf you've been editing is not the my.cnf >that your mysql instance is using. IIRC there was some talk about >moving from the usual BSD-ish /var/db/mysql/my.cnf to >/usr/local/etc/my.cnf (no doubt under som

Re: securing MySQL: easiest/best ways?

2012-05-08 Thread Peter Vereshagin
Hello. 2012/05/08 06:49:01 -0700 Paul Beard => To FreeBSD-questions : PB> Monkeying with IPv6, I discovered that globally routable addresses are what it says on the tin, so hiding behind a network appliance is not longer viable for me. An nmap scan showed the port 3306 was hanging out for all

Re: securing MySQL: easiest/best ways?

2012-05-08 Thread Matthew Seaman
On 08/05/2012 14:49, Paul Beard wrote: > Monkeying with IPv6, I discovered that globally routable addresses > are what it says on the tin, so hiding behind a network appliance is > not longer viable for me. An nmap scan showed the port 3306 was > hanging out for all to see but I couldn't figure ou

securing MySQL: easiest/best ways?

2012-05-08 Thread Paul Beard
Monkeying with IPv6, I discovered that globally routable addresses are what it says on the tin, so hiding behind a network appliance is not longer viable for me. An nmap scan showed the port 3306 was hanging out for all to see but I couldn't figure out how to close it off. The "--skip-networkin