I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

secure DNT node ID info

Browse Source
This commit is contained in:
zzz
2012-08-05 16:57:59 +00:00
parent 2135740dd0
commit ff23666b04
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
www.i2p2/pages/bittorrent.html
View File

@ -1,7 +1,7 @@
{% extends "_layout.html" %}
{% block title %}Bittorrent over I2P{% endblock %}
{% block content %}
Updated May 2012, current as of router version 0.9
Updated August 2012, current as of router version 0.9.1
<p>There are several bittorrent clients and trackers on I2P.
@ -220,7 +220,7 @@ Queries use I2CP protocol number 17.
In addition to that UDP port, we use a second datagram
port equal to the query port + 1. This is used to receive
unsigned (raw) datagrams for replies, errors, and announces.
This port provides increased efficiency sine replies
This port provides increased efficiency since replies
contain tokens sent in the query, and need not be signed.
We call this the "response port".
This is the "rport" value from the extension message.
@ -239,6 +239,12 @@ In a response, the "nodes" key is a
single byte string with concatenated compact node info.
</p>
<p>
Secure node ID requirement: To make various DHT attacks more difficult,
the first 4 bytes of the Node ID must match the first 4 bytes of the destination Hash,
and the next two bytes of the Node ID must match the next two bytes of the
destination hash exclusive-ORed with the port.
</p>
<p>
In a torrent file,
the trackerless torrent dictionary "nodes" key is TBD.
It could be a list of