On Sat, Sep 24, 2005 at 07:35:09PM +0200, Gabor Gombas wrote:
> On Fri, Sep 23, 2005 at 08:01:05PM +0200, Christoph Haas wrote:
> > It appears like MySQL does that. It seems to check the IP address of the
> > connecting client to find the permissions in it's internal `users`
> > table. So it sees "127.0.0.1" and looks up "localhost.localdomain" which
> > it cannot find since it expects "localhost".
> Well, I don't think it's MySQL that expects "localhost", it's more like
> you have added users in the form of "user@localhost" instead of
> "firstname.lastname@example.org". These two forms are _not_ the same as far
> as MySQL is concerned.
> Ok, after a quick googling I found that this bug has already been
> reported for MySQL: http://bugs.mysql.com/11822 and is fixed in MySQL
> 5.0.11. So if it bothers you, you should upgrade.
That's exactly the explanation what I was looking for. I incorrectly
assumed that more than just MySQL is affected. But it appears like other
services do not care about the reverse resolution of 127.0.0.1.
Thank you for your explanation and the references. I'm maintaining a
tutorial for setting up mail servers on Debian. And I wanted to tell the
readers the correct way to handle these MySQL authorization problems.
".signature" [Modified] 3 lines --100%-- 3,41 All