Tor Expert Bundle confusion

I feel Tor Expert Bundle causes a lot of confusion because users (like myself) expect it to be something only experts should be using. I was trying to find just the tor binary when I couldn't until someone pointed out to me that it was the expert bundle. This naming is very confusing, unneeded and I think diverts some users looking for the binary but couldn't find it.

Why not rename it to something more obvious such as Tor Standalone?

added component::webpages/website owner::tbb-team priority::very low resolution::worksforme severity::normal status::closed type::enhancement labels

There is no any confusion with the TOR Expert Bundle. It contains just Tor and nothing else. You'll need to configure Tor and all of your applications manually. A job for experts only. I made a blind TOR relay on Windows XP with this Expert Bundle in only 10 minutes.

http://torforum.org/viewtopic.php?f=4&t=65755

After that, since Vidalia was discontinued and can't be used with the newest tor.exe versions, I made my own Python scripts (with STEM libs) to manage this server and now I have again all functionalities (including the TOR relay gracefully exit). I think this bundle is essential for the Windows users who want to help the TOR network. Not many people are capable to compile for Windows the TOR source code (minGW, dependencies, resources, etc). A clean Win32/64 tor.exe direct from developers is more consistent.

Sep 01 08:03:00.296 [notice] Tor v0.2.7.2-alpha (git-4d01238d3b7a3f9a) running on Windows XP with Libevent 2.0.21-stable, OpenSSL 1.0.1p and Zlib 1.2.8.
Sep 01 08:03:00.296 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning
Sep 01 08:03:00.296 [notice] This version is not a stable Tor release. Expect more bugs than usual.
Sep 01 08:03:00.328 [notice] Read configuration file "C:\torexpert\Data\Tor\torrc".
Sep 01 08:03:00.343 [notice] Based on detected system memory, MaxMemInQueues is set to 2048 MB. You can override this by setting MaxMemInQueues by hand.
Sep 01 08:03:00.359 [notice] Opening Socks listener on 127.0.0.1:9050
Sep 01 08:03:00.375 [notice] Opening Control listener on 127.0.0.1:9151
Sep 01 08:03:00.390 [notice] Opening OR listener on 0.0.0.0:9001
Sep 01 08:03:00.421 [notice] Opening Directory listener on 0.0.0.0:9030
Sep 01 08:03:00.000 [notice] Parsing GEOIP IPv4 file C:\torexpert\Data\Tor\geoip.
Sep 01 08:03:00.000 [notice] Parsing GEOIP IPv6 file C:\torexpert\Data\Tor\geoip6.
Sep 01 08:03:01.000 [notice] Your Tor server's identity key fingerprint is 'TORques CD0EB85333B9A20F6D676605F01CC5143E69F82F'
Sep 01 08:03:01.000 [notice] Bootstrapped 0%: Starting
Sep 01 08:03:11.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Sep 01 08:03:12.000 [notice] Bootstrapped 85%: Finishing handshake with first hop
Sep 01 08:03:12.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Sep 01 08:03:13.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Sep 01 08:03:13.000 [notice] Bootstrapped 100%: Done
Sep 01 08:03:13.000 [notice] Now checking whether ORPort 109.103.57.102:9001 and DirPort 109.103.57.102:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Sep 01 08:03:14.000 [warn] Failure from drain_fd
Sep 01 08:03:14.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Sep 01 08:03:15.000 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
Sep 01 08:03:16.000 [notice] Performing bandwidth self-test...done.
Sep 01 08:03:38.000 [notice] New control connection opened from 127.0.0.1.
Sep 01 08:03:49.000 [notice] New control connection opened from 127.0.0.1.
Sep 01 08:03:50.000 [notice] Catching signal TERM, exiting cleanly.

Explain me instead what is this warning: Sep 01 08:03:14.000 [warn] Failure from drain_fd

A multithreading conflict in Windows when a file is read by more threads? - drain_fd(fd, buf = nil) ⇒ true, false (Do nonblocking reads from fd, appending all data read into buf.)

Trac:
Username: TORques

That's what I call a "Tor Standalone": Tor v0.2.7.2-alpha (git-36c0ae6f7834af16) running on Windows XP with Libevent 2.0.22-stable, OpenSSL 1.0.2d and Zlib 1.2.8. - I built my own TOR - A single tor.exe with no DLL's - It's working with logout on console! ;-)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\tornou\Tor>tor -f C:\tornou\Data\Tor\torrc
Sep 03 02:42:33.294 [notice] Tor v0.2.7.2-alpha (git-36c0ae6f7834af16) running o
n Windows XP with Libevent 2.0.22-stable, OpenSSL 1.0.2d and Zlib 1.2.8.
Sep 03 02:42:33.294 [notice] Tor can't help you if you use it wrong! Learn how t
o be safe at https://www.torproject.org/download/download#warning
Sep 03 02:42:33.294 [notice] This version is not a stable Tor release. Expect mo
re bugs than usual.
Sep 03 02:42:33.403 [notice] Read configuration file "C:\tornou\Data\Tor\torrc".
Sep 03 02:42:33.419 [notice] Based on detected system memory, MaxMemInQueues is
set to 2048 MB. You can override this by setting MaxMemInQueues by hand.
Sep 03 02:42:33.466 [notice] Opening Socks listener on 127.0.0.1:9050
Sep 03 02:42:33.481 [notice] Opening Control listener on 127.0.0.1:9151
Sep 03 02:42:33.497 [notice] Opening OR listener on 0.0.0.0:9001
Sep 03 02:42:33.513 [notice] Opening Directory listener on 0.0.0.0:9030
Sep 03 02:42:33.000 [notice] Parsing GEOIP IPv4 file C:\tornou\Data\Tor\geoip.
Sep 03 02:42:33.000 [notice] Parsing GEOIP IPv6 file C:\tornou\Data\Tor\geoip6.
Sep 03 02:42:34.000 [notice] Configured to measure statistics. Look for the *-st
ats files that will first be written to the data directory in 24 hours from now.
Sep 03 02:42:34.000 [notice] Your Tor server's identity key fingerprint is 'TORq
ues CD0EB85333B9A20F6D676605F01CC5143E69F82F'
Sep 03 02:42:34.000 [notice] Bootstrapped 0%: Starting
Sep 03 02:42:43.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Sep 03 02:42:44.000 [notice] Bootstrapped 85%: Finishing handshake with first ho
p
Sep 03 02:42:44.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Sep 03 02:42:44.000 [notice] Tor has successfully opened a circuit. Looks like c
lient functionality is working.
Sep 03 02:42:44.000 [notice] Bootstrapped 100%: Done
Sep 03 02:42:44.000 [notice] Now checking whether ORPort 109.103.57.102:9001 and
 DirPort 109.103.57.102:9030 are reachable... (this may take up to 20 minutes --
 look for log messages indicating success)
Sep 03 02:42:45.000 [notice] Self-testing indicates your DirPort is reachable fr
om the outside. Excellent.
Sep 03 02:42:45.000 [warn] Failure from drain_fd
Sep 03 02:42:45.000 [notice] Self-testing indicates your ORPort is reachable fro
m the outside. Excellent. Publishing server descriptor.
Sep 03 02:42:49.000 [notice] Performing bandwidth self-test...done.

Clean install.

Trac:
Username: TORques

Replying to TORques:

Explain me instead what is this warning: Sep 01 08:03:14.000 [warn] Failure from drain_fd

There was this bug: https://trac.torproject.org/projects/tor/ticket/16741

Fixed 2 weeks ago: https://gitweb.torproject.org/tor.git/commit/?id=f724b2e5aaded4bc471b72f39eb990cc4114cb90

Trac:
Username: someone_else

Trac:
Sponsor: N/A to N/A
Milestone: N/A to Tor: 0.2.???

This is actually a Tor Browser/Website thing, and it's also trivial priority.

Trac:
Milestone: Tor: 0.2.??? to N/A
Owner: N/A to tbb-team
Priority: normal to trivial
Component: Tor to Tor Browser
Type: defect to enhancement

Trac:
Cc: N/A to gk

Moving to the website component, and also closing.

We call it the expert bundle so ordinary users won't be confused into fetching it and thinking that they should be able to make it work.

Trac:
Severity: N/A to Normal
Component: Tor Browser to Website
Reviewer: N/A to N/A
Resolution: N/A to worksforme
Status: new to closed

closed

moved to tpo/web/trac#16928 (closed)