| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | | |
| | |
| | |
| | |
| | | |
* ADD a new function, bridgedb.crypto.writeKeyToFile(), which is merely the
keyfile writing logic from bridgedb.crypto.getKey().
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
* MOVE bridgedb.Bridges.get_hmac() → bridgedb.crypto.getHMAC()
* MOVE bridgedb.Bridges.get_hmac_fn() → bridgedb.crypto.getHMACFunc()
* CHANGE all other modules which use these functions to use the newer
ones.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
do so.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
* ADD GimpCaptcha class, which handles retrieving cached CAPTCHAs from a
local directory, creating challenge strings from the CAPTCHA answers, and
later checking a client's proposed solution against the challenge.
* FIXES #10809.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This sounds bad. It is. What's worse: this only fixes half the
problem. The recaptcha.client.captcha.submit() function in the reCaptcha
API [0] is hardcoded to submit the server's (in this case, BridgeDB's)
private API key, the client's IP address (BridgeDB sends a faked one),
and the client's solution to the CAPTCHA, all over HTTP, in glorious
plaintext. Hooray.
[0]: https://recaptcha.googlecode.com/svn/trunk/recaptcha-plugins/python/recaptcha/client/captcha.py
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* CHANGE captcha.CaptchaProtectedResource class to only implement
general CAPTCHA functionality.
* CHANGE render_* methods in captcha.CaptchaProtectedResource to call
subclass overridable methods for actions which are implementation
specific, i.e. only the reCaptcha class needs to create a fake IP
address for a client (see the new
ReCaptchaProtectedResource.getRemoteIP() method), so this
functionality should be in a separate method rather than in
captcha.CaptchaProtectedResource.render_POST(). See methods
getCaptchaImage(), extractClientSolution(), and checkSolution().
* ADD new captcha.ReCaptchaProtectedResource class which is a subclass
of captcha.CaptchaProtectedResource, and which implements
reCaptcha-specific functionality.
* CHANGE lib/bridgedb/templates/captcha.html to use HTTP parameters
'captcha_challenge_field' and 'captcha_response_field', rather than
'recaptcha_challenge_field' and 'recaptcha_response_field' respectively.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
* RENAME captcha.Raptcha → captcha.ReCaptcha
* RENAME captcha.RaptchaKeyError → captcha.ReCaptchaKeyError
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* CHANGE imports of ``recaptcha.client.captcha`` to
``from recaptcha.client import captcha as recaptcha``, to avoid name
conflict.
* Update Sphinx source configuration and build files to reflect module
name change.
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
It looks like this was accidently deleted in
967f1a6a4290154977ab7c0cc2cbe0560d7246ce when we changed how we
parsed the bridge descriptors.
This was originally added in
11b83c612090d673d4f23ccaf85be66ec5588e8a.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously we did not check that a bridge was already in a splitter,
this resulted in adding bridges with (almost) identical information
and #9264.
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If it's not new then we want to overwrite the old instance.
Unconditionally appending to to the splitter results in duplicate
bridges.
Closes #9264
|
| | | | | |
|
| | |/ /
|/| | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
These warnings are for:
:logging-not-lazy (W1201):
*Specify string format arguments as logging function parameters*
Used when a logging statement has a call form of "logging.<logging
method>(format_string % (format_args...))". Such calls should leave
string interpolation to the logging method itself and be written
"logging.<logging method>(format_string, format_args...)" so that the
program may avoid incurring the cost of the interpolation in those
cases in which no message will be logged. For more, see
http://www.python.org/dev/peps/pep-0282/. This message belongs to the
logging checker.
:anomalous-backslash-in-string (W1401):
*Anomalous backslash in string: '%s'. String constant might be
missing an r prefix.*
Used when a backslash is in a literal string but not as an
escape. This message belongs to the string_constant checker.
|
| |\ \ \
| |/ /
|/| | |
|
| |/ / |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
This was left over from commit 120c8e6d4b9d714e79722d83c19e110120977e79,
wherein the HTTPS and email distributors were split into different
files. The domains are taken from config.EMAIL_DOMAINS and are only
applicable to the email server.
|
| | | |
|
| | | |
|
