1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-EDA831F7-7248-5C00-B6BE-B7F44097C9B6" xml:lang="en"><title>WhiteList/BlackList

    13 TLD Services Overview</title><shortdesc>This document introduces the Whitelist/Blacklist Top-Level Domain

    14 services of the InetURIList framework. </shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>

    15 <p>International domain names support increases the vulnerability of the device

    16 to homograph attacks (also called phishing), by allowing addresses (URIs)

    17 to contain UTF-8 characters. By using non-ASCII characters that are visually

    18 similar to familiar letters, attacks can lead the Internet user to harmful

    19 sites. </p>

    20 <p>To address this issue, the InetURIList framework provides a list of suspect

    21 characters (a BlackList) for each top-level domain (TLD). The framework also

    22 lists trusted characters in TLD-specific WhiteLists. This enables applications

    23 to detect safe and unsafe URIs depending on their top-level domain and the

    24 characters they contain. </p>

    25 <p>The Blacklists and Whitelists are stored in an XML file installed on the

    26 device. You can replace the default TLD policy file by installing an SIS package

    27 containing the updated lists. </p>

    28 <p>Applications can query the TLD list but cannot dynamically change its contents. </p>

    29 </conbody><related-links>

    30 <link href="GUID-E97C2A7E-8E8F-58E6-99D4-288589385B44.dita"><linktext> Querying

    31 the TLD policy data </linktext></link>

    32 <link href="GUID-AC4C18D1-D6A3-5988-AB10-5A5025183950.dita"><linktext> Modifying

    33 the TLD policy data</linktext></link>

    34 <link href="GUID-6A78F618-09A9-56A7-8C58-98C353BF0788.dita"><linktext>What is the

    35 Domain Name Server?</linktext></link>

    36 </related-links></concept>