Integration of Tor for Enhanced Privacy and Anonymity

This pull request marks a significant enhancement to our project by integrating Tor, leveraging the cretz/bine and ipsn/go-libtor library. This integration allows our peers to route their traffic through the Tor network, effectively turning each peer into a hidden service within this network. One of the key advantages of using ipsn/go-libtor is its ability to statically link Tor to our project, which simplifies deployment by eliminating the need for users to install Tor separately.

Usage Example:

To start a Tor process and manage a hidden service, the following code snippet demonstrates the basic operations:

conf := &tor.TorConfig{}
torInstance, _ := tor.NewTor(conf)
torInstance.StartTor()
onion, _ := torInstance.StartHiddenService()
torInstance.StopTor()

The tor.TorConfig struct has been set up to allow detailed configuration of the Tor instance, including:

DataDir: Directory for Tor data.
SocksPort: Port for the SOCKS proxy.
LocalPort: Local port for incoming connections.
RemotePort: Remote port for accessing services through Tor.
DeleteDataDirOnClose: Option to clean up data after the Tor process stops.
UseEmbedded: Flag to use the embedded Tor process.

Traffic Routing Options:

Peers can now route their traffic in multiple ways:

Clearnet: For non-anonymous routing, the setup remains straightforward:

peerInstance, _ := peer.NewPeer("127.0.0.1", port, "", "")
defer peerInstance.Shutdown()
peerInstance.Listen(nil)

Tor Network: To route traffic over the Tor network, peers use the onion address obtained from the code snippet above:

peerInstance, _ := peer.NewPeer(onion.ID+".onion", conf.LocalPort, conf.RemotePort, "127.0.0.1:"+conf.SocksPort)
defer peerInstance.Shutdown()
peerInstance.Listen(onion)

Limitations:

This implementation currently restricts our program to only operate on Linux-based systems due to dependencies in go-libtor.

For more information on go-libtor, please refer to go-libtor documentation.

Closes #14

scherzma / Skunk