infrastructure of the Six/Four network in the background at the same time.
- The next thing to implement will be a universal tunneling application:
it will work just like stunnel (or transparent bouncers): listen on a
port and redirect all connections to a preset host (in our case, not only
redirect, but transparently tunnel through the Six/Four network). Thus, most
applications using simple network protocols will be able to use Six/Four.
- A HTTP proxy already exists. A huge incentive for using it is that it
provides the benefit of being able to surf anonymously to EVERYONE
putting up and linking his own peer into the Six/Four net (as long
as enough Trusted Peers exist).
- A DNS proxy server for localhost, listening on port 53/UDP and tunneling
requests to an outside nameserver - adds trust and anonymity to DNS.
- IRC and other simple chat protocols can easily be tunneled using a
transparent Six/Four bouncer. It will effectively provide anonymous
IRC (users will appear with the IP address of their Trusted Peer).
To also hide the Trusted Peer address, one could put up a Trusted Peer
with connectivity to the anonymous, P2P, Invisible IRC Project (see
http://www.invisibleirc.net) - Tunneling IRC through the anonymous
IRC protocol, tunneled through the Six/Four protocol - super-anonymity!
- An anonymous passive FTP client would be interesting, where a special
TP could be written that disables uploading to the FTP (or not).
Even active FTP sessions would be possible, as Six/Four seamlessly
supports multiple concurrent connections.
- Anonymous news (both reading and posting) are certainly interesting for
many people in totalitarian country. Rather than using NTTP, a HTTP
proxy specifically optimized for Google News could be written for this
(parse POST at application protocol layer, hide some HTTP headers, manage
cookies, perhaps even manage anonymous sign-ups).
- A simple anonymous mail gateway by tunneling port 25 connections to
outside SMTP servers. This would probably require opening dedicated
SMTP servers to known Trusted Peers that have some extra anti-spam
checks in place themselves. Also possible for POP3 and IMAP.
- A gateway to remote FREENET servers.
- Caching proxies (possible for HTTP, FTP, NEWS, FREENET and other
protocols) could 1) Reduce network load at the TP side 2) add incentives
for Trusted Peer maintainers in form of a cache of interesting data.
- By putting up a Trusted Peer with a locally hacked protocol, one could
get out information out of censored countries instead of letting it
in: Let a chinese internet user put up a TP (which listens on port 443,
like all peers) and prenegotiate keys with a trusted party.
Now the hack: In the Session initiation request, there is a hostname
transmitted in full text. Hack the Trusted Peer to interpret that
hostname as a file or URL. Make the Trusted Peer serve up local content
from his Hard Drive on such requests, rather than connecting out to
anywhere. A way of requesting information from totalitarian countries,
pull-mode rather than push-mode, quite safe for Trusted Peer operator.
This document was generated using the LaTeX2HTML translator Version 2002-2 (1.70)
Copyright © 1993, 1994, 1995, 1996,
Nikos Drakos,
Computer Based Learning Unit, University of Leeds.
Copyright © 1997, 1998, 1999,
Ross Moore,
Mathematics Department, Macquarie University, Sydney.
The command line arguments were:
latex2html -no_subdir -split 0 -show_section_numbers /tmp/lyx_tmpdir10755x1TkOh/lyx_tmpbuf1/README.tex
The translation was initiated by mixter on 2003-02-14