[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [idn] Fwd: Slash-like mark problem

To: James Seng <jseng@pobox.org.sg>
Subject: Re: [idn] Fwd: Slash-like mark problem
From: William Tan <wil@dready.org>
Date: Sun, 20 Feb 2005 22:53:20 +1100
Cc: IETF idn working group <idn@ops.ietf.org>
In-reply-to: <990a895c69218e44e321a0bd88dc8ea1@pobox.org.sg>
References: <990a895c69218e44e321a0bd88dc8ea1@pobox.org.sg>
User-agent: Mozilla Thunderbird 1.0 (Windows/20041206)

this was demostrated to me just now. basically, the problem is U+2215, a slash-like mathematical symbol.

This makes a strong case for application-level filtering. AMC's blacklist will fail here, as any TLD can be used to exploit this. Apps will have to start detecting character properties such as symbol and punctuations (which I guess would be allowed by some TLD's IDN roll-out including VGRS's).

wil.
[gone phishing with U+2215]

Follow-Ups:
- Re: [idn] Fwd: Slash-like mark problem
  - From: "Adam M. Costello" <idn.amc+0@nicemice.net.RemoveThisWord>

References:
- [idn] Fwd: Slash-like mark problem
  - From: James Seng <jseng@pobox.org.sg>

Prev by Date: Re: [idn] quick & dirty (but not too dirty) homograph defense
Next by Date: Re: [idn] Fwd: Slash-like mark problem
Previous by thread: [idn] Fwd: Slash-like mark problem
Next by thread: Re: [idn] Fwd: Slash-like mark problem
Index(es):
- Date
- Thread