Update of /cvsroot/leaf/src/bering-uclibc4/source/tor
In directory sfp-cvsdas-2.v30.ch3.sourceforge.com:/tmp/cvs-serv3294
Added Files:
buildtool.cfg buildtool.mk tor-0.2.1.26.tar.gz tor.init torrc
Log Message:
new upstream version 0.2.1.26
--- NEW FILE: tor.init ---
#! /bin/sh
RCDLINKS="2,S50 3,S50 4,S50 5,S50 0,K50 1,K50 6,K50"
set -e
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/tor
NAME=tor
DESC="tor daemon"
TORPID=/var/run/tor.pid
WAITFORDAEMON=10
ARGS=""
test -x $DAEMON || exit 0
wait_for_deaddaemon () {
pid=$1
sleep 1
if test -n "$pid"
then
if kill -0 $pid 2>/dev/null
then
echo -n "."
cnt=0
while kill -0 $pid 2>/dev/null
do
cnt=`expr $cnt + 1`
if [ $cnt -gt $WAITFORDAEMON ]
then
echo " FAILED."
return 1
fi
sleep 1
echo -n "."
done
fi
fi
return 0
}
case "$1" in
start)
echo "Starting $DESC: $NAME..."
start-stop-daemon --start --quiet --oknodo \
--exec $DAEMON -- $ARGS --PIDfile $TORPID
echo "done."
;;
stop)
echo -n "Stopping $DESC: "
pid=`cat $TORPID 2>/dev/null` || true
if test ! -f $TORPID -o -z "$pid"
then
echo "not running (there is no $TORPID)."
elif start-stop-daemon --stop --quiet --exec $DAEMON
then
wait_for_deaddaemon $pid
echo "$NAME."
elif kill -0 $pid 2>/dev/null
then
echo "FAILED (Is $pid not $NAME? Is $DAEMON a different binary
now?)."
else
echo "FAILED ($DAEMON died: process $pid not running; or
permission denied)."
fi
;;
reload|force-reload)
echo -n "Reloading $DESC configuration: "
pid=`cat $TORPID 2>/dev/null` || true
if test ! -f $TORPID -o -z "$pid"
then
echo "not running (there is no $TORPID)."
elif start-stop-daemon --stop --signal 1 --quiet --exec $DAEMON
then
echo "$NAME."
elif kill -0 $pid 2>/dev/null
then
echo "FAILED (Is $pid not $NAME? Is $DAEMON a different binary
now?)."
else
echo "FAILED ($DAEMON died: process $pid not running; or
permission denied)."
fi
;;
restart)
$0 stop
sleep 1
$0 start
;;
*)
echo "Usage: $0 {start|stop|restart|reload|force-reload}" >&2
exit 1
;;
esac
exit 0
--- NEW FILE: buildtool.cfg ---
<File buildtool.mk>
Server = cvs4-sourceforge
Revision = HEAD
Directory = tor
</File>
<File tor-0.2.1.26.tar.gz>
Server = cvs4-sourceforge
Revision = HEAD
envname = TOR_SOURCE
Directory = tor
</File>
<File tor.init>
Server = cvs4-sourceforge
Revision = HEAD
Directory = tor
</File>
<File torrc>
Server = cvs4-sourceforge
Revision = HEAD
Directory = tor
</File>
<Package>
<tor>
Version = 0.2.1.26
Revision = 1
Help <<EOF
Tor is a toolset for a wide range of organizations and people
that want to improve their safety and security on the Internet.
Using Tor can help you anonymize web browsing and publishing,
instant messaging, IRC, SSH, and other applications that use
the TCP protocol.
privoxy.lrp is recommended to be used in conjunction with tor
to improve performance for local clients.
Homepage: http://tor.eff.org
Requires: libssl.lrp libcrpto.lrp lpthread.lrp libz.lrp
libevent.lrp
LEAF package by __PACKAGER__, __BUILDDATE__
EOF
<Permissions>
Files = 644
Directories = 755
</Permissions>
<Owner>
Files = root:root
Directories = root:root
</Owner>
<Contents>
<File>
Filename = etc/tor/torrc
Source = etc/tor/torrc
Description = tor configuration
Type = conf
Type = local
Type = binary
Permissions = 600
</File>
<File>
Filename = etc/init.d/tor
Source = etc/init.d/tor
Description = tor init file
Type = binary
Permissions = 755
</File>
<File>
Source = usr/sbin/tor
Filename = usr/sbin/tor
Type = binary
Permissions = 755
</File>
<File>
Source = usr/bin/tor-resolve
Filename = usr/bin/tor-resolve
Type = binary
Permissions = 755
</File>
</Contents>
</tor>
</Package>
--- NEW FILE: buildtool.mk ---
# makefile for tor
include $(MASTERMAKEFILE)
TOR_DIR:=tor-0.2.1.26
TOR_TARGET_DIR:=$(BT_BUILD_DIR)/tor
$(TOR_DIR)/.source:
zcat $(TOR_SOURCE) | tar -xvf -
touch $(TOR_DIR)/.source
source: $(TOR_DIR)/.source
$(TOR_DIR)/.configured: $(TOR_DIR)/.source
(cd $(TOR_DIR) ; CFLAGS="-I$(BT_STAGING_DIR)/include
-I$(BT_STAGING_DIR)/usr/include" \
LD_RUN_PATH="$(BT_STAGING_DIR)/lib:$(BT_STAGING_DIR)/usr/lib" \
LDFLAGS="-s -L$(BT_STAGING_DIR)/lib -L$(BT_STAGING_DIR)/usr/lib" \
CC=$(TARGET_CC) LD=$(TARGET_LD) ./configure --prefix=/usr
--sysconfdir=/etc)
touch $(TOR_DIR)/.configured
$(TOR_DIR)/.build: $(TOR_DIR)/.configured
mkdir -p $(TOR_TARGET_DIR)
mkdir -p $(TOR_TARGET_DIR)/etc/init.d
mkdir -p $(TOR_TARGET_DIR)/etc/tor
mkdir -p $(TOR_TARGET_DIR)/usr/bin
mkdir -p $(TOR_TARGET_DIR)/usr/sbin
make -C $(TOR_DIR)
-$(BT_STRIP) -s --remove-section=.note --remove-section=.comment
$(TOR_DIR)/src/or/tor
-$(BT_STRIP) -s --remove-section=.note --remove-section=.comment
$(TOR_DIR)/src/tools/tor-resolve
cp -a tor.init $(TOR_TARGET_DIR)/etc/init.d/tor
# cp -a $(TOR_DIR)/contrib/tor-tsocks.conf $(TOR_TARGET_DIR)/etc/tor
cp -a torrc $(TOR_TARGET_DIR)/etc/tor
cp -a $(TOR_DIR)/src/or/tor $(TOR_TARGET_DIR)/usr/sbin
cp -a $(TOR_DIR)/src/tools/tor-resolve $(TOR_TARGET_DIR)/usr/bin
cp -a $(TOR_TARGET_DIR)/* $(BT_STAGING_DIR)
touch $(TOR_DIR)/.build
build: $(TOR_DIR)/.build
clean:
make -C $(TOR_DIR) clean
rm -rf $(TOR_TARGET_DIR)
rm -rf $(TOR_DIR)/.build
rm -rf $(TOR_DIR)/.configured
srcclean: clean
rm -rf $(TOR_DIR)
rm -rf $(TOR_DIR)/.source
--- NEW FILE: tor-0.2.1.26.tar.gz ---
(This appears to be a binary file; contents omitted.)
--- NEW FILE: torrc ---
## Configuration file for a typical Tor user
## Last updated 9 February 2006 for Tor 0.1.1.13-alpha.
## <LEAF>
## Last updated 24 July 2010 for LEAF Tor package 0.2.1.26
## by [email protected]
## </LEAF>
##
## (May or may not work for older or newer versions of Tor.)
##
## Lines that begin with "## " try to explain what's going on. Lines
## that begin with just "#" are disabled commands: you can enable them
## by removing the "#" symbol.
##
## See the man page, or http://tor.eff.org/tor-manual-cvs.html, for more
## options you can use in this file.
##
## On Unix, Tor will look for this file in someplace like "~/.tor/torrc" or
## "/etc/torrc"
##
## On Windows, Tor will look for the configuration file in someplace like
## "Application Data\tor\torrc" or "Application Data\<username>\tor\torrc"
##
## With the default Mac OS X installer, Tor will look in ~/.tor/torrc or
## /Library/Tor/torrc
## Replace this with "SocksPort 0" if you plan to run Tor only as a
## server, and not make any local application connections yourself.
SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
#SocksListenAddress 192.168.0.1:9100 # listen on a chosen IP/port too
## Entry policies to allow/deny SOCKS requests based on IP address.
## First entry that matches wins. If no SocksPolicy is set, we accept
## all (and only) requests from SocksListenAddress.
#SocksPolicy accept 192.168.0.0/16
#SocksPolicy reject *
## Logs go to stdout at level "notice" unless redirected by something
## else, like one of the below lines. You can have as many Log lines as
## you want.
##
## We advise using "notice" in most cases, since anything more verbose
## may provide sensitive information to an attacker who obtains the logs.
##
## Send all messages of level 'notice' or higher to /usr/var/log/tor/notices.log
#Log notice file /usr/var/log/tor/notices.log
## Send every possible message to /usr/var/log/tor/debug.log
#Log debug file /usr/var/log/tor/debug.log
## Use the system log instead of Tor's logfiles
Log notice syslog
## To send all messages to stderr:
#Log debug stderr
## Uncomment this to start the process in the background... or use
## --runasdaemon 1 on the command line. This is ignored on Windows;
## see the FAQ entry if you want Tor to run as an NT service.
RunAsDaemon 1
## The directory for keeping all the keys/etc. By default, we store
## things in $HOME/.tor on Unix, and in Application Data\tor on Windows.
## Note that approx 5MB of space will be used
#DataDirectory /usr/var/lib/tor
DataDirectory /tmp/tor
## The port on which Tor will listen for local connections from Tor
## controller applications, as documented in control-spec.txt.
#ControlPort 9051
### A password is needed to access the control port from a remote machine,
### and that password's hash is defined below. The hash is calculated by
### issuing this command:
### tor --hash-password some_password
#HashedControlPassword
16:B26561D67C27302060D09845867ACF441375E14C6789D49A4F874F6A8C
############### This section is just for location-hidden services ###
## Look in .../hidden_service/hostname for the address to tell people.
## HiddenServicePort x y:z says to redirect a port x request from the
## client to y:z.
#HiddenServiceDir /usr/var/lib/tor/hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServiceDir /usr/var/lib/tor/other_hidden_service/
#HiddenServicePort 80 127.0.0.1:80
#HiddenServicePort 22 127.0.0.1:22
#HiddenServiceNodes moria1,moria2
#HiddenServiceExcludeNodes bad,otherbad
################ This section is just for servers #####################
## NOTE: If you enable these, you should consider mailing your identity
## key fingerprint to the tor-ops, so we can add you to the list of
## servers that clients will trust. See
## http://tor.eff.org/cvs/tor/doc/tor-doc-server.html for details.
## Required: A unique handle for this server
#Nickname ididnteditheconfig
## The IP or fqdn for this server. Leave commented out and Tor will guess.
#Address noname.example.com
## Contact info that will be published in the directory, so we can
## contact you if you need to upgrade or if something goes wrong.
## This is optional but recommended.
#ContactInfo Random Person <nobody AT example dot com>
## You might also include your PGP or GPG fingerprint if you have one:
#ContactInfo 1234D/FFFFFFFF Random Person <nobody AT example dot com>
## Required: what port to advertise for tor connections
#ORPort 9001
## If you want to listen on a port other than the one advertised
## in ORPort (e.g. to advertise 443 but bind to 9090), uncomment
## the line below. You'll need to do ipchains or other port forwarding
## yourself to make this work.
#ORListenAddress 0.0.0.0:9090
## Uncomment this to mirror the directory for others. Please do
## if you have enough bandwidth: see the bottom of
## http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth
#DirPort 9030 # what port to advertise for directory connections
## If you want to listen on a port other than the one advertised
## in DirPort (e.g. to advertise 80 but bind 9091), uncomment the line
## below. You'll need to do ipchains or other port forwarding yourself
## to make this work.
#DirListenAddress 0.0.0.0:9091
## Uncomment this if you run more than one Tor server, and add the
## nickname of each Tor server you control, even if they're on different
## networks. We declare it here so clients can avoid using more than
## one of your servers in a given circuit.
#MyFamily nickname1,nickname2,...
## A comma-separated list of exit policies. They're considered first
## to last, and the first match wins. If you want to _replace_
## the default exit policy, end this with either a reject *:* or an
## accept *:*. Otherwise, you're _augmenting_ (prepending to) the
## default exit policy. Leave commented to just use the default, which is
## available in the man page or at http://tor.eff.org/documentation.html
##
## Look at http://tor.eff.org/faq-abuse.html#TypicalAbuses
## for issues you might encounter if you use the default exit policy.
##
## If certain IPs and ports are blocked externally, e.g. by your firewall,
## you should update your exit policy to reflect this -- otherwise Tor
## users will be told that those destinations are down.
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp as well as default exit policy
#ExitPolicy reject *:* # middleman only -- no exits allowed
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
leaf-cvs-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-cvs-commits
