Bug#672359: thanks

2012-05-12 Thread Nicholas Bamber
On 12/05/12 15:11, M. Dietrich wrote: Hi, this is the usual setup, right? a database backend with mysql is contacted remotely... Not always. In a webserver+database stack turning off network access to the database is a security step. But yes you have found a bug in the Debian packaging.

Bug#672359: thanks

2012-05-12 Thread M. Dietrich
Hi, On Sat, May 12, 2012 at 01:15:42PM +0100, Nicholas Bamber wrote: > Okay so the following steps reproduce the issue. > > On machine A: > 1.) install mysql-server > 2.) Edit the bind-address field in /etc/mysql/my.cnf so that machine > B can connect. > 3.) Bounce the server. > 4.) Set up a user

Bug#672359: thanks

2012-05-12 Thread M. Dietrich
hi, On Sat, May 12, 2012 at 12:18:32PM +0100, Nicholas Bamber wrote: > Thanks. So you purged the client side but left the server side. You > removed those files manually. Then it broke. no. i purged everything. i have no server side on that machine. i removed the dir that was created by me manual

Bug#672359: [debian-mysql] Bug#672359: thanks

2012-05-12 Thread Nicholas Bamber
On 12/05/12 14:03, Olaf van der Spek wrote: On Sat, May 12, 2012 at 2:15 PM, Nicholas Bamber wrote: The solution should be to have a file like /etc/mysql/conf.d/.keepme in mysql-common. Isn't there a better way to ensure the dir exists? Well I was thing what conf.d is really for is that

Bug#672359: [debian-mysql] Bug#672359: thanks

2012-05-12 Thread Olaf van der Spek
On Sat, May 12, 2012 at 2:15 PM, Nicholas Bamber wrote: > The solution should be to have a file like /etc/mysql/conf.d/.keepme in > mysql-common. Isn't there a better way to ensure the dir exists? -- Olaf -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#672359: thanks

2012-05-12 Thread Nicholas Bamber
Michael, Okay so the following steps reproduce the issue. On machine A: 1.) install mysql-server 2.) Edit the bind-address field in /etc/mysql/my.cnf so that machine B can connect. 3.) Bounce the server. 4.) Set up a user that could be used from machine B. On machine B: 1.) Make sure that no

Bug#672359: thanks

2012-05-12 Thread Nicholas Bamber
tag 672359 -moreinfo thanks Michael, Thanks. So you purged the client side but left the server side. You removed those files manually. Then it broke. The question is if we install the clients side on its own with the server side on a different machine is everything okay? If not presumably