Changeset 4fd8da8


Ignore:
Timestamp:
May 24, 2011 10:33:28 PM (9 years ago)
Author:
kytv <kytv@…>
Branches:
master
Children:
641e71c
Parents:
68dccdf
Message:

Fix errors that tests/scripts/checkxml.sh found

Files:
7 edited

Legend:

Unmodified
Added
Removed
  • core/java/src/net/i2p/client/package.html

    r68dccdf r4fd8da8  
    2020
    2121<p>This client package provides the basic necessity for communicating over I2P,
    22 but there are three other subpackages that are helpful.  Specifically:<ul>
     22but there are three other subpackages that are helpful.  Specifically:</p><ul>
    2323<li>{@link net.i2p.client.datagram} - for applications that want their messages
    2424    to be both authenticated and repliable</li>
     
    2929    the streaming library is packaged seperate from the main SDK - in the
    3030    mstreaming.jar and streaming.jar)</li>
    31 </ul></p>
     31</ul>
    3232
    3333<p>The {@link net.i2p.client.I2PSession} implementation itself communicates with
  • installer/resources/eepsite.help/help/index.html

    r68dccdf r4fd8da8  
    4646 <li>Pick a name for your eepsite (<i>something</i>.i2p). Use all lower-case.
    4747     You may wish to check first in your own router's address book
    48      <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&filter=none">here</a>,
     48     <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&amp;filter=none">here</a>,
    4949     or the file <code>i2p/hosts.txt</code> to see if your name is already taken.
    5050     Enter the new name for your eepsite on the
  • installer/resources/eepsite.help/help/index_de.html

    r68dccdf r4fd8da8  
    114114</ol>
    115115
    116 <h4><a name="AnkerDEOeA" id="AnkerDEOeA"></a>3. Die Eepseite öffentlich ankündigen</h4>
     116<h4><a name="AnkerDEOeA"></a>3. Die Eepseite öffentlich ankündigen</h4>
    117117
    118118<ul>
     
    184184besteht.
    185185</p><p class="footnote"><a class="footnum" name="fn.2" href="#fnr.2">2.</a> Anmerkung: Wenn dieses Vorgehen mit der Fehlermeldung „Invalid nonce. Are you being spoofed?“ quittiert wird, müssen <em>Cookies</em> im Browser erlaubt werden. Ist dies nicht möglich, können Sie mit einem Editor die Datei <em>„i2p/userhosts.txt“</em> bearbeiten und so die Adressen einfügen. <a href="http://sperrbezirk.i2p/Konqueror_Susi.html">Konqueror</a> ist etwas eigenwillig.
    186 </p><p class="footnote"><a class="footnum" name="fn.3" href="#fnr.3">3.</a> Gleiches wie unter <sup><a class="footref" name="fnr.2" href="#fn.2">2</a></sup> gilt für <em>„i2p/addressbook/subscriptions.txt“</em>.</p>
     186</p><p class="footnote"><a class="footnum" name="fn.3" href="#fnr.3">3.</a> Gleiches wie unter gilt für <em>„i2p/addressbook/subscriptions.txt“</em>.</p>
    187187
    188188<div class="notify">
  • installer/resources/eepsite.help/help/index_fr.html

    r68dccdf r4fd8da8  
    4545 <li>Choissisez un nom pour votre eepsite (<i>quelquechose</i>.i2p). Tout en minuscule.
    4646     D'abord, vérifiez dans le carnet d'adresse de votre router
    47      <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&filter=none">ici</a>,
     47     <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&amp;filter=none">ici</a>,
    4848     ou dans le fichier <code>i2p/hosts.txt</code> pour voir si le nom a déjà été pris.
    4949     Entrez le nouveau nom de votre eepsite sur le
  • installer/resources/eepsite.help/help/index_nl.html

    r68dccdf r4fd8da8  
    4747 <li>Kies een naam voor je eepsite (<i>mijnsite</i>.i2p). Gebruik alleen kleine letters.
    4848     Kijk eerst
    49      <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&filter=none">hier</a>,
     49     <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&amp;filter=none">hier</a>,
    5050     in het adresboek van je router of in het bestand <code>i2p/hosts.txt</code> of de naam nog beschikbaar is.
    5151     Voer de nieuwe naam voor je eepsite in op de
  • installer/resources/eepsite.help/help/index_ru.html

    r68dccdf r4fd8da8  
    4141 
    4242<ul>
    43 <li>Выберите имя для своего сайта (<i>something</i>.i2p). Используйте только символы в нижнем регистре. Загляните в <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&filter=none">адресную книгу</a> Вашего маршрутизатора или в файл <code>i2p/hosts.txt</code> для проверки, возможно такое имя уже кто-то занял. Введите новое имя Вашего сайта на <a href="http://127.0.0.1:7657/i2ptunnel/edit.jsp?tunnel=3">странице настроек туннеля для i2p-сайта</a> в поле «Имя веб-сайта». Это заменит имя сайта по умолчанию «mysite.i2p». Поставьте галочку «Автозапуск». Ваш сайт будет доступен извне всегда, когда запущен Ваш маршрутизатор. Не забудьте нажать «Сохранить».
     43<li>Выберите имя для своего сайта (<i>something</i>.i2p). Используйте только символы в нижнем регистре. Загляните в <a href="http://127.0.0.1:7657/susidns/addressbook.jsp?book=router&amp;filter=none">адресную книгу</a> Вашего маршрутизатора или в файл <code>i2p/hosts.txt</code> для проверки, возможно такое имя уже кто-то занял. Введите новое имя Вашего сайта на <a href="http://127.0.0.1:7657/i2ptunnel/edit.jsp?tunnel=3">странице настроек туннеля для i2p-сайта</a> в поле «Имя веб-сайта». Это заменит имя сайта по умолчанию «mysite.i2p». Поставьте галочку «Автозапуск». Ваш сайт будет доступен извне всегда, когда запущен Ваш маршрутизатор. Не забудьте нажать «Сохранить».
    4444
    4545<li>Кликните <a href="http://127.0.0.1:7657/i2ptunnel/index.jsp">в менеджере туннелей</a> на кнопке запуска вашего сайта. Вы должны увидеть запись «i2p-сайт» в списке «Локальные туннели» в левой части <a href="http://127.0.0.1:7657/index.jsp">консоли маршрутизатора</a>. С этого момента Ваш сайт запущен.
  • router/java/src/net/i2p/data/i2np/package.html

    r68dccdf r4fd8da8  
    88does not specify or require any particular transport layer, allowing transport protocols
    99to work over TCP, Polling HTTP, SMTP+POP3/IMAP, UDP, among anything else
    10 that can pass data. I2NP merely requires that they:
     10that can pass data. I2NP merely requires that they:</p>
    1111<ul>
    1212<li>
    1313Register a unique identifier for use in RouterAddress structures consisting of no
    14 more than 32 UTF-8 characters.
     14more than 32 UTF-8 characters.</li>
    1515<li>
    1616Define standard text based options that uniquely define a contact method (for
    1717example .hostname. and .port. or .email address.) as usable in the
    18 RouterAddress structure's set of options.
     18RouterAddress structure's set of options.</li>
    1919<li>
    2020Provide a means to reliably deliver a chunk of data, where the contents of any
    2121particular chunk is delivered in order. However, different chunks of data do not
    22 need to be delivered in order.
     22need to be delivered in order.</li>
    2323<li>
    2424Secure the chunks of data from alteration or disclosure (e.g. encrypt them and use
    25 checksums).
     25checksums).</li>
    2626<li>
    27 Enable the router to control the transport's bandwidth usage.
     27Enable the router to control the transport's bandwidth usage.</li>
    2828<li>
    2929Provide estimates for the latency and bandwidth associated with passing a chunk of
    30 data.
     30data.</li>
    3131<li>
    32 Provide a programmable interface suitable for integration with various routers.
     32Provide a programmable interface suitable for integration with various routers.</li>
    3333</ul>
    34 </p>
    3534<p>
    3635Transports themselves can implement advanced features, such as steganography,
     
    5756tunnel, where it is passed along again to that tunnel's end point and made available to
    5857the target for reception. To understand fully, each step in the process must be
    59 explained in detail.
     58explained in detail.</p>
    6059<ul>
    6160<li>
    6261First, once the originating router receives the message and the Destination, it
    6362attempts to find the LeaseSet associated with it as stored in the Network Database
    64 under the key calculated by SHA256 of the Destination.
     63under the key calculated by SHA256 of the Destination.</li>
    6564<li>
    6665The router then builds a GarlicMessage addressed to the SHA256 of the
     
    7271body of the GarlicMessage with all enclosed GarlicCloves is encrypted to the key
    7372specified on the LeaseSet using the ElGamal+AES256 algorithm described in the
    74 data structure spec.
     73data structure spec.</li>
    7574<li>
    7675The router then selects one or more outbound tunnels through which the
    77 GarlicMessage will be delivered.
     76GarlicMessage will be delivered.</li>
    7877<li>
    7978Then the router selects one or more of those Lease structures from the LeaseSet
    8079and constructs a TunnelMessage along with DeliveryInstructions for the
    8180outbound tunnel's end point to deliver the GarlicMessage to the inbound tunnel's
    82 gateway router.
     81gateway router.</li>
    8382<li>
    8483The source router then passes the various TunnelMessages down the outbound
    8584tunnel to that tunnel's end point, where the instructions are decrypted, specifying
    86 where the message should be delivered.
     85where the message should be delivered.</li>
    8786<li>
    8887At this point, the end point must determine how to contact the router specified in
    8988the decrypted DeliveryInstructions, perhaps looking up RouterInfo or
    9089LeaseSet structures in the Network Database, and maybe even delaying a
    91 requested period of time before passing on the message.
     90requested period of time before passing on the message.</li>
    9291<li>
    9392Once the tunnel end point has the data it needs to contact the inbound tunnel's
     
    9594RouterAddress or source routed through one of its published trusted peers. Over
    9695this medium the tunnel end point delivers the GarlicMessage as it was wrapped by
    97 the source router, along with the TunnelId.
     96the source router, along with the TunnelId.</li>
    9897<li>
    9998Once delivered to the inbound tunnel's gateway, the gateway builds a
    10099TunnelMessage wrapping the GarlicMessage, encrypting a
    101100DeliveryInstructions to specify local delivery upon arrival at the tunnel's end
    102 point.
     101point.</li>
    103102<li>
    104103Once the TunnelMessage is passed down to the end point in inbound tunnel, the
     
    106105and then proceeds to review the contents of the TunnelMessage's payload, which in
    107106this case is a GarlicMessage addressed to the SHA256 of a LeaseSet that it has
    108 published. It then decrypts the payload of the message with ElGamal + AES256.
     107published. It then decrypts the payload of the message with ElGamal + AES256.</li>
    109108<li>
    110109After opening up the GarlicMessage, it reviews each of the GarlicCloves and
     
    113112for local processing (e.g. Network Database messages or DeliveryStatusMessages)
    114113are processed, and cloves asking for forwarding to other routers are passed off for
    115 delivery.
     114delivery.</li>
    116115</ul>
    117116<p>
Note: See TracChangeset for help on using the changeset viewer.