Hi Gerv, Gervase Markham wrote: > How did a discussion about avoiding homograph spoofing turn into a > suggestion that we only allow Latin characters? > Did you follow the thread actually? But I'd suggest we move this discussion to a new thread since it's not related to this inclusion request. > That's entirely unreasonable. We've spent years working on things like > IDN to internationalise the web; That's for domain names, yes. So it's questionable for digital certificates IMO... > why reverse all that for fields in > certificates? I explained it before. Because YOU can't read the subject line /C=ישראל/ST=דרום/O=סטארטקום בע"מ/CN=אדי ניק It's completely useless to you. A passport or international driving license entirely in Hebrew, Arabic, Chinese, Japanese, Russian etc. would be useless as well. However all international ID documents issued by the affected countries have at least an English (Latin) translation included (in addition to the natural language and character set). I view digital certificates as such an international ID document. It should be readable by the majority (as in passports). > There are established methods of checking for homographs - > e.g. the Unicode Consortium TR#36's list of confusables. It's not about confusion or spoofing in relation to domain names, but about the other content of the certificate.
-- Regards Signer: Eddy Nigg, StartCom Ltd. <http://www.startcom.org> Jabber: [EMAIL PROTECTED] <xmpp:[EMAIL PROTECTED]> Blog: Join the Revolution! <http://blog.startcom.org> Phone: +1.213.341.0390 _______________________________________________ dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
