1. 10 May, 2021 1 commit
  2. 07 May, 2021 10 commits
  3. 21 Apr, 2021 4 commits
  4. 19 Apr, 2021 3 commits
  5. 14 Apr, 2021 3 commits
  6. 13 Apr, 2021 7 commits
  7. 08 Apr, 2021 1 commit
    • David Goulet's avatar
      guard: Don't check bridge transport name when selecting eligible guards · 218f9f90
      David Goulet authored
      This is related to ticket #40360 which found this problem when a Bridge entry
      with a transport name (let say obfs4) is set without a fingerprint:
      
        Bridge obfs4 <IP>:<PORT> cert=<...> iat-mode=0
      
      (Notice, no fingerprint between PORT and "cert=")
      
      Problem: commit 09c6d032
      
       added a check in
      get_sampled_guard_for_bridge() that would return NULL if the selected bridge
      did not have a valid transport name (that is the Bridge transport name that
      corresponds to a ClientTransportPlugin).
      
      Unfortuantely, this function is also used when selecting our eligible guards
      which is done *before* the transport list is populated and so the added check
      for the bridge<->transport name is querying an empty list of transports
      resulting in always returning NULL.
      
      For completion, the logic is: Pick eligible guards (use bridge(s) if need be)
      then for those, initiate a connection to the pluggable transport proxy and
      then populate the transport list once we've connected.
      
      Back to get_sampled_guard_for_bridge(). As said earlier, it is used when
      selecting our eligible guards in a way that prevents us from selecting
      duplicates. In other words, if that function returns non-NULL, the selection
      continues considering the bridge was sampled before. But if it returns NULL,
      the relay is added to the eligible list.
      
      This bug made it that our eligible guard list was populated with the *same*
      bridge 3 times like so (remember no fingerprint):
      
        [info] entry_guards_update_primary(): Primary entry guards have changed. New primary guard list is:
        [info] entry_guards_update_primary():   1/3: [bridge] ($0000000000000000000000000000000000000000)
        [info] entry_guards_update_primary():   2/3: [bridge] ($0000000000000000000000000000000000000000)
        [info] entry_guards_update_primary():   3/3: [bridge] ($0000000000000000000000000000000000000000)
      
      When tor starts, it will find the bridge fingerprint by connecting to it and
      will then update the primary guard list by calling
      entry_guard_learned_bridge_identity() which then goes and update only 1 single
      entry resulting in this list:
      
        [debug] sampled_guards_update_consensus_presence(): Sampled guard [bridge] ($<FINGERPRINT>) is still listed.
        [debug] sampled_guards_update_consensus_presence(): Sampled guard [bridge] ($0000000000000000000000000000000000000000) is still listed.
        [debug] sampled_guards_update_consensus_presence(): Sampled guard [bridge] ($0000000000000000000000000000000000000000) is still listed.
      
      And here lies the problem, now tor is stuck attempting to wait for a valid
      descriptor for at least 2 guards where the second one is a bunch of zeroes and
      thus tor will never fully bootstraps:
      
        [info] I learned some more directory information, but not enough to build a
        circuit: We're missing descriptors for 1/2 of our primary entry guards
        (total microdescriptors: 6671/6703). That's ok. We will try to fetch missing
        descriptors soon.
      
      Now, why passing the fingerprint then works? This is because the list of
      guards contains 3 times the same bridge but they all have a fingerprint and so
      the descriptor can be found and tor can bootstraps.
      
      The solution here is to entirely remove the transport name check in
      get_sampled_guard_for_bridge() since the transport_list is empty at that
      point. That way, the eligible guard list only gets 1 entry, the bridge, and
      can then go on to bootstrap properly.
      
      It is OK to do so since when launching a bridge descriptor fetch, we validate
      that the bridge transport name is OK and thus avoid connecting to a bridge
      without a ClientTransportPlugin. If we wanted to keep the check in place, we
      would need to populate the transport_list much earlier and this would require
      a much bigger refactoring.
      
      Fixes #40360
      Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
      218f9f90
  8. 07 Apr, 2021 1 commit
    • Nick Mathewson's avatar
      Try making our configure.ac script build with AC 2.70. · 02816d60
      Nick Mathewson authored
      In versions <=2.69, according to the autoconf docs, AC_PROG_CC_C99
      is needed with some compilers, if they require extra arguments to
      build C99 programs.  In versions >=2.70, AC_PROG_CC checks for these
      compilers automatically, and so the AC_PROG_CC_C99 macro is
      obsolete.
      
      So, what can you do if you want your script to work right with both
      autoconf versions?  IIUC, neither including AC_PROG_CC_C99 macro nor
      leaving it out will give you the right behavior with both versions.
      It looks like you need to look at the autoconf version explicitly.
      
      (Now, the autoconf manual implies that it's "against autoconf
      philosophy" to look at the autoconf version rather than trying the
      behavior to see if it works, but they don't actually tell you how to
      detect recoverably at autoconf-time whether a macro is obsolete or
      not, and I can't find a way to do that.)
      
      So, is it safe to use m4_version_prereq, like I do here?  It isn't
      listed in the autoconf 2.63 manual (which is the oldest version we
      support).  But a mailing list message [1] (which added the
      documentation back in 2008) implies that m4_version_prereq has been
      there since "at least back to autoconf 2.59".
      
      https://lists.gnu.org/archive/html/autoconf-patches/2008-12/msg00025.html
      
      So I think this will work.
      
      I am basing this patch against Tor 0.3.5 since, if autoconf 2.70
      becomes widespread before 0.3.5 is unsupported, we might need this
      patch to continue 0.3.5 development.  But I don't think we should
      backport farther than 0.4.5 until/unless that actually happens.
      
      This is part of a fix for #40355.
      02816d60
  9. 26 Mar, 2021 1 commit
    • Jigsaw52's avatar
      Fix glob processing on BSD systems. #40318 · 36768b57
      Jigsaw52 authored
      On Linux systems, glob automatically ignores the errors ENOENT and
      ENOTDIR because they are expected during glob expansion. But BSD
      systems do not ignore these, resulting in glob failing when globs
      expand to invalid paths. This is fixed by adding a custom error
      handler that ignores only these two errors and removing the
      GLOB_ERR flag as it makes glob fail even if the error handler
      ignores the error and is unnecessary as the error handler will
      make glob fail on all other errors anyway.
      36768b57
  10. 24 Mar, 2021 1 commit
  11. 23 Mar, 2021 1 commit
  12. 17 Mar, 2021 1 commit
  13. 16 Mar, 2021 5 commits
  14. 15 Mar, 2021 1 commit