Re:The perils of internationalized domain names
by pjscott on Friday September 24, 2010 @06:03PM
(#1725595)
I still think that supporting Unicode in domain names is asking for trouble. Don't believe me? Just wait until a few thousand people get suckered into giving their credit card information to "amazοn.com". That's amazοn with a lower-case omicron, not an O. A workaround for this, used by Safari and probably others, is for the browser to only display the ASCII-encoded versions of the URLs -- in this case, "xn--amazn-uce.com" -- but that defeats the purpose of having Unicode in your DNS in the first place.
[ Parent
| on HN ]
Re:The perils of internationalized domain names
by avar on Friday September 24, 2010 @08:19PM
(#1725902)
Browsers are already aware and defending against this: http://en.wikipedia.org/wiki/IDN_homograph_attack#Defending_...
Re:The perils of internationalized domain names
by sukuriant on Friday September 24, 2010 @07:49PM
(#1725828)
I was going to say something precisely to this effect, but you already hit the nail on the head. Given enough time, the odds of something like that happen will approach 1; and, suspecting how people that create frauds work, this won't take long to happen, either.
Looks like it's going to become more important than ever to not only check for the " https:// " but also click on it to be sure it's from the source you trust. --- until Verisign is replaced with the unicode look-alike to itself.