[Latingp] For IP:.Re: From IP: Diacritics below a security risk?

Fri Sep 21 06:51:36 UTC 2018

Thank you Mirjana and Latin GP members.  

The message has been shared with the IP members. 

I will share their feedback, once it is available.

Regards,
Sarmad

From: Mirjana Tasić <Mirjana.Tasic at rnids.rs> 
Sent: Friday, September 21, 2018 12:57 AM
To: Sarmad Hussain <sarmad.hussain at icann.org>; Latin GP <latingp at icann.org>
Subject: [Ext] For IP:.Re: [Latingp] From IP: Diacritics below a security risk?

Dear IP,

Please find enclosed the response of Latin GP to your letter “Diacritics below a security risk?”.

Latin GP cannot give the direct answer to your letter in this turn. Latin GP will appreciate very much if you could help us to clarify the questions we are discussing in our document  sent as attachment in this message.

We shall have face to face meeting in Brussels from October the 1st for three days. Your response to this document could help us to be more efficient and finalize our work.

 It would also help us to provide a better response to your question about diacritics.

Best regards

Mirjana Tasic

From: Latin GP <latingp-bounces at icann.org <mailto:latingp-bounces at icann.org> > on behalf of Sarmad Hussain <sarmad.hussain at icann.org <mailto:sarmad.hussain at icann.org> >
Date: Wednesday, August 29, 2018 at 08:58
To: Latin GP <latingp at icann.org <mailto:latingp at icann.org> >
Subject: [Latingp] From IP: Diacritics below a security risk?

Dear Latin GP members  

Kindly find below some feedback from IP for your consideration.

Regards 

Sarmad 

TO: LatinGP
FROM: IP

There are recent and widely published examples of phishing attacks using Latin IDNs in which the key features involved were diacritics below the letter. Here is an example:

Of all diacritics, diacritics below can be difficult to distinguish or be prone to clipping -- there is less space below the baseline than between the typical lowercase glyph and the top of the line.

The example given above shows a further interaction with URL underlining - and not all display engines actually do as nice a job interrupting the underline as in the screen shot above. For example, here is how one system will render this (using a designated UI font - Segoe UI):

Note, this code point (U+1E33) is in the MSR as is (U+1E35 LATIN SMALL K WITH LINE BELOW).

The second example contains U+1E35 --  while the effect does not show equally at all type sizes, from 12pt and below the LINE BELOW is reliably hidden. Here are the two examples at 10pt

The issue is not limited to "K". We see "B", "D", "L" and "N" with both DOT and LINE BELOW and "M" and "H" with DOT BELOW, all on the same page in the MSR.

It can be argued users have no working understanding of typography and would not reliably interpret small gaps or bulges in the underline as being related to an unfamiliar code point. This appears to make all diacritics below security-sensitive, however, the initial determination belongs to the relevant GPs.

Note by the way that the Devanagari LGR treats sequences containing NUKTA (a dot below) as variants in at least some cases and recent community comments for that script are calling for more variant sequences. However, while the feature is graphically analog (dot below), each script works differently and there is no single a-priori solution.

The IP would like to encourage the LatinGP (and any other GP facing cases like this) to explicitly examine this example and other cases like it, where code points can become indistinguishable in common usage scenarios for IDNs, and formally conclude whether and how to take these into account when designing their LGR.

At this point, the IP would expect the GP to:

* explicitly discuss this and other scenarios like it

* evaluate whether they constitute a security risk to the Root Zone

* come up with a reasoned decision as to whether and how to address them in the design of the Latin GP; and finally

* document both the decision and its rationale.

In coming to a decision, the GP may resolve:

1) to make them variants

2) to list them for attention as confusable

3) to take no action, because the GP feels that they do not represent a special security risk.

As part of the review of the Latin LGR, the IP will look at the background and rationale offered by the Latin GP in coming to its conclusion; note that if the IP feels that the facts considered and rationale documented do not support the conclusion reached by the GP it may raise objections at that time.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180921/88d21497/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 131067 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180921/88d21497/image001-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 878 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180921/88d21497/image002-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 939 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180921/88d21497/image003-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 777 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180921/88d21497/image004-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5026 bytes
Desc: not available
URL: <http://mm.icann.org/pipermail/latingp/attachments/20180921/88d21497/smime-0001.p7s>