Re: Non-ASCII in DNS queries
From: Eugene Gershnik (gershnik_at_hotmail.com)
Date: 03/18/04
- Next message: Eugene Gershnik: "Re: loopback interface/Firewall/Winsock"
- Previous message: Ken Spreitzer: "Re: Help with WpPost or WpWiz"
- In reply to: Gary Krall: "Re: Non-ASCII in DNS queries"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 18 Mar 2004 01:36:36 -0800
Gary Krall wrote:
> Eugene:
>
> Hmmm...a Windows machine will always send the DNS query as
> xn--sgard-lra.no to the DNS server if it is being used within an IDNA
> supported application such as Netscape 7.1+, Opera 7.2+, Safari 1.2+,
> SmartFTP, and Internet Explorer through i-Nav (to name a few). I am
> unclear as to why you think Windows is stripping off the "xn-"
> portion of the address. Windows Sockets is rather dumb in this
> regard and to my knowledge it does not make the type of decisions you
> are talking about. It would rely on the client application layer to
> make these kinds of changes before sending the query.
I was talking about the registration not the query. When you name a Windows
machine during the setup (or afterwards) the actual DNS name will be as I
described. Quite surprising for a user.
As for various browser plugins they are fine but this thing really ought to
be done by Winsock. There are many non-browser clients and if they don't
work while browser does this will drive user crazy. Imagine not being able
to ftp but being able to browse.
> In your example, cnn.com (U+0063 U+006E U+006E) will always be an
> ASCII address. The Russian form, ?nn.com (U+0441 U+006E U+006E) will
> be converted by the IDNA application to its Punycode counterpart
> during transport or xn--nn-nmc.com.
The user will see www.cnn.com in the address field of his browser. The
resultant IDN name is invisible to him. One more way for social engineering.
> There are obviously all kinds of
> complaints related to this especially as it relates to overlapping
> Cyrillic and Latin characters, but the standard is published and
> client applications are starting to support it.
Maybe. It doesn't make I18Nized DNS names a good idea though.
-- Eugene
- Next message: Eugene Gershnik: "Re: loopback interface/Firewall/Winsock"
- Previous message: Ken Spreitzer: "Re: Help with WpPost or WpWiz"
- In reply to: Gary Krall: "Re: Non-ASCII in DNS queries"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
