[Tor-BSD] Building Tor 0.2.7.x on OpenBSD
list at sysfu.com
Wed Jul 15 16:52:02 EDT 2015
On Wed, 15 Jul 2015 12:23:50 -0700, Michael McConville
<mmcconville at mykolab.com> wrote:
> Has anyone got this to work? I tried it on OpenBSD-current within the
> past month, but it seemed that the system Libevent was too old and the
> the Libevent 2 port presented a lot of problems.
I was able to get it to build from source no problem with these commands
on OpenBSD 5.7 amd64 w/LibreSSL 2.2.1
./configure --sysconfdir=/etc --with-openssl-dir=/usr/local
CFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib make check
sudo make uninstall
Startup log file:
Jul 16 06:50:56.000 [notice] Catching signal TERM, exiting cleanly.
Jul 16 06:50:59.000 [notice] Tor 0.2.7.1-alpha (git-df76da0f3bfd6897)
opening log file.
Jul 16 06:50:59.222 [notice] Tor v0.2.7.1-alpha (git-df76da0f3bfd6897)
running on OpenBSD with Libevent 1.4.15-stable, OpenSSL LibreSSL 2.2.1 and
Jul 16 06:50:59.222 [notice] Tor can't help you if you use it wrong! Learn
how to be safe at https://www.torproject.org/download/download#warning
Jul 16 06:50:59.222 [notice] This version is not a stable Tor release.
Expect more bugs than usual.
Jul 16 06:50:59.223 [notice] Read configuration file "/etc/tor/torrc".
Jul 16 06:50:59.227 [warn] Tor is currently configured as a relay and a
hidden service. That's not very secure: you should probably run your
hidden service in a separate Tor process, at least -- see
Jul 16 06:50:59.227 [notice] Based on detected system memory,
MaxMemInQueues is set to 563 MB. You can override this by setting
MaxMemInQueues by hand.
Jul 16 06:50:59.227 [warn] Using accounting with a hidden service and an
ORPort is risky: your hidden service(s) and your public address will all
turn off at the same time, which may alert observers that they are being
run by the same party.
Jul 16 06:50:59.228 [warn] Tor is running as an exit relay. If you did not
want this behavior, please set the ExitRelay option to 0. If you do want
to run an exit Relay, please set the ExitRelay option to 1 to disable this
warning, and for forward compatibility.
Jul 16 06:50:59.232 [notice] Opening Socks listener on 127.0.0.1:9050
Jul 16 06:50:59.232 [notice] Opening OR listener on 0.0.0.0:9001
Jul 16 06:50:59.232 [notice] Opening OR listener on
Jul 16 06:50:59.000 [warn] Failed to unlink /var/tor/bw_accounting:
Operation not permitted
Jul 16 06:50:59.000 [notice] We were built to run on a 64-bit CPU, with
OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently
lacks accelerated support for the NIST P-224 and P-256 groups. Building
openssl with such support (using the enable-ec_nistp_64_gcc_128 option
when configuring it) would make ECDH much faster.
Jul 16 06:50:59.000 [notice] Your Tor server's identity key fingerprint is
Jul 16 06:50:59.000 [notice] Configured hibernation. This interval began
at 2015-07-15 19:45:00; the scheduled wake-up time was 2015-07-15
19:45:00; we expect to exhaust our quota for this interval around
2015-07-16 19:45:00; the next interval begins at 2015-07-16 19:45:00 (all
Jul 16 06:50:59.000 [notice] Parsing GEOIP IPv4 file
Jul 16 06:50:59.000 [notice] Parsing GEOIP IPv6 file
Jul 16 06:50:59.000 [notice] Configured to measure statistics. Look for
the *-stats files that will first be written to the data directory in 24
hours from now.
Jul 16 06:50:59.000 [notice] Bootstrapped 0%: Starting
Jul 16 06:51:04.000 [notice] Bootstrapped 80%: Connecting to the Tor
Jul 16 06:51:04.000 [notice] Self-testing indicates your ORPort is
reachable from the outside. Excellent. Publishing server descriptor.
Jul 16 06:51:05.000 [notice] Bootstrapped 85%: Finishing handshake with
Jul 16 06:51:06.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Jul 16 06:51:08.000 [notice] Tor has successfully opened a circuit. Looks
like client functionality is working.
Jul 16 06:51:08.000 [notice] Bootstrapped 100%: Done
More information about the Tor-BSD