commit ae6c59f6eea4b13ea6c008ac9df9e9e8f432fd4a
Author: Isis Lovecruft <[email protected]>
Date: Sun Mar 16 18:09:15 2014 +0000
Update CHANGELOG entry for bridgedb-0.1.5.
---
CHANGELOG | 25 ++++++++++++++++++++-----
1 file changed, 20 insertions(+), 5 deletions(-)
diff --git a/CHANGELOG b/CHANGELOG
index bfe527e..b8c9d71 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -1,12 +1,27 @@
Changes in version 0.1.5 - 2014-02-27
BridgeDB 0.1.5 includes fixes for the following bugs:
+ * FIXES #9264 Problem with transport lines in BridgeDB's bridge
+ pool assignment files
* FIXES #10809 reCAPTCHA on bridges.torproject.org are impossible
to solve for humans
- * FIXES #10834
-
-Including the following general changes:
- * CHANGES the reCaptcha remote IP address to be either a
- configurable value, or random (as it was previously).
+ * FIXES #10834 Configurable reCAPTCHA remoteip
+ * FIXES #11127 reCaptcha verification is hardcoded to use
+ plaintext HTTP
+
+And includes the following general changes:
+ * CHANGES the way the client's IP address is reported to the
+ reCaptcha API server. Previously, for each client request, a
+ completely random IP address was generated, and BridgeDB lied to
+ the reCaptcha server by sending this random IP and saying that it
+ was the client's IP. With these changes, BridgeDB can be
+ configured to report a static IP address (it's own IP) as the
+ client's IP, in the hopes that the IP whitelisting used by
+ reCaptcha makes the returned CAPTCHAs less impossible to solve.
+ * ADDS the ability to use a local cache of CAPTCHAs created by
+ scripting Gimp with Python. See:
+ https://github.com/isislovecruft/gimp-captcha
+ * USES TLS during CAPTCHA solution verification when using
+ reCaptcha.
Changes in version 0.1.4 - 2014-02-21
_______________________________________________
tor-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits
