# -*- mode: python ; coding: utf-8 -*- # # +---------------+ # | bridgedb.conf | # +---------------+ # # This file uses Python syntax, and is sourced as if it were a .py file. Just # pretend you're writing Python, and everything will be peachy keen. #______________________________________________________________________________ # # Part of BridgeDB, a Tor bridge distribution system. # # :authors: The Tor Project, Inc. # :license: This file is freely distributed as part of BridgeDB, see LICENSE # for details. # :copyright: (c) 2007-2013 The Tor Project, Inc. # (c) 2007-2013, all sentient entities within the AUTHORS file # :version: 0.0.8 #=============================================================================== # # CHANGELOG: # ~~~~~~~~~~ # Changes in version 0.0.8 - 2014-05-14 # * CHANGE RECAPTCHA_PRIV_KEY to RECAPTCHA_SEC_KEY. # # Changes in version 0.0.7 - 2014-03-31 # * ADD new settings for tracing function calls and thread info within logged # messages: LOG_THREADS, LOG_TRACE, and LOG_TIME_FORMAT. # # Changes in version 0.0.6 - 2014-03-28 # * CHANGE gimp-captchas to be the norm. # * ADD bucket for support team. # # Changes in version 0.0.5 - 2014-02-27 # * ADD GIMP_CAPTCHA_ENABLED, GIMP_CAPTCHA_DIR, GIMP_CAPTCHA_HMAC_KEYFILE, # and GIMP_CAPTCHA_RSA_KEYFILE settings (see #10809). # * Decrease email share. # * Whitelist the public IP address of bridges.torproject.org in # RECAPTCHA_REMOTE_IP setting. # # Changes in version 0.0.4 - 2014-01-24 # * ADD COLLECT_TIMESTAMPS option (see #10724). Set it to False for the # staging instance (etc/test-bridgedb.conf), and True for the production # server (etc/bridgedb.conf). # # Changes in version 0.0.3 - 2014-01-17 # * UPDATE config from bridgedb.git/bridgedb.conf, without changing any of the # settings. # # Changes in version 0.0.2 - 2014-01-17 # * ADD missing settings, EMAIL_GPG_SIGNING_ENABLED and EMAIL_GPG_SIGNING_KEY. # # Changes in version 0.0.1 - 2013-08-30 # * ADD version of config file in use on ponticum. # - Two config variables, RECAPTCHA_PUB_KEY and RECAPTCHA_PRIV_KEY, have # been removed, they can be found in: # patches/001-bridgedb-conf-recaptcha-vars.patch. # * CLEANUP the config file slightly (such as adding these headers) and # fixing the linewraps. No other variables were touched. # #=============================================================================== #===========================# # General-purpose options # #___________________________# #---------------- # Required Files \ You'll want to make sure that these ones exist! #------------------------------------------------------------------------------ # # All filenames are taken as relative to the RUNTIME directory, which is the # current working directory when you call the ``bridgedb`` script, or you may # specify a particular RUNTIME directory by doing: # # $ bridgedb -r /path/to/some/nice/place # # Obviously, this config file should live in that directory, so that BridgeDB # can read it. #------------------------------------------------------------------------------ # List of filenames from which we read ``@type bridge-server-descriptor``s, on # startup and on SIGHUP. BRIDGE_FILES = ["bridge-descriptors"] # List of filenames from which we read ``@type bridge-extra-info`` # descriptors, for learning about a bridge's pluggable transports: EXTRA_INFO_FILES = ["cached-extrainfo", "cached-extrainfo.new"] # Filename from which we read ``@type bridge-network-status`` entries, for # learning which current bridges are Running, as well as their IPv6 addresses. STATUS_FILE = "networkstatus-bridges" # Certificate file and private key for the HTTPS Distributor. To create a # self-signed cert, run ``scripts/make-ssl-cert`` it will create these files # in your current directory. HTTPS_CERT_FILE="cert" HTTPS_KEY_FILE="privkey.pem" #---------------- # Output Files \ Where to store created data #------------------------------------------------------------------------------ # # These will get automatically created for you, just specify where they should # go. #------------------------------------------------------------------------------ # Either a file to log to, or None if we should log to the console. LOGFILE = "bridgedb.log" # File in which to write our pid PIDFILE = "bridgedb.pid" # Filename of the database to store persistent info in. DB_FILE = "bridgedist.db" # Filename to log changes to persistent info in. For debugging and bugfixing. DB_LOG_FILE = "bridgedist.log" # Filename where we store our secret HMAC root key. This file and the key # inside are automatically created for you if they do not exist. MASTER_KEY_FILE = "secret_key" # File to which we dump bridge pool assignments for statistics. ASSIGNMENTS_FILE = "assignments.log" #------------------ # Logging Options \ #------------------------------------------------------------------------------ # # Be sure to also see the LOGFILE option above! #------------------------------------------------------------------------------ # One of "DEBUG", "INFO", "WARNING", "ERROR", or "FATAL: LOGLEVEL = "DEBUG" # If true, we scrub all potentially identifying information before we log it SAFELOGGING = True # Logfile rotation settings LOGFILE_COUNT = 5 LOGFILE_ROTATE_SIZE = 10000000 # If True, include thread IDs and numbers in log messages, if available: LOG_THREADS = False # If True, include the module name, function name, and line number of the # calling function where the log message was generated: LOG_TRACE = True # A strftime(3) format string that specifies how to log timestamps: LOG_TIME_FORMAT = "%H:%M:%S" #--------------------------- # Database/Parsing Options \ #------------------------------------------------------------------------------ # # These options change various database transaction and descriptor parsing # behaviours. #------------------------------------------------------------------------------ # (boolean) If True, then collect, sort, and store all timestamps seen for all # bridges. This operation is extremely expensive, and should be disabled when # it is not necessary. COLLECT_TIMESTAMPS = True #------------------------------- # General Distribution Options \ #------------------------------------------------------------------------------ # # These options are not specific to a certain distributor and they may alter # the bridge selection process in certain circumstances. #------------------------------------------------------------------------------ # Filename that contains blocked bridges list. Comment out to disable. #COUNTRY_BLOCK_FILE = "blocked-bridges" # A list of filenames that contain IP addresses (one per line) of proxies. # All IP-based distributors that see an incoming connection from a proxy # will treat them specially. PROXY_LIST_FILES = [] # How many clusters do we group IPs in when distributing bridges based on IP? # Note that if PROXY_LIST_FILES is set (below), what we actually do here # is use one higher than the number here, and the extra cluster is used # for answering requests made by IP addresses in the PROXY_LIST_FILES file. N_IP_CLUSTERS = 4 # If possible, always give a certain number of answers with a given ORPort. # This is a list of ``(port, minimum)`` tuples. FORCE_PORTS = [(443, 1)] # If possible, always give a certain number of answers with a given flag. # Only "Stable" is now supported. This is a list of (flag,minimum) tuples. FORCE_FLAGS = [("Stable", 1)] # Only consider routers whose purpose matches this string. BRIDGE_PURPOSE = "bridge" #------------------------------- # HTTP(S) Distribution Options \ #------------------------------------------------------------------------------ # # These options configure the behaviour of the web interface bridge # distribution mechanism. If HTTPS_DIST is enabled, make sure that the above # HTTPS_CERT_FILE and HTTPS_KEY_FILE options point to the correct location of # your SSL certificate and key! #------------------------------------------------------------------------------ # (boolean) True to enable distribution via HTTP or HTTPS; False otherwise. HTTPS_DIST = True # (string or None) The IP address where we listen for HTTPS connections. If # ``None``, listen on the default interface. HTTPS_BIND_IP = '127.0.0.1' # (integer or None) The port to listen on for incoming HTTPS connections. HTTPS_PORT = 6789 # How many bridges do we give back in an answer (either HTTP or HTTPS)? HTTPS_N_BRIDGES_PER_ANSWER = 3 # Should we tell http users about the bridge fingerprints? Turn this on # once we have the vidalia/tor interaction fixed for everbody. HTTPS_INCLUDE_FINGERPRINTS = True # If true, there is a trusted proxy relaying incoming messages to us: take # the *last* entry from its X-Forwarded-For header as the client's IP. HTTPS_USE_IP_FROM_FORWARDED_HEADER = False # (string or None) The IP address to listen on for unencrypted HTTP # connections. Set to ``None`` to disable unencrypted connections to the web # interface. HTTP_UNENCRYPTED_BIND_IP = None # (integer or None) The port to listen on for incoming HTTP connections. HTTP_UNENCRYPTED_PORT = None # (boolean) Same as the HTTPS_USE_IP_FROM_FORWARDED_HEADER option, but for # unencrypted connections. HTTP_USE_IP_FROM_FORWARDED_HEADER = False # Options related to recaptcha support. # Enable/Disable recaptcha RECAPTCHA_ENABLED = False # Recaptcha API keys RECAPTCHA_PUB_KEY = '' RECAPTCHA_SEC_KEY = '' # The remoteip we send to reCAPTCHA during verification RECAPTCHA_REMOTEIP = '' # If true, use a local cache of generated CAPTCHAs: GIMP_CAPTCHA_ENABLED = True # The directory for the local CAPTCHA cache: GIMP_CAPTCHA_DIR = 'captchas' # The location of the files which store the HMAC secret key and RSA keypair # (for checking captcha responses): GIMP_CAPTCHA_HMAC_KEYFILE = 'captcha_hmac_key' GIMP_CAPTCHA_RSA_KEYFILE = 'captcha_rsa_key' #------------------------------- # Email Distribution Options \ #------------------------------------------------------------------------------ # # These options configure the behaviour of the email bridge distribution # mechanism. If EMAIL_DIST is enabled, make sure that the above # HTTPS_CERT_FILE and HTTPS_KEY_FILE options point to the correct location of # your SSL certificate and key! # ------------------------------------------------------------------------------ # True if we are enabling distribution via Email; false otherwise. EMAIL_DIST = True # What email addresses do we use for outgoing email? # EMAIL_FROM_ADDR goes in the 'From:' header on outgoing emails: EMAIL_FROM_ADDR = "bridges@torproject.org" # EMAIL_SMTP_FROM_ADDR goes in the 'MAIL FROM:' command in outgoing SMTP: EMAIL_SMTP_FROM_ADDR = "bridges@torproject.org" EMAIL_SMTP_HOST = "127.0.0.1" EMAIL_SMTP_PORT = 25 # Reject any RCPT TO lines that aren't to this user. EMAIL_USERNAME = "bridges" # Canonical versions of domains that we will reply to. EMAIL_DOMAINS = ["gmail.com", "yahoo.com"] # Map from unofficial domain to canonical domain. EMAIL_DOMAIN_MAP = {"mail.google.com": "gmail.com", "googlemail.com": "gmail.com"} # Map from canonical domain to list of options for that domain. Recognized # options are: # "ignore_dots" -- the service ignores "." characters in email addresses. # "dkim" -- if there is not a X-DKIM-Authentication-Result header # with the value "pass", then drop the message. # # Note that unrecognized options are ignored; be sure to spell them right! EMAIL_DOMAIN_RULES = {'gmail.com': ["ignore_dots", "dkim"], 'yahoo.com': ["dkim"]} # If there are any IPs in this list, only allow incoming connections from # those IPs. EMAIL_RESTRICT_IPS = [] # IP and port to listen on for email connections. Debugging only. EMAIL_BIND_IP = "127.0.0.1" EMAIL_PORT = 6725 # How many bridges do we give back in an answer? EMAIL_N_BRIDGES_PER_ANSWER = 3 # Should we tell http users about the bridge fingerprints? Turn this on # once we have the vidalia/tor interaction fixed for everbody. EMAIL_INCLUDE_FINGERPRINTS = True # Configuration options for GPG signed messages EMAIL_GPG_SIGNING_ENABLED = True EMAIL_GPG_SIGNING_KEY = 'gnupghome/TESTING.subkeys.sec' #------------------------------- # Hashring Allocation Options \ #------------------------------------------------------------------------------ # # These options determine the proportions of bridges per hashring. When # BridgeDB receives a descriptor for a new bridge, that bridge is assigned to # a hashring. For example, if ``HTTPS_DIST`` and ``EMAIL_DIST`` are both # enabled, there is a hashring for bridges allocated to the HTTP(S) # Distributor, and another for the Email Distributor. In addition, an # "Unallocated" hashring is always created, in order to reserve some portion # of bridges for manual distribution, or as backup in the case of a major # blocking event. Once a bridge is assigned to one of these allocation groups, # it stays there; there is currently no mechanism for changing a bridge's # hashring allocation. # # Once a bridge is assigned to either of the first two groups, it stays there # persistently. The bridges are allocated to these groups in a proportion of # # ``HTTPS_SHARE`` : ``EMAIL_SHARE`` : ``RESERVED_SHARE`` # ------------------------------------------------------------------------------ # The proportion of bridges to allocate to HTTP distribution. HTTPS_SHARE = 10 # The proportion of bridges to allocate to Email distribution. EMAIL_SHARE = 5 # An integer specifying the proportion of bridges which should remain # unallocated, for backup usage and manual distribution. RESERVED_SHARE = 2 # A dictionary of {FILENAME: NUMBER} where FILENAME is a string specifying the # filename to store a certain NUMBER (an integer) of bridges in. The number of # bridges here is *not* a share/proportion, as above; instead it's literally # the number of bridges. See the ``README`` for more details. FILE_BUCKETS = {}