-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2017-03-21 07:22, Marcus Meissner wrote:

On Tue, Mar 21, 2017 at 07:03:51AM +0300, Andrei Borzenkov wrote:

...

Inspired by recent discussion on users list.

BIND can be built with idnkit to support non-ASCII domain names. As far as I can tell, bind comes with copy of idnkit in contrib and our package even builds and installs it, but as packaged bind itself does *not* use this library during build.

Is it intentional? Today non-ASCII domains are increasingly more common.

Which openSUSE? Tumbleweed?

Not intentional. The last upgrade might have unintentionally disabled it.

Leap 42.2: cer@minas-tirith:~> ping ?????????.?? ping: unknown host ?????????.?? cer@minas-tirith:~> ping $(idn ?????????.??) PING xn--d1abbgf6aiiy.xn--p1ai (95.173.136.80) 56(84) bytes of data. ^C - --- xn--d1abbgf6aiiy.xn--p1ai ping statistics --- 22 packets transmitted, 0 received, 100% packet loss, time 21113ms cer@minas-tirith:~> - -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAljRMHcACgkQja8UbcUWM1zg5wD/bYQAnOWCmGg00kAeopoKZEJ4 jRQEQoT7v9X8wBmgs4AA/A6mE8T8sN/7HXXxdKahS/vHJ7M5tT043AOV8shHJj14 =yErf -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Mar 21, 2017 at 10:53 AM, Carlos E. R. wrote:

cer@minas-tirith:~> ping ?????????.?? ping: unknown host ?????????.??

Yes, ping does not parse idn hostnames, this post is about BIND related tools. ping makes no use of them. To fix ping: - Port it to use unprivileged ICMP sockets. so the binary is no longer ever running with elevated capabiltiies (cap_net_raw in current products, setuid root in other releases) and the risk of linking another library (in this case idnkit or whatever) is lowered. - make it understand IDN with such library. - profit :-) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, Mar 21, 2017 at 07:22:43AM +0100, Marcus Meissner wrote:

On Tue, Mar 21, 2017 at 07:03:51AM +0300, Andrei Borzenkov wrote:

...

Inspired by recent discussion on users list.

BIND can be built with idnkit to support non-ASCII domain names. As far as I can tell, bind comes with copy of idnkit in contrib and our package even builds and installs it, but as packaged bind itself does *not* use this library during build.

Is it intentional? Today non-ASCII domains are increasingly more common.

Which openSUSE? Tumbleweed?

Not intentional. The last upgrade might have unintentionally disabled it.

I opened https://bugzilla.suse.com/show_bug.cgi?id=1030306 Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Andrei Borzenkov wrote:

On Tue, Mar 21, 2017 at 4:53 PM, Carlos E. R.

...

Leap 42.2:

cer@minas-tirith:~> ping ?????????.??

This is about utilities provided by ISC BIND project, not about ping.

---- If bind was built with a idnkit library, wouldn't ping automatically benefit -- i.e. it could pass a non-ascii name to bind and have it resolve? AFAIK, wouldn't ping just pass whatever bytes are on the cmdline to be looked up by bind? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org