Quote:
Originally posted by veniamin
Well you are right but why dont make it a little bit harder for them.
In some packets there is an IP and a PORT, IP is 4 bytes long and PORT is 2 bytes. My thought is to take the actuall ip ort and encrypt it. The encrypted result should be 6 bytes so that we can put the first 4 bytes into the IP field and the last 2 bytes at the PORT field.
Servents dont have to encrypt/decrypt the packets all the time but only when it is neseccery ex: when we want to make a connection or download a file. I remind you that no ips should be exported visually in any servant. So the servants keep the encrypted data somewhere stored and when it needs an ip it decrypts it. The problem with this method is which encryption method should be used, what would be the password for the encryption, and finally that users with some knowledge of computers can still find an IP but ONLY for a connected servant. For example you can make a search for "faithless .mp3" and receive many query hits but you dont know which user shares what. Only when you try to download a file you can find that the user you are connected to is sharing this specific file and not a list of "illegal" files.
Old clients that dont support this method are not compatible. This is the right thing because otherwise someone could connect to Gnutella with an old client and still find/track all the IPs.
Any ideas? |
Even if you encrypt the IP and port information people who write Gnutella clients that comply with the encryption could still make a client that makes the IP visible since gnutella is an open protocal. Not to mention people who write search monitors. The problem with encrypting the packets is you'd have to have public password so everyone could decrypt and respond to queries. On the other hand if you use public key encrypt then only the client with private key code decrypt the packet thus serverly limiting your search.