• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

isislovecruft / bridgedb / 752 / 3
80%
develop: 91%

Build:
Build:
LAST BUILD BRANCH: bridgedb-0.6.5
DEFAULT BRANCH: develop
Ran 22 Feb 2015 12:27AM UTC
Files 37
Run time 7s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

21 Feb 2015 11:05PM UTC coverage: 77.097%. First build
TWISTED_VERSION=15.0.0 PYOPENSSL_VERSION=0.14

push

travis-ci

isislovecruft
Don't insert bridges in NO_DISTRIBUTION_COUNTRIES into the hashrings.

When two-letter country codes are given in the bridgedb.conf option
NO_DISTRIBUTION_COUNTRIES, e.g.:

    NO_DISTRIBUTION_COUNTRIES = ['IR', 'SY']

and a Bridge parsed from the descriptor files is found to be geolocated
in one of these countries, we skip adding that Bridge to the hashrings
entirely.

 * FIXES #12843 https://bugs.torproject.org/12843

 * TODO We could add these blacklisted Bridges to their own hashring of
   Undistributables which are never to be distributed to real clients.

   Potentially, we could distribute these Undistributables to
   adversaries which are definitely not real clients, as a form of
   supplying adversaries with decoys (see #12537).  By doing so, we
   would be handing an adversary which is probably some intelligence
   agency's bridge enumeration program (e.g. part of the NSA and GCHQ's
   HOMING TROLL and XKEYSCORE programmes) bridges which are run by
   another intelligence agency (presumedly واجا (VAJA) and/or إدارة
   الأمن العام) in order to gather information about the clients
   connecting to them (presumedly hoping that someone from their
   jurisdiction would use the bridge).  Thus, in the best case scenario,
   feeding each agency false (albeit trivially discoverable as false)
   information on the other and — in the worst case scenario — simply
   being an annoyance by breaking things for both parties.

   However, the current organisation of the hashring structures is not
   really amenable to adding hashrings for Undistributables — at least
   not in any way that safely guarantees that they wouldn't end up in
   some bucket or such intended for real clients (which would defeat the
   whole purpose of this patch).  Because of this concern, using
   Undistributables as decoys is not yet feasible.

3484 of 4519 relevant lines covered (77.1%)

0.77 hits per line

Source Files on job 752.3 (TWISTED_VERSION=15.0.0 PYOPENSSL_VERSION=0.14)
  • Tree
  • List 0
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 752
  • Travis Job 752.3
  • f80033f8 on github
  • Next Job for TWISTED_VERSION=15.0.0 PYOPENSSL_VERSION=0.14 on fix/12843-cc-spurning_r2 (#753.3)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc