Date: Wed, 25 Jun 2014 17:31:24 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: Polytropon <freebsd@edvax.de> Cc: Outback Dingo <outbackdingo@gmail.com>, freebsd-questions@freebsd.org, Bernt Hansson <bah@bananmonarki.se> Subject: Re: server funding Message-ID: <20140625103124.GA66527@admin.sibptus.tomsk.ru> In-Reply-To: <20140625121617.a72bc88c.freebsd@edvax.de> References: <53A994C7.7080308@tysdomain.com> <20140625073142.GA60979@admin.sibptus.tomsk.ru> <53AA85F3.9080305@bananmonarki.se> <20140625084357.GB62939@admin.sibptus.tomsk.ru> <CAKYr3zwSf4hqmMYzoCxo6MY88fxx9xXMcGWJ2h5o_31gVDPPGA@mail.gmail.com> <20140625092520.GA64543@admin.sibptus.tomsk.ru> <20140625114114.1345527e.freebsd@edvax.de> <20140625100231.GA65737@admin.sibptus.tomsk.ru> <20140625121617.a72bc88c.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Polytropon wrote: > And now take into mind that Unicode characters can also be > used, so http://??y.F????????bS??/ isn't far away. And think about > all the funny attack vectors enabled by "similarly looking", > but actually different URLs... ;-) Usually there are some provisions and transformation rules approved by ICANN to minimize this risk. I can speak for .ÒÆ only (AKA xn--p1ai), there are no permitted characters other than a restricted set of Cyrillic. You cannot have some e.g. Greek or even Latin character in this Cyrillic-only domain name, i.e. you cannot replace U+043E (cyrillic small letter "o") with an ascii "o". -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140625103124.GA66527>