Update: Tormachi

The idea for Tormachi was to make the program, Hamachi, able to connect through any internet configuration. The problem we continually ran into was that in a corporate, and sometimes school network, the handshake to join the Hamachi “network”, which issues the “5.” ip address would fail. The reason for this was commonly blocked ports. Our idea, was to allow Hamachi to use the common internet interface card and connect to the Hamachi “network” via common ports 80, 8080, or 443. Therein lies a problem: localized port redirection. This means that we’d need our local computer to run a virtual port redirection service. In other words, we need program traffic on port 1010 to redirect via our software to port 8080. Not as easy at it sounds, that’s for sure.

So, as we found what we needed, and found that our efforts are in vain trying to develop the technology on which others are probobly also working, we’ve moved onto the next step…

Indexing the tsnlocal network.

Technorati Tags: ,

Project: Tormachi

Project: Tormachi … what is it? It’s file sharing routed through a proxy. Now, some of you might say “isn’t that what hamachi is?” And some of you might be right. But we’re not using hamachi…we’re using hamachi and Tor….to do something that has not been done before, to our knowledge, for our purposes.

What we are working on is an idea of punching a hold in a firewall that blocks port access of url connections to remote ports. Hamachi connects to a url ###.###.###.###:12975 . The current setup that we’re trying to break will allow connections to the ###’s but not to the 12975 part. However, we have successfully connected to other ports on the internet via Torpark (a Firefox bastardization, using Tor as the internal proxy for secure, anonymous internet browsing).

By taking this idea one-step further, one should be able to send handshake requests through the proxy. However, hamachi does not have the option of configuring a proxy connection for the handshake request, since in reality, it’s a secure connection itself.

What we’re trying to do is not route internet traffic through the proxy, but route the entire network interface itself to run through a proxy, to disable the rejection of remote-port access. This way, any traffic that runs on this connection will run through the proxy, and it will be fully integrated with the network connection, not just a browser.

It’s new technology – as far as we know – and we’re half way there. We’ll post more details and setup instructions when we get it working.

Technorati Tags: , , , , , , , , , , , , , , , , , , , , ,