[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [bridgedb/develop] Change CHANGELOG entry links to use https://bugs.torproject.org.
commit 2457a24cdce957f99252cf2e1fda0f63d99c6b7e
Author: Isis Lovecruft <isis@xxxxxxxxxxxxxx>
Date: Thu Jul 24 03:16:03 2014 +0000
Change CHANGELOG entry links to use https://bugs.torproject.org.
---
CHANGELOG | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git a/CHANGELOG b/CHANGELOG
index 70b8446..7c9e76e 100644
--- a/CHANGELOG
+++ b/CHANGELOG
@@ -17,7 +17,7 @@ Changes in version 0.2.3 - 2014-07-XXX
Changes in version 0.2.2 - 2014-06-06
- * FIXES #9874 https://trac.torproject.org/projects/tor/ticket/9874
+ * FIXES #9874 https://bugs.torproject.org/9874
BridgeDB's email and HTTPS distributors were written in a manner
that makes them largely impossible to write unittests for. Since
the recent rewrite of BridgeDB's email distributor server backends
@@ -25,7 +25,7 @@ Changes in version 0.2.2 - 2014-06-06
has near 100% code coverage, see
https://coveralls.io/r/isislovecruft/bridgedb
- * FIXES #12086 https://trac.torproject.org/projects/tor/ticket/12086
+ * FIXES #12086 https://bugs.torproject.org/12086
BridgeDB was found to accept incoming emails sent to any email
address whose local part included the word bridges, e.g. emails
sent to 'givemebridges@xxxxxxxxxx' would be responded to as if
@@ -39,7 +39,7 @@ Changes in version 0.2.2 - 2014-06-06
domain name portion of BridgeDB's configured email address, or
is a subdomain of that domain.
- * FIXES #12089 https://trac.torproject.org/projects/tor/ticket/12089
+ * FIXES #12089 https://bugs.torproject.org/12089
There has been a bug for quite some time now where BridgeDB could
be used to email arbitrary email addresses (as long as these
addresses were ones which BridgeDB allows, i.e. Gmail or Yahoo
@@ -52,7 +52,7 @@ Changes in version 0.2.2 - 2014-06-06
addition to the previous checks that the email address' domain
is in the set of allowed domains.
- * FIXES #12090 https://trac.torproject.org/projects/tor/ticket/12090
+ * FIXES #12090 https://bugs.torproject.org/12090
BridgeDB has been replying with an empty email. I don't actually
know for sure if this one is fixed. Before deploying version
0.2.1, the continuous integration tests showed email responses
@@ -63,14 +63,14 @@ Changes in version 0.2.2 - 2014-06-06
outdated Python version in Debian Wheezy. I have not been able to
reproduce this bug on any other machine.
- * FIXES #12091 https://trac.torproject.org/projects/tor/ticket/12091
+ * FIXES #12091 https://bugs.torproject.org/12091
BridgeDB wasn't properly ignoring emails whose DKIM signature
verification header read "X-DKIM-Authentication-Results: dunno".
- Bridgedb now marks incoming emails which have a
"X-DKIM-Authentication-Results: dunno" header as invalid and
ignores them.
- * FIXES #12147 https://trac.torproject.org/projects/tor/ticket/12147
+ * FIXES #12147 https://bugs.torproject.org/12147
If a user refreshed https://bridges.torproject.org/bridges after
successfully solving a CAPTCHA, BridgeDB would reply with a new
set of bridges for each page refresh. This was due to the use of
@@ -88,7 +88,7 @@ Changes in version 0.2.2 - 2014-06-06
afterwards redirect back to the CAPTCHA page.
THANKS TO francisco on IRC and arma for reporting the bug.
- * FIXES #12212 https://trac.torproject.org/projects/tor/ticket/12122
+ * FIXES #12212 https://bugs.torproject.org/12122
TRANSLATOR comments are now properly extracted into the gettext PO
template file.
@@ -150,7 +150,7 @@ And include the following general changes:
Changes in version 0.2.1 - 2014-05-16
- * FIXES #5463 https://trac.torproject.org/projects/tor/ticket/5463
+ * FIXES #5463 https://bugs.torproject.org/5463
Emails sent from BridgeDB's email distributor should now be signed.
- BridgeDB's emails will be signed with its online GnuPG keypair. The
public key has the following fingerprint:
@@ -166,7 +166,7 @@ Changes in version 0.2.1 - 2014-05-16
All of BridgeDB's keys may be found on the public keyservers, as
well as at https://bridges.torproject.org/keys
- * FIXES #7547 https://trac.torproject.org/projects/tor/ticket/7547
+ * FIXES #7547 https://bugs.torproject.org/7547
BridgeDB's email distributor will now send you a message
explaining how to use it, including valid commands and the list of
Pluggable Transport TYPES currently supported. To receive help
@@ -178,16 +178,16 @@ Changes in version 0.2.1 - 2014-05-16
"get help"
in the body of your email.
- * FIXES #7550 https://trac.torproject.org/projects/tor/ticket/7550
+ * FIXES #7550 https://bugs.torproject.org/7550
BridgeDB's email responder is now interactive, as described in the
above entry for ticket #7547.
- * FIXES #8241 https://trac.torproject.org/projects/tor/ticket/8241
+ * FIXES #8241 https://bugs.torproject.org/8241
BridgeDB's HTTP distributor won't tell you how to get obfs3
bridges through email, although a blank email, or an email
containing "get help" will.
- * CLOSES #9678 https://trac.torproject.org/projects/tor/ticket/9678
+ * CLOSES #9678 https://bugs.torproject.org/9678
A "Select Language" button was requested for the HTTP distributor
on https://bridges.torproject.org. Instead, translated pages are
distributed automatically (via detecting the "Accept-Language"
@@ -198,31 +198,31 @@ Changes in version 0.2.1 - 2014-05-16
https://bridges.torproject.org/options?lang=ar
will provide the bridge options selection page in Arabic.
- * FIXES #11215 https://trac.torproject.org/projects/tor/ticket/11215
+ * FIXES #11215 https://bugs.torproject.org/11215
BridgeDB's usage of gimp-captcha, which creates a local cache of
CAPTCHA for use on the HTTP distributor, now supports timeouts. If
a CAPTCHA is not solved within 30 minutes of being served to a
client, the solution is invalid regardless of its correctness.
- * FIXES #11475 https://trac.torproject.org/projects/tor/ticket/11475
+ * FIXES #11475 https://bugs.torproject.org/11475
BridgeDB's email responder, up until this point, explained how to
use bridges with Vidalia. It now uses the same help text as found
at https://bridges.torproject.org/howto which explains how to
enter bridges into TorLauncher (used by Tor Browser and Tails).
- * FIXES #11522 https://trac.torproject.org/projects/tor/ticket/11522
+ * FIXES #11522 https://bugs.torproject.org/11522
There were several errors and bugs in BridgeDB's email
distributor. The entire system of server supporting BridgeDB's
email distribution system was rewritten.
- * FIXES #11664 https://trac.torproject.org/projects/tor/ticket/11664
+ * FIXES #11664 https://bugs.torproject.org/11664
Due to changes in the Python language builtin `buffer` in Python3,
which were backported to Python 2.7.6, but neither backported to
Python 2.6.x nor to Python <= 2.7.5, BridgeDB's use of
`io.StringIO` and `io.BytesIO` combined with buffers had to be
revised to support both the new and old Python `buffer` APIs.
- * FIXES #11753 https://trac.torproject.org/projects/tor/ticket/11753
+ * FIXES #11753 https://bugs.torproject.org/11753
BridgeDB's emails should now be translated.
- The translations system for BridgeDB, as well as the template
system for emails, was completely rewritten. By default, email
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits