Bug#664846: skip name resolving

2012-07-16 Thread Bjoern Boschman 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Nicholas,

my mysql.user table still includes 'user'@'%' records.

- From 8.9.8 I can read the following:

To disable DNS host name lookups, start the server with the
- --skip-name-resolve option.

This in my ears sound like: disable any gethostbyaddr/gethostbyname
requests no matter what. But it still uses these system calls (what
can be seen in tcpdump or similar)

Any wildcard name based GRANTS (e.g. 'user'@'%.foo.com') are no longer
supposed to work, but IP wildcard GRANTS (e.g. 'user'@'192.168.0.%')
must still work.

Cheers
B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAD7kYACgkQABMWRpwdNumaogCgxBwkRRU+xZH4lQxCu84TFys9
JQAAn0mX8VbvkigNf5RnvPzcd6BtxQGX
=QqJC
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#664846: skip name resolving

2012-07-07 Thread Nicholas Bamber 
Bjoern,
Can I just check that all the Host values in your mysql.user table are
IP addresses or localhost. I wonder if this also precludes '%'. Of
course it could raise the question of what the option actually does.

 --skip-name-resolve

Do not resolve host names when checking client connections. Use only IP
addresses. If you use this option, all Host column values in the grant
tables must be IP addresses or localhost. See Section 8.9.8, “DNS Lookup
Optimization and the Host Cache”.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org