upg tor tor-alpha-dev
This commit is contained in:
parent
7157954a80
commit
c6736af0af
|
|
@ -6,8 +6,8 @@
|
|||
#-----------------------------------------| DESCRIPTION |---------------------------------------
|
||||
|
||||
pkgname=tor-alpha
|
||||
pkgver=0.4.8.0.alpha.dev.r1.g4259bc3
|
||||
pkgrel=01
|
||||
pkgver=0.4.7.10.r93.g982c504
|
||||
pkgrel=1
|
||||
pkgdesc="An anonymizing overlay network (development version) no-zstd no-systemd"
|
||||
arch=('x86_64')
|
||||
url="https://www.torproject.org"
|
||||
|
|
@ -54,6 +54,7 @@ build() {
|
|||
--disable-html-manual \
|
||||
--disable-systemd \
|
||||
--disable-zstd \
|
||||
--disable-ipv6 \
|
||||
--disable-zstd-advanced-apis \
|
||||
--enable-lzma \
|
||||
--enable-xz \
|
||||
|
|
|
|||
|
|
@ -1,103 +0,0 @@
|
|||
#!/usr/bin/bash
|
||||
# JOBoRun : Jwm OpenBox Obarun RUNit
|
||||
# Maintainer : Joe Bo Run <joborun@disroot.org>
|
||||
# PkgSource : url="https://gittea.disroot.org/joborun-pkg/jobextra/$pkgname"
|
||||
#-----------------------------------------| DESCRIPTION |---------------------------------------
|
||||
|
||||
pkgname=tor-alpha
|
||||
pkgver=0.4.7.3.alpha.r15.g66e7ddb
|
||||
pkgrel=01
|
||||
pkgdesc="An anonymizing overlay network (development version)"
|
||||
arch=('x86_64')
|
||||
url="https://www.torproject.org"
|
||||
conflicts=('tor' 'tor-git')
|
||||
provides=('tor')
|
||||
backup=('etc/tor/torrc'
|
||||
'etc/tor/torrc.d/nodes.conf'
|
||||
'etc/tor/torrc.d/bridge.conf'
|
||||
'etc/tor/torrc.d/isolation.conf'
|
||||
'etc/tor/torrc.d/transparent_proxy.conf')
|
||||
|
||||
depends=('openssl' 'libevent' 'libseccomp' 'xz')
|
||||
makedepends=('asciidoc')
|
||||
checkdepends=('python')
|
||||
optdepends=('torsocks: allow transparent SOCKS proxying'
|
||||
'obfs4proxy: obfuscating pluggable transport proxy'
|
||||
'meek: obfuscating pluggable transport proxy')
|
||||
|
||||
[[ $_malloc = 'jemalloc' ]] && depends+=('jemalloc')
|
||||
[[ $_malloc = 'tcmalloc' ]] && depends+=('gperftools')
|
||||
|
||||
# https://gitweb.torproject.org/tor.git/tag/?h=tor-0.4.7.3-alpha
|
||||
source=("git+https://git.torproject.org/tor.git#branch=${_branch:-main}"
|
||||
{nodes,bridge,transparent_proxy,isolation}.conf
|
||||
'torrc' 'tor.logrotate' 'tor.tmpfiles' 'tor.sysusers')
|
||||
|
||||
pkgver () {
|
||||
cd tor
|
||||
git describe --long --tags --abbrev=7 "origin/${_branch:-main}" \
|
||||
|sed -e 's/tor.//g;s/\([^-]*-g\)/r\1/;s/-/./g'
|
||||
}
|
||||
|
||||
prepare() {
|
||||
cd tor
|
||||
./autogen.sh
|
||||
}
|
||||
|
||||
build() {
|
||||
cd tor
|
||||
|
||||
./configure \
|
||||
--prefix=/usr --sysconfdir=/etc --localstatedir=/var \
|
||||
--disable-html-manual \
|
||||
--disable-systemd \
|
||||
--disable-zstd \
|
||||
--enable-lzma \
|
||||
--enable-xz \
|
||||
--enable-pic \
|
||||
--with-malloc="${_malloc:-system}" #\
|
||||
#--disable-module-relay \
|
||||
#--disable-unittests
|
||||
make
|
||||
}
|
||||
|
||||
check() {
|
||||
cd tor
|
||||
make check ||true
|
||||
}
|
||||
|
||||
package() {
|
||||
cd tor
|
||||
make DESTDIR="$pkgdir" install
|
||||
|
||||
rm -f "$pkgdir/etc/tor/tor-tsocks.conf"
|
||||
rm -f "$pkgdir/usr/bin/torify"
|
||||
|
||||
install -dm755 "$pkgdir/etc/tor"
|
||||
install -dm750 "$pkgdir/etc/tor/torrc.d"
|
||||
|
||||
install -Dm640 "$srcdir/torrc" "$pkgdir/etc/tor/torrc"
|
||||
install -Dm640 "$srcdir/nodes.conf" "$pkgdir/etc/tor/torrc.d/nodes.conf"
|
||||
install -Dm640 "$srcdir/bridge.conf" "$pkgdir/etc/tor/torrc.d/bridge.conf"
|
||||
install -Dm640 "$srcdir/isolation.conf" "$pkgdir/etc/tor/torrc.d/isolation.conf"
|
||||
install -Dm640 "$srcdir/transparent_proxy.conf" "$pkgdir/etc/tor/torrc.d/transparent_proxy.conf"
|
||||
|
||||
install -Dm644 "$srcdir/tor.logrotate" "$pkgdir/etc/logrotate.d/tor"
|
||||
install -Dm644 "$srcdir/tor.tmpfiles" "$pkgdir/usr/lib/tmpfiles.d/tor.conf"
|
||||
install -Dm644 "$srcdir/tor.sysusers" "$pkgdir/usr/lib/sysusers.d/tor.conf"
|
||||
install -Dm644 LICENSE "$pkgdir/usr/share/licenses/tor-git/LICENSE"
|
||||
}
|
||||
|
||||
#---- license gpg-key sha256sums ----
|
||||
|
||||
license=('BSD')
|
||||
|
||||
sha256sums=(SKIP a
|
||||
60c77f74f795739cd44899add8916f842fed1d692f2789f1a11e8241ee6ed950 # nodes.conf
|
||||
eab04421822cce29a3c5065b707b0033fdab6dedd140a49ea902daf36bb767e0 # bridge.conf
|
||||
b6d5027754831bb4230c748affa245e5e7ee4f801214bca19ea6418cb84fd417 # transparent_proxy.conf
|
||||
9156f0d768119e7c8390be625cc591af90304198ad5dc5b0b4a036e7cc92fa07 # isolation.conf
|
||||
1f32a363443437a08d133494732008b98a9dc520173a97d53ce832edfb923f7b # torrc
|
||||
5756d919fb7a9c7063fb6311b8056c6695576ed12658098325aef7758824c960 # tor.logrotate
|
||||
06c00318d84ead3f939b267c7ae9e4cc1cd90c534d0b57ddd2595fee9065ee7f # tor.tmpfiles
|
||||
632cd25223ac163aed2a848784108d5310e641e1eb839375813c7c406ecee9d0) # tor.sysusers
|
||||
|
|
@ -1,267 +0,0 @@
|
|||
## Configuration file for a typical Tor user
|
||||
## Last updated 28 February 2019 for Tor 0.3.5.1-alpha.
|
||||
## (may or may not work for much older or much 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 'man tor', or https://www.torproject.org/docs/tor-manual.html,
|
||||
## for more options you can use in this file.
|
||||
##
|
||||
## Tor will look for this file in various places based on your platform:
|
||||
## https://www.torproject.org/docs/faq#torrc
|
||||
|
||||
## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
|
||||
## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
|
||||
## as a relay, and not make any local application connections yourself.
|
||||
SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.
|
||||
#SOCKSPort 192.168.0.1:9100 # Bind to this address: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 that reach a SOCKSPort. Untrusted users who
|
||||
## can access your SOCKSPort may be able to learn about the connections
|
||||
## you make.
|
||||
#SOCKSPolicy accept 192.168.0.0/16
|
||||
#SOCKSPolicy accept6 FC00::/7
|
||||
#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 /var/log/tor/notices.log
|
||||
#Log notice file /var/log/tor/notices.log
|
||||
## Send every possible message to /var/log/tor/debug.log
|
||||
#Log debug file /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
|
||||
|
||||
## Default username and group the server will run as
|
||||
User tor
|
||||
|
||||
## 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.
|
||||
DataDirectory /var/lib/tor
|
||||
|
||||
## The port on which Tor will listen for local connections from Tor
|
||||
## controller applications, as documented in control-spec.txt.
|
||||
#ControlPort 9051
|
||||
## If you enable the controlport, be sure to enable one of these
|
||||
## authentication methods, to prevent attackers from accessing it.
|
||||
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
|
||||
#CookieAuthentication 1
|
||||
|
||||
############### This section is just for location-hidden services ###
|
||||
|
||||
## Once you have configured a hidden service, you can look at the
|
||||
## contents of the file ".../hidden_service/hostname" for the address
|
||||
## to tell people.
|
||||
##
|
||||
## HiddenServicePort x y:z says to redirect requests on port x to the
|
||||
## address y:z.
|
||||
|
||||
#HiddenServiceDir /var/lib/tor/hidden_service/
|
||||
#HiddenServicePort 80 127.0.0.1:80
|
||||
|
||||
#HiddenServiceDir /var/lib/tor/other_hidden_service/
|
||||
#HiddenServicePort 80 127.0.0.1:80
|
||||
#HiddenServicePort 22 127.0.0.1:22
|
||||
|
||||
################ This section is just for relays #####################
|
||||
#
|
||||
## See https://www.torproject.org/docs/tor-doc-relay for details.
|
||||
|
||||
## Required: what port to advertise for incoming 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), you can do it as
|
||||
## follows. You'll need to do ipchains or other port forwarding
|
||||
## yourself to make this work.
|
||||
#ORPort 443 NoListen
|
||||
#ORPort 127.0.0.1:9090 NoAdvertise
|
||||
## If you want to listen on IPv6 your numeric address must be explicitly
|
||||
## between square brackets as follows. You must also listen on IPv4.
|
||||
#ORPort [2001:DB8::1]:9050
|
||||
|
||||
## The IP address or full DNS name for incoming connections to your
|
||||
## relay. Leave commented out and Tor will guess.
|
||||
#Address noname.example.com
|
||||
|
||||
## If you have multiple network interfaces, you can specify one for
|
||||
## outgoing traffic to use.
|
||||
## OutboundBindAddressExit will be used for all exit traffic, while
|
||||
## OutboundBindAddressOR will be used for all OR and Dir connections
|
||||
## (DNS connections ignore OutboundBindAddress).
|
||||
## If you do not wish to differentiate, use OutboundBindAddress to
|
||||
## specify the same address for both in a single line.
|
||||
#OutboundBindAddressExit 10.0.0.4
|
||||
#OutboundBindAddressOR 10.0.0.5
|
||||
|
||||
## A handle for your relay, so people don't have to refer to it by key.
|
||||
## Nicknames must be between 1 and 19 characters inclusive, and must
|
||||
## contain only the characters [a-zA-Z0-9].
|
||||
## If not set, "Unnamed" will be used.
|
||||
#Nickname ididnteditheconfig
|
||||
|
||||
## Define these to limit how much relayed traffic you will allow. Your
|
||||
## own traffic is still unthrottled. Note that RelayBandwidthRate must
|
||||
## be at least 75 kilobytes per second.
|
||||
## Note that units for these config options are bytes (per second), not
|
||||
## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
|
||||
## 2^20, etc.
|
||||
#RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
|
||||
#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)
|
||||
|
||||
## Use these to restrict the maximum traffic per day, week, or month.
|
||||
## Note that this threshold applies separately to sent and received bytes,
|
||||
## not to their sum: setting "40 GB" may allow up to 80 GB total before
|
||||
## hibernating.
|
||||
##
|
||||
## Set a maximum of 40 gigabytes each way per period.
|
||||
#AccountingMax 40 GBytes
|
||||
## Each period starts daily at midnight (AccountingMax is per day)
|
||||
#AccountingStart day 00:00
|
||||
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
|
||||
## is per month)
|
||||
#AccountingStart month 3 15:00
|
||||
|
||||
## Administrative contact information for this relay or bridge. This line
|
||||
## can be used to contact you if your relay or bridge is misconfigured or
|
||||
## something else goes wrong. Note that we archive and publish all
|
||||
## descriptors containing these lines and that Google indexes them, so
|
||||
## spammers might also collect them. You may want to obscure the fact that
|
||||
## it's an email address and/or generate a new address for this purpose.
|
||||
##
|
||||
## If you are running multiple relays, you MUST set this option.
|
||||
##
|
||||
#ContactInfo Random Person <nobody AT example dot com>
|
||||
## You might also include your PGP or GPG fingerprint if you have one:
|
||||
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
|
||||
|
||||
## Uncomment this to mirror directory information for others. Please do
|
||||
## if you have enough bandwidth.
|
||||
#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 to 9091), you can do it as
|
||||
## follows. below too. You'll need to do ipchains or other port
|
||||
## forwarding yourself to make this work.
|
||||
#DirPort 80 NoListen
|
||||
#DirPort 127.0.0.1:9091 NoAdvertise
|
||||
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
|
||||
## can explain what Tor is if anybody wonders why your IP address is
|
||||
## contacting them. See contrib/tor-exit-notice.html in Tor's source
|
||||
## distribution for a sample.
|
||||
#DirPortFrontPage /etc/tor/tor-exit-notice.html
|
||||
|
||||
## Uncomment this if you run more than one Tor relay, and add the identity
|
||||
## key fingerprint of each Tor relay you control, even if they're on
|
||||
## different networks. You declare it here so Tor clients can avoid
|
||||
## using more than one of your relays in a single circuit. See
|
||||
## https://www.torproject.org/docs/faq#MultipleRelays
|
||||
## However, you should never include a bridge's fingerprint here, as it would
|
||||
## break its concealability and potentially reveal its IP/TCP address.
|
||||
##
|
||||
## If you are running multiple relays, you MUST set this option.
|
||||
##
|
||||
## Note: do not use MyFamily on bridge relays.
|
||||
#MyFamily $keyid,$keyid,...
|
||||
|
||||
## Uncomment this if you want your relay to be an exit, with the default
|
||||
## exit policy (or whatever exit policy you set below).
|
||||
## (If ReducedExitPolicy, ExitPolicy, or IPv6Exit are set, relays are exits.
|
||||
## If none of these options are set, relays are non-exits.)
|
||||
#ExitRelay 1
|
||||
|
||||
## Uncomment this if you want your relay to allow IPv6 exit traffic.
|
||||
## (Relays do not allow any exit traffic by default.)
|
||||
#IPv6Exit 1
|
||||
|
||||
## Uncomment this if you want your relay to be an exit, with a reduced set
|
||||
## of exit ports.
|
||||
#ReducedExitPolicy 1
|
||||
|
||||
## Uncomment these lines if you want your relay to be an exit, with the
|
||||
## specified set of exit IPs and ports.
|
||||
##
|
||||
## A comma-separated list of exit policies. They're considered first
|
||||
## to last, and the first match wins.
|
||||
##
|
||||
## If you want to allow the same ports on IPv4 and IPv6, write your rules
|
||||
## using accept/reject *. If you want to allow different ports on IPv4 and
|
||||
## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules
|
||||
## using accept/reject *4.
|
||||
##
|
||||
## 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
|
||||
## described in the man page or at
|
||||
## https://www.torproject.org/documentation.html
|
||||
##
|
||||
## Look at https://www.torproject.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.
|
||||
##
|
||||
## For security, by default Tor rejects connections to private (local)
|
||||
## networks, including to the configured primary public IPv4 and IPv6 addresses,
|
||||
## and any public IPv4 and IPv6 addresses on any interface on the relay.
|
||||
## See the man page entry for ExitPolicyRejectPrivate if you want to allow
|
||||
## "exit enclaving".
|
||||
##
|
||||
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more
|
||||
#ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy
|
||||
#ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy
|
||||
#ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as default exit policy
|
||||
#ExitPolicy reject *:* # no exits allowed
|
||||
|
||||
## Bridge relays (or "bridges") are Tor relays that aren't listed in the
|
||||
## main directory. Since there is no complete public list of them, even an
|
||||
## ISP that filters connections to all the known Tor relays probably
|
||||
## won't be able to block all the bridges. Also, websites won't treat you
|
||||
## differently because they won't know you're running Tor. If you can
|
||||
## be a real relay, please do; but if not, be a bridge!
|
||||
##
|
||||
## Warning: when running your Tor as a bridge, make sure than MyFamily is
|
||||
## NOT configured.
|
||||
#BridgeRelay 1
|
||||
## By default, Tor will advertise your bridge to users through various
|
||||
## mechanisms like https://bridges.torproject.org/. If you want to run
|
||||
## a private bridge, for example because you'll give out your bridge
|
||||
## address manually to your friends, uncomment this line:
|
||||
#BridgeDistribution none
|
||||
|
||||
## If non-zero, try to write to disk less frequently than we would otherwise.
|
||||
## This is useful when running on flash memory or other media that support
|
||||
## only a limited number of writes.
|
||||
AvoidDiskWrites 1
|
||||
|
||||
## Try to use built-in (static) crypto hardware acceleration when available.
|
||||
HardwareAccel 1
|
||||
|
||||
## If set to 1, Tor will attempt to lock all current and future memory pages,
|
||||
## so that memory cannot be paged out.
|
||||
DisableAllSwap 1
|
||||
|
||||
## Configuration options can be imported from files or folders using the %include
|
||||
## option with the value being a path. This path can have wildcards. Wildcards are
|
||||
## expanded first, using lexical order. Then, for each matching file or folder, the following
|
||||
## rules are followed: if the path is a file, the options from the file will be parsed as if
|
||||
## they were written where the %include option is. If the path is a folder, all files on that
|
||||
## folder will be parsed following lexical order. Files starting with a dot are ignored. Files
|
||||
## on subfolders are ignored.
|
||||
## The %include option can be used recursively.
|
||||
%include /etc/tor/torrc.d/*.conf
|
||||
|
|
@ -1,267 +0,0 @@
|
|||
## Configuration file for a typical Tor user
|
||||
## Last updated 28 February 2019 for Tor 0.3.5.1-alpha.
|
||||
## (may or may not work for much older or much 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 'man tor', or https://www.torproject.org/docs/tor-manual.html,
|
||||
## for more options you can use in this file.
|
||||
##
|
||||
## Tor will look for this file in various places based on your platform:
|
||||
## https://www.torproject.org/docs/faq#torrc
|
||||
|
||||
## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
|
||||
## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
|
||||
## as a relay, and not make any local application connections yourself.
|
||||
SOCKSPort 9050 # Default: Bind to localhost:9050 for local connections.
|
||||
#SOCKSPort 192.168.0.1:9100 # Bind to this address: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 that reach a SOCKSPort. Untrusted users who
|
||||
## can access your SOCKSPort may be able to learn about the connections
|
||||
## you make.
|
||||
#SOCKSPolicy accept 192.168.0.0/16
|
||||
#SOCKSPolicy accept6 FC00::/7
|
||||
#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 /var/log/tor/notices.log
|
||||
#Log notice file /var/log/tor/notices.log
|
||||
## Send every possible message to /var/log/tor/debug.log
|
||||
#Log debug file /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
|
||||
|
||||
## Default username and group the server will run as
|
||||
#User tor
|
||||
|
||||
## 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.
|
||||
DataDirectory /var/lib/tor
|
||||
|
||||
## The port on which Tor will listen for local connections from Tor
|
||||
## controller applications, as documented in control-spec.txt.
|
||||
#ControlPort 9051
|
||||
## If you enable the controlport, be sure to enable one of these
|
||||
## authentication methods, to prevent attackers from accessing it.
|
||||
#HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C
|
||||
#CookieAuthentication 1
|
||||
|
||||
############### This section is just for location-hidden services ###
|
||||
|
||||
## Once you have configured a hidden service, you can look at the
|
||||
## contents of the file ".../hidden_service/hostname" for the address
|
||||
## to tell people.
|
||||
##
|
||||
## HiddenServicePort x y:z says to redirect requests on port x to the
|
||||
## address y:z.
|
||||
|
||||
#HiddenServiceDir /var/lib/tor/hidden_service/
|
||||
#HiddenServicePort 80 127.0.0.1:80
|
||||
|
||||
#HiddenServiceDir /var/lib/tor/other_hidden_service/
|
||||
#HiddenServicePort 80 127.0.0.1:80
|
||||
#HiddenServicePort 22 127.0.0.1:22
|
||||
|
||||
################ This section is just for relays #####################
|
||||
#
|
||||
## See https://www.torproject.org/docs/tor-doc-relay for details.
|
||||
|
||||
## Required: what port to advertise for incoming 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), you can do it as
|
||||
## follows. You'll need to do ipchains or other port forwarding
|
||||
## yourself to make this work.
|
||||
#ORPort 443 NoListen
|
||||
#ORPort 127.0.0.1:9090 NoAdvertise
|
||||
## If you want to listen on IPv6 your numeric address must be explicitly
|
||||
## between square brackets as follows. You must also listen on IPv4.
|
||||
#ORPort [2001:DB8::1]:9050
|
||||
|
||||
## The IP address or full DNS name for incoming connections to your
|
||||
## relay. Leave commented out and Tor will guess.
|
||||
#Address noname.example.com
|
||||
|
||||
## If you have multiple network interfaces, you can specify one for
|
||||
## outgoing traffic to use.
|
||||
## OutboundBindAddressExit will be used for all exit traffic, while
|
||||
## OutboundBindAddressOR will be used for all OR and Dir connections
|
||||
## (DNS connections ignore OutboundBindAddress).
|
||||
## If you do not wish to differentiate, use OutboundBindAddress to
|
||||
## specify the same address for both in a single line.
|
||||
#OutboundBindAddressExit 10.0.0.4
|
||||
#OutboundBindAddressOR 10.0.0.5
|
||||
|
||||
## A handle for your relay, so people don't have to refer to it by key.
|
||||
## Nicknames must be between 1 and 19 characters inclusive, and must
|
||||
## contain only the characters [a-zA-Z0-9].
|
||||
## If not set, "Unnamed" will be used.
|
||||
#Nickname ididnteditheconfig
|
||||
|
||||
## Define these to limit how much relayed traffic you will allow. Your
|
||||
## own traffic is still unthrottled. Note that RelayBandwidthRate must
|
||||
## be at least 75 kilobytes per second.
|
||||
## Note that units for these config options are bytes (per second), not
|
||||
## bits (per second), and that prefixes are binary prefixes, i.e. 2^10,
|
||||
## 2^20, etc.
|
||||
#RelayBandwidthRate 100 KBytes # Throttle traffic to 100KB/s (800Kbps)
|
||||
#RelayBandwidthBurst 200 KBytes # But allow bursts up to 200KB (1600Kb)
|
||||
|
||||
## Use these to restrict the maximum traffic per day, week, or month.
|
||||
## Note that this threshold applies separately to sent and received bytes,
|
||||
## not to their sum: setting "40 GB" may allow up to 80 GB total before
|
||||
## hibernating.
|
||||
##
|
||||
## Set a maximum of 40 gigabytes each way per period.
|
||||
#AccountingMax 40 GBytes
|
||||
## Each period starts daily at midnight (AccountingMax is per day)
|
||||
#AccountingStart day 00:00
|
||||
## Each period starts on the 3rd of the month at 15:00 (AccountingMax
|
||||
## is per month)
|
||||
#AccountingStart month 3 15:00
|
||||
|
||||
## Administrative contact information for this relay or bridge. This line
|
||||
## can be used to contact you if your relay or bridge is misconfigured or
|
||||
## something else goes wrong. Note that we archive and publish all
|
||||
## descriptors containing these lines and that Google indexes them, so
|
||||
## spammers might also collect them. You may want to obscure the fact that
|
||||
## it's an email address and/or generate a new address for this purpose.
|
||||
##
|
||||
## If you are running multiple relays, you MUST set this option.
|
||||
##
|
||||
#ContactInfo Random Person <nobody AT example dot com>
|
||||
## You might also include your PGP or GPG fingerprint if you have one:
|
||||
#ContactInfo 0xFFFFFFFF Random Person <nobody AT example dot com>
|
||||
|
||||
## Uncomment this to mirror directory information for others. Please do
|
||||
## if you have enough bandwidth.
|
||||
#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 to 9091), you can do it as
|
||||
## follows. below too. You'll need to do ipchains or other port
|
||||
## forwarding yourself to make this work.
|
||||
#DirPort 80 NoListen
|
||||
#DirPort 127.0.0.1:9091 NoAdvertise
|
||||
## Uncomment to return an arbitrary blob of html on your DirPort. Now you
|
||||
## can explain what Tor is if anybody wonders why your IP address is
|
||||
## contacting them. See contrib/tor-exit-notice.html in Tor's source
|
||||
## distribution for a sample.
|
||||
#DirPortFrontPage /etc/tor/tor-exit-notice.html
|
||||
|
||||
## Uncomment this if you run more than one Tor relay, and add the identity
|
||||
## key fingerprint of each Tor relay you control, even if they're on
|
||||
## different networks. You declare it here so Tor clients can avoid
|
||||
## using more than one of your relays in a single circuit. See
|
||||
## https://www.torproject.org/docs/faq#MultipleRelays
|
||||
## However, you should never include a bridge's fingerprint here, as it would
|
||||
## break its concealability and potentially reveal its IP/TCP address.
|
||||
##
|
||||
## If you are running multiple relays, you MUST set this option.
|
||||
##
|
||||
## Note: do not use MyFamily on bridge relays.
|
||||
#MyFamily $keyid,$keyid,...
|
||||
|
||||
## Uncomment this if you want your relay to be an exit, with the default
|
||||
## exit policy (or whatever exit policy you set below).
|
||||
## (If ReducedExitPolicy, ExitPolicy, or IPv6Exit are set, relays are exits.
|
||||
## If none of these options are set, relays are non-exits.)
|
||||
#ExitRelay 1
|
||||
|
||||
## Uncomment this if you want your relay to allow IPv6 exit traffic.
|
||||
## (Relays do not allow any exit traffic by default.)
|
||||
#IPv6Exit 1
|
||||
|
||||
## Uncomment this if you want your relay to be an exit, with a reduced set
|
||||
## of exit ports.
|
||||
#ReducedExitPolicy 1
|
||||
|
||||
## Uncomment these lines if you want your relay to be an exit, with the
|
||||
## specified set of exit IPs and ports.
|
||||
##
|
||||
## A comma-separated list of exit policies. They're considered first
|
||||
## to last, and the first match wins.
|
||||
##
|
||||
## If you want to allow the same ports on IPv4 and IPv6, write your rules
|
||||
## using accept/reject *. If you want to allow different ports on IPv4 and
|
||||
## IPv6, write your IPv6 rules using accept6/reject6 *6, and your IPv4 rules
|
||||
## using accept/reject *4.
|
||||
##
|
||||
## 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
|
||||
## described in the man page or at
|
||||
## https://www.torproject.org/documentation.html
|
||||
##
|
||||
## Look at https://www.torproject.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.
|
||||
##
|
||||
## For security, by default Tor rejects connections to private (local)
|
||||
## networks, including to the configured primary public IPv4 and IPv6 addresses,
|
||||
## and any public IPv4 and IPv6 addresses on any interface on the relay.
|
||||
## See the man page entry for ExitPolicyRejectPrivate if you want to allow
|
||||
## "exit enclaving".
|
||||
##
|
||||
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports on IPv4 and IPv6 but no more
|
||||
#ExitPolicy accept *:119 # accept nntp ports on IPv4 and IPv6 as well as default exit policy
|
||||
#ExitPolicy accept *4:119 # accept nntp ports on IPv4 only as well as default exit policy
|
||||
#ExitPolicy accept6 *6:119 # accept nntp ports on IPv6 only as well as default exit policy
|
||||
#ExitPolicy reject *:* # no exits allowed
|
||||
|
||||
## Bridge relays (or "bridges") are Tor relays that aren't listed in the
|
||||
## main directory. Since there is no complete public list of them, even an
|
||||
## ISP that filters connections to all the known Tor relays probably
|
||||
## won't be able to block all the bridges. Also, websites won't treat you
|
||||
## differently because they won't know you're running Tor. If you can
|
||||
## be a real relay, please do; but if not, be a bridge!
|
||||
##
|
||||
## Warning: when running your Tor as a bridge, make sure than MyFamily is
|
||||
## NOT configured.
|
||||
#BridgeRelay 1
|
||||
## By default, Tor will advertise your bridge to users through various
|
||||
## mechanisms like https://bridges.torproject.org/. If you want to run
|
||||
## a private bridge, for example because you'll give out your bridge
|
||||
## address manually to your friends, uncomment this line:
|
||||
#BridgeDistribution none
|
||||
|
||||
## If non-zero, try to write to disk less frequently than we would otherwise.
|
||||
## This is useful when running on flash memory or other media that support
|
||||
## only a limited number of writes.
|
||||
#AvoidDiskWrites 1
|
||||
|
||||
## Try to use built-in (static) crypto hardware acceleration when available.
|
||||
#HardwareAccel 1
|
||||
|
||||
## If set to 1, Tor will attempt to lock all current and future memory pages,
|
||||
## so that memory cannot be paged out.
|
||||
#DisableAllSwap 1
|
||||
|
||||
## Configuration options can be imported from files or folders using the %include
|
||||
## option with the value being a path. This path can have wildcards. Wildcards are
|
||||
## expanded first, using lexical order. Then, for each matching file or folder, the following
|
||||
## rules are followed: if the path is a file, the options from the file will be parsed as if
|
||||
## they were written where the %include option is. If the path is a folder, all files on that
|
||||
## folder will be parsed following lexical order. Files starting with a dot are ignored. Files
|
||||
## on subfolders are ignored.
|
||||
## The %include option can be used recursively.
|
||||
%include /etc/tor/torrc.d/*.conf
|
||||
29
tor/PKGBUILD
29
tor/PKGBUILD
|
|
@ -1,29 +1,28 @@
|
|||
#!/usr/bin/bash
|
||||
# JOBoRun : Jwm OpenBox Obarun RUNit
|
||||
# Maintainer : Joe Bo Run <joborun@disroot.org>
|
||||
# PkgSource : url="https://gittea.disroot.org/joborun-pkg/jobcore/$pkgname"
|
||||
# PkgSource : url="https://gittea.disroot.org/joborun-pkg/jobextra/$pkgname"
|
||||
# Website : https://pozol.eu
|
||||
#-----------------------------------------| DESCRIPTION |---------------------------------------
|
||||
|
||||
pkgname=tor
|
||||
pkgver=0.4.7.8
|
||||
pkgrel=02
|
||||
pkgver=0.4.7.10
|
||||
pkgrel=01
|
||||
pkgdesc='Anonymizing overlay network. w/o zstd and systemd'
|
||||
arch=('x86_64')
|
||||
#url='https://www.torproject.org/dist'
|
||||
url="https://dist.torproject.org/"
|
||||
url="https://dist.torproject.org"
|
||||
source=("$url/$pkgname-$pkgver.tar.gz"{,.sha256sum{,.asc}}
|
||||
'torrc.patch'
|
||||
# 'torrc.patch'
|
||||
'tor.sysusers'
|
||||
'tor.tmpfiles')
|
||||
|
||||
prepare() {
|
||||
# verify the signed sums match the expected source tarball
|
||||
sha256sum -c ${pkgname}-${pkgver}.tar.gz.sha256sum
|
||||
cd ${pkgname}-${pkgver}
|
||||
# uncomment essential config sections in the torrc file
|
||||
patch -Np1 < "${srcdir}/torrc.patch"
|
||||
# verify the signed sums match the expected source tarball
|
||||
sha256sum -c ${pkgname}-${pkgver}.tar.gz.sha256sum
|
||||
cd ${pkgname}-${pkgver}
|
||||
# # uncomment essential config sections in the torrc file
|
||||
# patch -Np1 < "${srcdir}/torrc.patch"
|
||||
}
|
||||
|
||||
depends=(
|
||||
|
|
@ -50,6 +49,7 @@ build() {
|
|||
--disable-zstd-advanced-apis \
|
||||
--disable-systemd \
|
||||
--disable-html-manual \
|
||||
--disable-ipv6 \
|
||||
--enable-lzma \
|
||||
--enable-xz \
|
||||
--enable-pic
|
||||
|
|
@ -66,7 +66,7 @@ package() {
|
|||
install -Dm0644 "${srcdir}/tor.tmpfiles" "${pkgdir}/usr/lib/tmpfiles.d/tor.conf"
|
||||
|
||||
# patch upstream configuration file
|
||||
patch -Np1 < "${srcdir}/torrc.patch"
|
||||
# patch -Np1 < "${srcdir}/torrc.patch"
|
||||
|
||||
make DESTDIR="${pkgdir}" install
|
||||
|
||||
|
|
@ -85,8 +85,9 @@ validpgpkeys=(2133BC600AB133E1D826D173FE43009C4607B1FB # Nick Mathewson
|
|||
F65CE37F04BA5B360AE6EE17C218525819F78451 # Roger Dingledine
|
||||
1C1BC007A9F607AA8152C040BEA7B180B1491921) # Alexander Færøy <ahf@0x90.dk>
|
||||
|
||||
sha256sums=(9e9a5c67ad2acdd5f0f8be14ed591fed076b1708abf8344066990a0fa66fe195 # tor-0.4.7.8.tar.gz
|
||||
759c4f3146a74ba20232b351b81026ec69bfe7cb45e8cbafcaf9d3d1174609b9 # tor-0.4.7.8.tar.gz.sha256sum
|
||||
c9632d05816d7a1ccfe1e258518c130808decaee7f3544494f9d53ab828cf22c # torrc.patch
|
||||
sha256sums=(647e56dfa59ea36dab052027fcfc7663905c826c03509363c456900ecd435a5b # tor-0.4.7.10.tar.gz
|
||||
107d97106a47ea698b2f8da9f3c3610f56a58bff574ab7dc7bebffa550042cd9 # tor-0.4.7.10.tar.gz.sha256sum
|
||||
c1e0b8e612bf2a4c610c92434d99dd68d7e03863d165278d53d80938952f6a9c # tor-0.4.7.10.tar.gz.sha256sum.asc
|
||||
# 9f69d71ff03a2adef13a539c76abbbb9c8e81a52403edb26effef3222657da11 # torrc.patch
|
||||
04eec05b4e61efccc58c5da657363f0c1059d7f122cb15c32331a201af2d7f94 # tor.sysusers
|
||||
07bedb17660a3673b31b0005b6505065c90b32f2c6b28b969241da675560f926) # tor.tmpfiles
|
||||
|
|
|
|||
|
|
@ -6,32 +6,38 @@
|
|||
# Contributor: Sid Karunaratne
|
||||
|
||||
pkgname=tor
|
||||
pkgver=0.4.6.9
|
||||
pkgrel=1
|
||||
pkgver=0.4.7.8
|
||||
pkgrel=2
|
||||
pkgdesc='Anonymizing overlay network.'
|
||||
arch=('x86_64')
|
||||
url='https://www.torproject.org/'
|
||||
url='https://www.torproject.org/download/tor/'
|
||||
license=('BSD')
|
||||
depends=('openssl' 'libevent' 'bash' 'libseccomp' 'zstd' 'libcap' 'systemd-libs'
|
||||
'libsystemd.so' 'libzstd.so' 'libseccomp.so' 'libcap.so')
|
||||
optdepends=('torsocks: for torify')
|
||||
makedepends=('ca-certificates' 'systemd')
|
||||
backup=('etc/tor/torrc')
|
||||
source=("https://www.torproject.org/dist/${pkgname}-${pkgver}.tar.gz"{,.asc}
|
||||
source=("https://dist.torproject.org/${pkgname}-${pkgver}.tar.gz"{,.sha256sum{,.asc}}
|
||||
'torrc.patch'
|
||||
'tor.sysusers'
|
||||
'tor.tmpfiles'
|
||||
'tor.service')
|
||||
b2sums=('7d6add30867a3b18471bece559acbf6782b516229b8ab2c764f4a581fcbe3c2fa748f2708c60bf0f8a1165bc1fdd930fe00adaf7c1f546e6a7e98bdc0f1abb21'
|
||||
b2sums=('40f6eab453d95a09e4531ce7cdb59715a21b84e1d0b1045d107add6a443fb7563a5747734b23e0e1dfda6490a5a7659f912e38c11cdb5fa635535dcff6169eeb'
|
||||
'0fa1e094af83c74f46f87d0569a623bd3061b416f272d19326faf08ab6e9e926b14c2d46c99fba80d68f22188aa74c73e68477015e1c37382e4acb115d10a5a2'
|
||||
'SKIP'
|
||||
'3359e138d823a77df2a42ce3fe8c6ecb4004e9ec191863db7857aceea7c136c78f09518b1a199dfd3215f5d61f1c060f4a0e2141c5bdb6b847af60fb6e9a81a7'
|
||||
'9053da53926f2120ac57b6c1442238f5bbd89bf9270347c4e00b721b39939bebc6adfcf814a9d7289dfd14d085d91c193529305336db93190da5b7f586a031df'
|
||||
'5d55d9a7e42b6ce78b8ab985bab37afe8f0bacddb5abd895c4a490adb8f98b9422f90b40066fef05ecf37b7b21e80aadc615c4b7f6e12b05581304113a1b1f1d'
|
||||
'327c1a35c3d4c44f93edb47959c8c41ab6af4cbfcbb8f4e9f54f2f69d17d148bf85e2d2c8aefe2d3165e123056dd68a248af78d1ba713b94a4e6d27a9cf412f1')
|
||||
validpgpkeys=('2133BC600AB133E1D826D173FE43009C4607B1FB' # Nick Mathewson
|
||||
'F65CE37F04BA5B360AE6EE17C218525819F78451') # Roger Dingledine
|
||||
validpgpkeys=(
|
||||
'2133BC600AB133E1D826D173FE43009C4607B1FB' # Nick Mathewson
|
||||
'B74417EDDF22AC9F9E90F49142E86A2A11F48D36' # David Goulet
|
||||
'1C1BC007A9F607AA8152C040BEA7B180B1491921' # Alexander Færøy
|
||||
)
|
||||
|
||||
prepare() {
|
||||
# verify the signed sums match the expected source tarball
|
||||
sha256sum -c ${pkgname}-${pkgver}.tar.gz.sha256sum
|
||||
cd ${pkgname}-${pkgver}
|
||||
# uncomment essential config sections in the torrc file
|
||||
patch -Np1 < "${srcdir}/torrc.patch"
|
||||
|
|
|
|||
1
tor/key
1
tor/key
|
|
@ -1 +1,2 @@
|
|||
gpg --recv-keys 42E86A2A11F48D36
|
||||
gpg -v --recv-keys 6AFEE6D49E92B601
|
||||
|
|
|
|||
|
|
@ -1,28 +1,28 @@
|
|||
--- a/src/config/torrc.sample 2020-10-06 18:11:24.173821006 +0200
|
||||
+++ b/src/config/torrc.sample 2020-10-06 18:11:06.000000000 +0200
|
||||
--- a/src/config/torrc.sample.in 2021-03-10 19:59:10.123456789 +0100
|
||||
+++ b/src/config/torrc.sample.in 2021-03-10 19:59:10.123456789 +0100
|
||||
@@ -11,6 +11,7 @@
|
||||
##
|
||||
## Tor will look for this file in various places based on your platform:
|
||||
## https://www.torproject.org/docs/faq#torrc
|
||||
+User tor
|
||||
|
||||
|
||||
## Tor opens a SOCKS proxy on port 9050 by default -- even if you don't
|
||||
## configure one below. Set "SOCKSPort 0" if you plan to run Tor only
|
||||
@@ -39,7 +40,7 @@
|
||||
## Send every possible message to /var/log/tor/debug.log
|
||||
#Log debug file /var/log/tor/debug.log
|
||||
## Send every possible message to @LOCALSTATEDIR@/log/tor/debug.log
|
||||
#Log debug file @LOCALSTATEDIR@/log/tor/debug.log
|
||||
## Use the system log instead of Tor's logfiles
|
||||
-#Log notice syslog
|
||||
+Log notice syslog
|
||||
## To send all messages to stderr:
|
||||
#Log debug stderr
|
||||
|
||||
|
||||
@@ -50,7 +51,7 @@
|
||||
|
||||
|
||||
## 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.
|
||||
-#DataDirectory /var/lib/tor
|
||||
+DataDirectory /var/lib/tor
|
||||
|
||||
-#DataDirectory @LOCALSTATEDIR@/lib/tor
|
||||
+DataDirectory @LOCALSTATEDIR@/lib/tor
|
||||
|
||||
## The port on which Tor will listen for local connections from Tor
|
||||
## controller applications, as documented in control-spec.txt.
|
||||
|
|
|
|||
Loading…
Reference in New Issue