Loading etc/bridgedb.conf +0 −44 Original line number Diff line number Diff line Loading @@ -905,50 +905,6 @@ EMAIL_N_BRIDGES_PER_ANSWER = 3 # once we have the vidalia/tor interaction fixed for everbody. EMAIL_INCLUDE_FINGERPRINTS = True # # Configuration options for OpenPGP signing and encryption # ------------------------------------------------------------------------------ # Should we sign all email responses to clients with the key specified by # EMAIL_GPG_PRIMARY_KEY_FINGERPRINT (or one of its subkeys)? EMAIL_GPG_SIGNING_ENABLED = True # The directory, relative to BridgeDB's runtime directory, in which to store # OpenPGP keyrings and associated files. EMAIL_GPG_HOMEDIR = '.gnupg' # This should be a 40-character hexadecimal string containing the OpenPGP # fingerprint (without spaces) of the default primary key to use. The key # should be capable of both signing and encryption, or have subkeys capable of # such. # # The default primary key fingerprint below is BridgeDB's online signing keypair: EMAIL_GPG_PRIMARY_KEY_FINGERPRINT = 'DF811109E17C8BF134B5EEB68DC43A2848821E32' # If the key referred to by EMAIL_GPG_PRIMARY_KEY_FINGERPRINT requires a # passphrase for signing or encryption, then the passphrase may be given in # the EMAIL_GPG_PASSPHRASE option (as a string), or it may be contained within # the file pointed to by EMAIL_GPG_PASSPHRASE_FILE. Currently, only one # passphrase is supported, so if the key specified by # EMAIL_GPG_PRIMARY_KEY_FINGERPRINT has multiple subkeys, those subkeys MUST # all have the same passphrase. # # If EMAIL_GPG_PASSPHRASE_FILE is used, and the filepath is not absolute, the # path is interpreted as being relative to BridgeDB's runtime directory. # (Note: be sure not to put any newlines after the phassphrase in the # EMAIL_GPG_PASSPHRASE_FILE, or else they will be interpreted as part of the # passphrase.) # # There are currently no safety checks on the permissions of either this # configuration file or the EMAIL_GPG_PASSPHRASE_FILE, so beware and use at # your own risk. # # If both EMAIL_GPG_PASSPHRASE and EMAIL_GPG_PASSPHRASE_FILE are ``None``, # then it is assumed that the key specified by # EMAIL_GPG_PRIMARY_KEY_FINGERPRINT does not require a passphrase. EMAIL_GPG_PASSPHRASE = None EMAIL_GPG_PASSPHRASE_FILE = '.gnupg/passphrase' #------------------------------- # Hashring Allocation Options \ #------------------------------------------------------------------------------ Loading Loading
etc/bridgedb.conf +0 −44 Original line number Diff line number Diff line Loading @@ -905,50 +905,6 @@ EMAIL_N_BRIDGES_PER_ANSWER = 3 # once we have the vidalia/tor interaction fixed for everbody. EMAIL_INCLUDE_FINGERPRINTS = True # # Configuration options for OpenPGP signing and encryption # ------------------------------------------------------------------------------ # Should we sign all email responses to clients with the key specified by # EMAIL_GPG_PRIMARY_KEY_FINGERPRINT (or one of its subkeys)? EMAIL_GPG_SIGNING_ENABLED = True # The directory, relative to BridgeDB's runtime directory, in which to store # OpenPGP keyrings and associated files. EMAIL_GPG_HOMEDIR = '.gnupg' # This should be a 40-character hexadecimal string containing the OpenPGP # fingerprint (without spaces) of the default primary key to use. The key # should be capable of both signing and encryption, or have subkeys capable of # such. # # The default primary key fingerprint below is BridgeDB's online signing keypair: EMAIL_GPG_PRIMARY_KEY_FINGERPRINT = 'DF811109E17C8BF134B5EEB68DC43A2848821E32' # If the key referred to by EMAIL_GPG_PRIMARY_KEY_FINGERPRINT requires a # passphrase for signing or encryption, then the passphrase may be given in # the EMAIL_GPG_PASSPHRASE option (as a string), or it may be contained within # the file pointed to by EMAIL_GPG_PASSPHRASE_FILE. Currently, only one # passphrase is supported, so if the key specified by # EMAIL_GPG_PRIMARY_KEY_FINGERPRINT has multiple subkeys, those subkeys MUST # all have the same passphrase. # # If EMAIL_GPG_PASSPHRASE_FILE is used, and the filepath is not absolute, the # path is interpreted as being relative to BridgeDB's runtime directory. # (Note: be sure not to put any newlines after the phassphrase in the # EMAIL_GPG_PASSPHRASE_FILE, or else they will be interpreted as part of the # passphrase.) # # There are currently no safety checks on the permissions of either this # configuration file or the EMAIL_GPG_PASSPHRASE_FILE, so beware and use at # your own risk. # # If both EMAIL_GPG_PASSPHRASE and EMAIL_GPG_PASSPHRASE_FILE are ``None``, # then it is assumed that the key specified by # EMAIL_GPG_PRIMARY_KEY_FINGERPRINT does not require a passphrase. EMAIL_GPG_PASSPHRASE = None EMAIL_GPG_PASSPHRASE_FILE = '.gnupg/passphrase' #------------------------------- # Hashring Allocation Options \ #------------------------------------------------------------------------------ Loading