diff options
Diffstat (limited to 'docs')
-rw-r--r-- | docs/Prevent_Tracking.txt | 3 | ||||
-rw-r--r-- | docs/Tox_middle_level_network_protocol.txt | 16 |
2 files changed, 10 insertions, 9 deletions
diff --git a/docs/Prevent_Tracking.txt b/docs/Prevent_Tracking.txt index 86402110..a641f02c 100644 --- a/docs/Prevent_Tracking.txt +++ b/docs/Prevent_Tracking.txt | |||
@@ -119,7 +119,8 @@ announce response packet: | |||
119 | encrypted with the DHT private key of Node D, the public key in the request and the nonce:[[uint8_t is_stored] | 119 | encrypted with the DHT private key of Node D, the public key in the request and the nonce:[[uint8_t is_stored] |
120 | [(32 bytes) ping_id if is_stored is 0 or 2, public key that must be used to send data packets if is_stored is 1][Node_Format * (maximum of 8)]] | 120 | [(32 bytes) ping_id if is_stored is 0 or 2, public key that must be used to send data packets if is_stored is 1][Node_Format * (maximum of 8)]] |
121 | (if the is_stored is not 0, it means the information to reach the client id we are searching for is stored on this node) | 121 | (if the is_stored is not 0, it means the information to reach the client id we are searching for is stored on this node) |
122 | is_stored is 2 as a response to a peer trying to announce himself to tell the peer that he is currently annouced successfully. | 122 | is_stored is 2 as a response to a peer trying to announce himself to tell the |
123 | peer that he is currently announced successfully. | ||
123 | 124 | ||
124 | data to route response packet: | 125 | data to route response packet: |
125 | [uint8_t packet id (134)][nonce][temporary just generated public key] | 126 | [uint8_t packet id (134)][nonce][temporary just generated public key] |
diff --git a/docs/Tox_middle_level_network_protocol.txt b/docs/Tox_middle_level_network_protocol.txt index ff894246..ca561474 100644 --- a/docs/Tox_middle_level_network_protocol.txt +++ b/docs/Tox_middle_level_network_protocol.txt | |||
@@ -43,13 +43,13 @@ cookie request packet: | |||
43 | bytes)][Encrypted message containing: [Senders real public key (32 | 43 | bytes)][Encrypted message containing: [Senders real public key (32 |
44 | bytes)][padding (32 bytes)][uint64_t number (must be sent | 44 | bytes)][padding (32 bytes)][uint64_t number (must be sent |
45 | back untouched in cookie response)]] | 45 | back untouched in cookie response)]] |
46 | Encrypted message is encrypted with sender DHT private key, recievers DHT | 46 | Encrypted message is encrypted with sender DHT private key, receivers DHT |
47 | public key and the nonce. | 47 | public key and the nonce. |
48 | 48 | ||
49 | cookie response packet: | 49 | cookie response packet: |
50 | [uint8_t 25][Random nonce (24 bytes)][Encrypted message containing: | 50 | [uint8_t 25][Random nonce (24 bytes)][Encrypted message containing: |
51 | [Cookie][uint64_t number (that was sent in the request)]] | 51 | [Cookie][uint64_t number (that was sent in the request)]] |
52 | Encrypted message is encrypted with sender DHT private key, recievers DHT | 52 | Encrypted message is encrypted with sender DHT private key, receivers DHT |
53 | public key and the nonce. | 53 | public key and the nonce. |
54 | 54 | ||
55 | The Cookie should be basically: | 55 | The Cookie should be basically: |
@@ -110,11 +110,11 @@ packet request packet: [uint8_t (1)][uint8_t num][uint8_t num][uint8_t | |||
110 | num]...[uint8_t num] | 110 | num]...[uint8_t num] |
111 | 111 | ||
112 | the list of nums are a list of packet numbers the other is requesting. | 112 | the list of nums are a list of packet numbers the other is requesting. |
113 | to get the real packet numbers from this list take the recvbuffers buffer_start | 113 | to get the real packet numbers from this list take the recvbuffers buffer_start |
114 | from the packet, substract 1 to it and put it in packet_num then start from the | 114 | from the packet, subtract 1 to it and put it in packet_num then start from the |
115 | beggining of the num list: if num is zero, add 255 to packet_num then do the | 115 | beginning of the num list: if num is zero, add 255 to packet_num then do the |
116 | next num. if num isn't zero, add its value to packet_num, note that the other | 116 | next num. if num isn't zero, add its value to packet_num, note that the other |
117 | has requested we send this packet again to them then continue to the next num in | 117 | has requested we send this packet again to them then continue to the next num in |
118 | the list. | 118 | the list. |
119 | 119 | ||
120 | 120 | ||