initial import

This commit is contained in:
2025-06-22 20:39:04 -05:00
commit f8a70886f0
3428 changed files with 302546 additions and 0 deletions

13
tor/0001.patch Normal file
View File

@@ -0,0 +1,13 @@
diff --git a/Makefile.in b/Makefile.in
index 8e1f09e..90bc44f 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -497,7 +497,7 @@ am__installdirs = "$(DESTDIR)$(bindir)" "$(DESTDIR)$(bindir)" \
@LIBFUZZER_ENABLED_TRUE@ src/test/fuzz/lf-fuzz-vrs$(EXEEXT)
PROGRAMS = $(bin_PROGRAMS) $(noinst_PROGRAMS)
LIBRARIES = $(noinst_LIBRARIES)
-ARFLAGS = cru
+ARFLAGS = crD
AM_V_AR = $(am__v_AR_@AM_V@)
am__v_AR_ = $(am__v_AR_@AM_DEFAULT_V@)
am__v_AR_0 = @echo " AR " $@;

69
tor/PKGBUILD Normal file
View File

@@ -0,0 +1,69 @@
# Maintainer: Jesus E. <heckyel@riseup.net>
pkgname=tor
pkgver=0.4.5.9
pkgrel=4
pkgdesc='Anonymizing overlay network'
arch=('i686' 'x86_64')
url='https://www.torproject.org/'
license=('Modified-BSD')
depends=('libressl' 'libevent' 'bash' 'libseccomp')
optdepends=('torsocks: for torify')
makedepends=('ca-certificates')
backup=('etc/tor/torrc'
'etc/tor/torrc-dist'
'etc/conf.d/tor')
install='tor.install'
source=("https://www.torproject.org/dist/${pkgname}-${pkgver}.tar.gz"{,.asc}
'0001.patch'
'torrc'
'tor.confd'
'tor.initd'
'tor.conf'
'tor.run')
sha512sums=('b3c3b5cce30c881fb1e705ec6183513f625ddb9d076671b9cd6299e81a410bc12f59a30677636371c336e397211432f0831bdcb2105c9aed8dcb608eae54e2b2'
'SKIP'
'b68c24f05dcfa34a9491b2082f06c61571b5bf404e80e383041d5a036e0abf46b4a813bcb507f45220a3f0791d17d8031f8ff86d12555c4b10f14e2bc040e442'
'2da22ea0432c29fa80f98fca4ccb63c735bfe7c4039e7c2630de9d3330b9ba80632af68293aec2b0ff817bd3e28542e1472ef3f1fc5e10db557d6ab810f5674a'
'9028ac41e3acdf4405095addb69537e87edecafaec840296ac27a5a8992fe132dc822e4e4abb8826f76460c438da2719dea17859690d03e17198a82086a3d660'
'c54004c92874337822cbee7646a685fd79bd4cd793560e0171d2c4fe0cd2f80a73f7acbd7be1ab2baea929314c40d15b90f8157abd0b35bb34af17d027f8cf48'
'41a26c8301864abd2129a50b03f7d7ff482023ad0185bab808c223c54b520e25b7abeb45f4ba340a0f954e984733e6fc61cb6ab7b4907547dca54ced4b363f65'
'9e307895c7c85f5c22538c27d97b2d93b1c3b29ad5964f90a5e69dd132c4e477c137e78742d475b22ad35d4c14e71c219f1ab05da5701a4598d9220767ba5c89')
validpgpkeys=('2133BC600AB133E1D826D173FE43009C4607B1FB' # Nick Mathewson
'F65CE37F04BA5B360AE6EE17C218525819F78451') # Roger Dingledine
prepare() {
cd "${pkgname}-${pkgver}"
# Fix issue https://gitlab.torproject.org/tpo/core/tor/-/issues/27309
patch -p1 -i "${srcdir}/0001.patch"
}
build() {
cd "${pkgname}-${pkgver}"
./configure \
--prefix=/usr \
--sysconfdir=/etc \
--localstatedir=/var \
--enable-lzma \
--disable-zstd-advanced-apis
make
}
package() {
cd "${pkgname}-${pkgver}"
make DESTDIR="${pkgdir}" install
install -dm0700 -o 43 -g 43 "${pkgdir}/var/lib/tor"
mv "${pkgdir}/etc/tor/torrc.sample" "${pkgdir}/etc/tor/torrc-dist"
install -Dm0644 "${srcdir}/torrc" "${pkgdir}/etc/tor/torrc"
install -Dm0644 "${srcdir}/tor.confd" "${pkgdir}/etc/conf.d/tor"
install -Dm0755 "${srcdir}/tor.initd" "${pkgdir}/etc/init.d/tor"
install -Dm0644 "${srcdir}/tor.conf" "${pkgdir}/etc/sv/tor/conf"
install -Dm0755 "${srcdir}/tor.run" "${pkgdir}/etc/sv/tor/run"
install -Dm0644 LICENSE -t "${pkgdir}/usr/share/licenses/${pkgname}"
}

11
tor/tor.conf Normal file
View File

@@ -0,0 +1,11 @@
# Set the file limit
rc_ulimit="-n 30000"
# Configuration
rc_file="/etc/tor/torrc"
# Pid-file
pidfile="/var/run/tor/tor.pid"
# Start options as daemon
tor_opts="-f \"${rc_file}\" --hush --runasdaemon 1 --pidfile \"${pidfile}\""

3
tor/tor.confd Normal file
View File

@@ -0,0 +1,3 @@
#
# Set the file limit
rc_ulimit="-n 30000"

36
tor/tor.initd Normal file
View File

@@ -0,0 +1,36 @@
#!/sbin/openrc-run
# Copyright 1999-2016 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
command=/usr/bin/tor
pidfile=/var/run/tor/tor.pid
command_args="--hush --runasdaemon 1 --pidfile \"${pidfile}\""
retry=${GRACEFUL_TIMEOUT:-60}
stopsig=INT
command_progress=yes
extra_commands="checkconfig"
extra_started_commands="reload"
description="Anonymizing overlay network for TCP"
description_checkconfig="Check for valid config file"
description_reload="Reload the configuration"
checkconfig() {
${command} --verify-config --hush > /dev/null 2>&1
if [ $? -ne 0 ] ; then
eerror "Tor configuration (/etc/tor/torrc) is not valid."
return 1
fi
}
start_pre() {
checkconfig || return 1
checkpath -d -m 0755 -o tor:tor /var/run/tor
}
reload() {
checkconfig || return 1
ebegin "Reloading Tor configuration"
start-stop-daemon -s HUP --pidfile ${pidfile}
eend $?
}

25
tor/tor.install Normal file
View File

@@ -0,0 +1,25 @@
post_install() {
if ! getent group tor &>/dev/null; then
groupadd -g 43 tor >/dev/null
fi
if ! getent passwd tor &>/dev/null; then
useradd -u 43 -g tor -d /var/lib/tor -s /bin/nologin tor >/dev/null
fi
tor_shell=$(getent passwd tor | cut -d: -f7)
if [ "$tor_shell" != '/bin/nologin' ]; then
chsh -s /bin/nologin tor &>/dev/null
fi
}
post_upgrade() {
post_install
}
post_remove() {
if getent passwd tor &>/dev/null; then
userdel tor >/dev/null
fi
if getent group tor &>/dev/null; then
groupdel tor >/dev/null
fi
}

6
tor/tor.run Normal file
View File

@@ -0,0 +1,6 @@
#!/bin/sh
[ -r ./conf ] && . ./conf
install -o tor -g tor -m 0755 -d /var/run/tor
ulimit ${rc_ulimit}
chpst -U tor:tor tor ${tor_opts}
exec pause

194
tor/torrc Normal file
View File

@@ -0,0 +1,194 @@
## Configuration file for a typical Tor user
## Last updated 22 April 2012 for Tor 0.2.3.14-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
## Default username and group the server will run as
User tor
PIDFile /var/run/tor/tor.pid
## 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 adddress: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 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
Log warn syslog
## 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.
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
## 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.
# OutboundBindAddress 10.0.0.5
## A handle for your relay, so people don't have to refer to it by key.
#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 20 KB.
## 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 KB # Throttle traffic to 100KB/s (800Kbps)
#RelayBandwidthBurst 200 KB # But allow bursts up to 200KB/s (1600Kbps)
## 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 "4 GB" may allow up to 8 GB total before
## hibernating.
##
## Set a maximum of 4 gigabytes each way per period.
#AccountingMax 4 GB
## 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
## Contact info to be published in the directory, so we can contact you
## if your relay is misconfigured or something else goes wrong. Google
## indexes this, so spammers might also collect it.
#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 potentionally reveal its IP/TCP address.
#MyFamily $keyid,$keyid,...
## 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
## 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 your public IP address. See the man page entry
## for ExitPolicyRejectPrivate if you want to allow "exit enclaving".
##
#ExitPolicy accept *:6660-6667,reject *:* # allow irc ports but no more
#ExitPolicy accept *:119 # accept nntp 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!
#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:
#PublishServerDescriptor 0