gsathya / torflow Public

Use --help to view usage.

Using --help gives the list of
options required for SoaT.

Make sure the commandline arguments are correct
before proceding. If not, show error message and
correct usage.

"Tor 0.2.3.4-alpha makes 'FetchUselessDescriptors' cause all descriptor types and
all consensus types (including microdescriptors) to get fetched.
Fixes bug 3851; bugfix on 0.2.3.1-alpha."

update README to bump library versions

recommend using newer versions of SQLAlchemy and Elixir in the README.
direct postgresql users to install python-psycopg2.

Add Appendix B: for postgres configuration

Explain how to get a postgres backend working
with BwAuthority

BwAuthority sample db_url should refer to distinct databases.

Wraps custom library imports in try/except, and
adds error messages in format:
"""
TorCtl not found in os.path.abspath($cwd/../..)
Exiting...
"""

We want to ensure they always have fresh consensus data from within the hour.

refill_targets maps add_target to a list of urls
add_target expects tuple (url, filetype) and adds
a target ('h', 't') -- probably from 'http://...'

renamed 'contet' to 'content'

replaced content_prefix+".content" with:
self.address_to_context(address)+".content",

Added this to libsoat.py

This looks safe to comment

It looks as if this was meant to be 'search_req.code' and not 'code'

fixed missing 'self'; also corrected a reference-before-assignment

missing 'self'

This fix corrects 2 references to an undefined variable sha1sum:

fix for missing sha1sum #1 just uses the sha() of the content from
the new request because compare() already declares the content equal:

if req.content == new_req.content:
  assert(sha(req.content) == sha(new_req.content))

fix for missing sha1sum #2 is to load the original content (from disk)
and compute sha(). I added a helper function load_original_sha1sum()
for clarity.

This should fix bug 2697 by allowing us to scan for failures on port 80 SSL
hosts.

Also use the new TorCtl.connect() method.

The fix for 3798 (https://trac.torproject.org/projects/tor/ticket/3798)
introduced a new error: TorCtl.Connection.close() at program exit will
occasionally cause BwAuthority to hang indefinitely. This issue was originally
reported in ticket 3834 (https://trac.torproject.org/projects/tor/ticket/3834)

TorCtl.Connection.close() should not be used at this time. The issue occurs
when called in either atexit handlers as well as at the end of the main thread.

TorCtl.Connection.close() doesn't block;
use TorCtl.Connection.block_until_close() to join the _eventLoop thread