32 lines
1.4 KiB
Text
32 lines
1.4 KiB
Text
|
# Template file for 'tsocks'
|
||
|
|
pkgname=tsocks
|
||
|
|
version=1.8beta5
|
||
|
|
wrksrc="tsocks-1.8"
|
||
|
|
homepage="http://tsocks.sourceforge.net/"
|
||
|
|
distfiles="${SOURCEFORGE_SITE}/tsocks/tsocks-$version.tar.gz"
|
||
|
|
build_style=gnu-configure
|
||
|
|
configure_args="--libdir=/usr/lib"
|
||
|
|
short_desc="Transparent SOCKS proxying library"
|
||
|
|
maintainer="Juan RP <xtraeme@gmail.com>"
|
||
|
|
license="GPL-2"
|
||
|
|
checksum=849d7ef5af80d03e76cc05ed9fb8fa2bcc2b724b51ebfd1b6be11c7863f5b347
|
||
|
|
long_desc="
|
||
|
|
SOCKS servers are a form of proxy that are commonly used in firewalled LAN
|
||
|
|
environments to allow access between networks, and often to the Internet.
|
||
|
|
The problem is that most applications don't know how to gain access through
|
||
|
|
SOCKS servers. This means that network based applications that don't
|
||
|
|
understand SOCKS are very limited in networks they can reach. An example of
|
||
|
|
this is simple 'telnet'. If you're on a network firewalled from the internet
|
||
|
|
with a SOCKS server for outside access, telnet can't use this server and
|
||
|
|
thus can't telnet out to the Internet.
|
||
|
|
|
||
|
|
tsocks' role is to allow these non SOCKS aware applications (e.g telnet, ssh,
|
||
|
|
ftp etc) to use SOCKS without any modification. It does this by intercepting
|
||
|
|
the calls that applications make to establish network connections and
|
||
|
|
negotating them through a SOCKS server as necessary."
|
||
|
|
|
||
|
|
post_install() {
|
||
|
|
vmkdir usr/share/examples/tsocks
|
||
|
|
install -m644 *.example ${DESTDIR}/usr/share/examples/tsocks
|
||
|
|
}
|