Set UseEntryGuards=1 in entrycons.py

Torperfs that were piggybacked with entrycons.py to select their guards were still disabling guard nodes with UseEntryNodes 1.

added actualpoints::1 component::metrics/collector owner::mikeperry points::1 priority::medium resolution::fixed status::closed type::defect labels

This fix and the script that found the issue are in mikeperry/bug2566 for torperf's git.

Trac:
Resolution: N/A to fixed
Status: new to closed

Trac:
Resolution: fixed to N/A
Status: closed to reopened
Points: N/A to 1

Trac:
Status: reopened to assigned
Owner: 1 to mikeperry

I love you too, trac.

Trac:
Resolution: N/A to fixed
Status: assigned to closed

Not so fast. We should merge your fix, plus the fact that we were not redirecting stderr. See branch bug2566 in my public repository which is based on yours.

Trac:
Resolution: fixed to N/A
Status: closed to reopened

Trac:
Status: reopened to needs_review

I'm not sure I like {{{

• conn.set_option("StrictEntryNodes", "1")

• conn.set_option("UseEntryNodes", "1")
• conn.set_option("StrictNodes", "1") }}} unless we are extra sure we don't want to run torperfs on 0.2.1.x tors

Sebastian says that 0.2.2.x will work just fine with StrictEntryNodes. So let's undo that change, so that we can support 0.2.1.x, too. But let's keep UseEntryNodes 1 in, because it does no harm.

Thanks, merged with my suggested fix.

Trac:
Status: needs_review to closed
Resolution: N/A to fixed

closed

changed time estimate to 8h

added 8h of time spent

mentioned in issue #2571 (moved)

mentioned in issue tpo/core/tor#2571 (closed)