summaryrefslogtreecommitdiff
path: root/net/Makefile
diff options
context:
space:
mode:
authorwiz <wiz@pkgsrc.org>2012-12-12 13:19:06 +0000
committerwiz <wiz@pkgsrc.org>2012-12-12 13:19:06 +0000
commit013e37e88ec4910e6549d1556922033b9c56825b (patch)
treeb28f98ef07db08c5e2aa38653ee96fd8bca5d717 /net/Makefile
parent3d63ff72de67a699427abf42f58ed9aaf246070f (diff)
downloadpkgsrc-013e37e88ec4910e6549d1556922033b9c56825b.tar.gz
Import iodine-0.6.0rc1 as net/iodine, packaged for wip by Moritz Wilhelmy,
Georg Schwarz and MJ Turner. iodine lets you tunnel IPv4 data through a DNS server. This can be usable in different situations where internet access is firewalled, but DNS queries are allowed. It runs on Linux, Mac OS X, FreeBSD, NetBSD and OpenBSD and needs a TUN/TAP device. The bandwidth is assymetrical with limited upstream and up to 1 Mbit/s downstream. Compared to other DNS tunnel implementations, iodine offers: * Higher performance: iodine uses the NULL type that allows the downstream data to be sent without encoding. Each DNS reply can contain nearly a kilobyte of payload data. * Portability: iodine runs on many different UNIX-like systems. Tunnels can be set up between two hosts no matter their endianness or operating system. * Security: iodine uses challenge-response login secured by MD5 hash. It also filters out any packets not coming from the IP and port used when logging in. * Less setup: iodine handles setting IP number on interfaces automatically, and up to 8 users can share one server at the same time.
Diffstat (limited to 'net/Makefile')
0 files changed, 0 insertions, 0 deletions