Re:The most important ICANN announcement: Introduction of no...
by antiform on Tuesday July 08, 2008 @04:39PM
(#240327)
This is actually a browser issue, and was anticipated long before. A valid workaround would be to allow for input in Unicode, but display the url output in Punycode.
I'm pretty sure most popular browsers already account for this vulnerability. At the very least, Mozilla-forked browsers should still have a built-in defense against homograph attacks. [https://bugzilla.mozilla.org/show_bug.cgi?id=279099#c135]
Re:The most important ICANN announcement: Introduction of no...
by greyman on Tuesday July 08, 2008 @04:10PM
(#240285)
I am with you. In my mother language, there are also a few characters which have special small signs above them, but I still think using them in URL will be a disaster. Websites which have such characters in their names will be forced to register both names (with and without special chars)...or...maybe that's the point?!
How can you distinguish between Latin o and Cyrillic o?