| NNPand i was doing this 6 months before bram had even dreamed of bittorrent
you tell me what its like
and how safe it would have been back then compared to BT
Nice lil white paper to work on:
Was good enough that before there was encryption in both Azureus and utorrent
i made sourceforge project and told both utorrent and azureus project people that if they didnt i would add a better encryption layer and do my app
The Neural Network Protocol
*Each computer in the network is open on port 1000. This is a constantly streaming, one-way connection that broadcasts IP's of computers in the network that are accepting connections on port 1000.
(1)
**** "realign" (so next byte=start of an IP address) every 10 ip's...
(2) following 6 byte sequence byte1,byte2,byte3,byte4,ttl,x,day
--bytes 1-4 are the ip address
--TTL is the "Time To Live," or how many hosts have forwarded this
IP address. If TTL >5 clients may either discard, or if they
can connect, set to zero.
--(X *337.5) = seconds since midnight in greenwich.
-- day in hte month.
To logon the network, a computer establishing secure connections to 40 other computers in the network, using hte proceeding protocols.
--------
-Port 1001 is used to establish encrypted connections on port 1002.
Client may issue these commands on port 1001:
USER ( handle) <---login to server
FORWARDING (key) for (handle) <---forwarding a key for (handle)
FORWARD (key) to (IPaddress)
SEAL 10,15,9
eg: use XOR of keys 10,15, and 9 for key of port 1002**
**(adlib not the SEAL may have preordained scrambing aka encryption)
Server may issue these commands may issue these commands on port 1001:
Recieved key##, checksum,check_sum_algorithm_used
Once "Seal" command is sent , hte client drops port 1002 connection and reconnects. This is to avoid any TCP/IP-lag-related confusion over what data was sent with what keycode.
------
Port 1002 commands
ESTABLISH (keynumber),(key) to send an encryption key over an already
encrypted connection. Double headache for
gov't , riaa etc.
------
Any two hosts may "spider out" over the network until paths are found between them. ( each computer in network is connected to about 40 computers [ could be more if the server aka this form of tracker could handle it and idea of user ended servering and client use would then preclude need for a centralized server and thus create a massive encrypted network with NO ip's only ids.])
The following commands can be issued on Port 1002:
"I have route to" (handle) (ttl)"
"I have route to" (handle) (ttl)"
etc ... up to total of 40 times.
TTL starts at zero. For the first three transfers, it is randomly bounced around the network in an unpredictable mannr, without braching out. Each will then begin branching out a minimum of the next two hops, and if plenty of bandwidth is available to intermediary computers, even further(This way, nobody can floodthe network to thepoint it quits working. It will just reduce the max TTL allowed. )
Each computer will remmber which other coputers sent it "I have route to" or "I need a route to" commands, so that this route may be used.
--------
Once any computer receives "I have a route to" and "I need a route to" commands, it will send in both directions.
routefound to ( handle)
--------
Now many routes have been established between two computers, by jumping through unknown servers in the middle. Keys may be forwarded in this way:
forward (key) to (handle)
If a key is successfully sent and keeps its checksum ( an unpredictable checksum algorithm is used between client and server, to make tampering impossible ), then it can also be used for the port 1002 secure connection.
-------
The following is a short description of "Ultra Secure" transfer MODE:
1) open connection to host. Forward 10 keys through ten comuters in the network.
2)Use your secure connection to send an encryption key.
3) Re-establish connection, securing it with the keys from 1 and 2 above.
Repeat every 5 minutes.
|
