- ugettext functions will be removed in Django 4.0. Each use emits a warning
when running with Django 3.2. Since we have warnings enabled in developer mode,
we see quite a few messages because of this.
- ugettext is already a simple alias of gettext. So, no regressions are
expected.
Tests:
- Accessing an affected app in UI with Django 3.2 and Django 2.2 works fine.
- Using Django 3.2 there are no warnings related to removal of ugettext
functions.
- Ran regular unit tests.
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
- Convert line terminators in the form field so that it matches the
current status information resulting in proper detection of change in
value.
- Allow IPv6 addresses properly. Allow "[ipv6]:port" format.
- Make specifying port optional.
- Allow spaces at the beginning and ending of the line to compensate for
copy/paste errors.
- Allow empty lines between bridge specifications.
- Allow multiple spaces between the components.
- Raise error if upstream bridges are not provided when 'use upstream
bridges' option is enabled.
- Write tests for upstream bridges validator.
- Mention that this option is for preventing censorship.
- Simplify description of upstream bridges.
- Give hyperlink to bridges.torproject.org.
- Make it slightly more clear that users can copy paste information from
bridges page.
- Update list of supported transports.
- Allow users to run regular relays. In addition to that users will be
able to turn them into bridge relays. Like before, by default,
relaying is enabled and the relay type bridge relay.
- Show obfs3/4 transport ports as needing firewall port forwarding only
if bridge relay is enabled.
- Remove pluggable transports configuration from configuration when
bridge rely is disabled.
- Improve description message for relays and bridge relays.
- When Tor hidden service is enable along with regular web server, it is
possible to de-anonymize the server.
- When Tor hidden service is enabled along with Tor relay, the hidden
service can be de-anonymized by sending large traffic observing
traffic patterns published by Tor relay. See:
https://trac.torproject.org/projects/tor/ticket/8742
Warn users not to rely on Tor hidden service functionality for strong
anonymity. We can remove this warning when implement a mechanism to
disable most other services when Tor hidden service is enabled.
