Re: [tor-bugs] #18655 [Obfuscation/meek]: Make meek-server easy to use with Let's Encrypt

[Tor Bug Tracker & Wiki]

#18655: Make meek-server easy to use with Let's Encrypt
--+--
 Reporter:  dcf   |  Owner:  dcf
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * status:  new => needs_review


Comment:

 Here is a branch for review.
   https://gitweb.torproject.org/pluggable-
 transports/meek.git/log/?h=bug18655
   https://gitweb.torproject.org/pluggable-
 transports/meek.git/diff/?h=bug18655=1fcae3cad2=93dd339f7

 Let's Encrypt support is activated by the `--acme-hostnames` option, which
 specifies the set of hostnames for which the server will ask for
 certificates. For example,
 {{{
 ServerTransportPlugin meek exec /usr/local/bin/meek-server --acme-
 hostnames meek.bamsoftware.com --acme-email da...@bamsoftware.com
 }}}

 I have this running right now on https://meek.bamsoftware.com/ (which is
 the bridge
 [https://atlas.torproject.org/#details/C20658946DD706A7A2181159A1A04CD838570D04
 maenad]).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21836 [Obfuscation/meek]: meek-azure seems broken

[Tor Bug Tracker & Wiki]

#21836: meek-azure seems broken
--+-
 Reporter:  cypherpunks   |  Owner:
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by dcf):

 * component:  - Select a component => Obfuscation/meek


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18654 [Obfuscation/Snowflake]: Use TLS WebSockets (wss://) for proxy-to-server communication

[Tor Bug Tracker & Wiki]

#18654: Use TLS WebSockets (wss://) for proxy-to-server communication
---+--
 Reporter:  dcf|  Owner:
 Type:  enhancement| Status:  needs_review
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  snowflake, cupcake |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by dcf):

 I merged the letsencrypt branch in [https://gitweb.torproject.org
 /pluggable-
 transports/snowflake.git/commit/?id=61b604fc46df7e43d8a6069e7c6c00204d46665d
 61b604fc46df7e43d8a6069e7c6c00204d46665d].

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21748 [Obfuscation/Snowflake]: Snowflake breaks nightly builds as of March 15

[Tor Bug Tracker & Wiki]

#21748: Snowflake breaks nightly builds as of March 15
---+--
 Reporter:  gk |  Owner:  arlolra
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Major  | Resolution:
 Keywords:  tbb-7.0-must-nightly   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by arlolra):

 That seemed to work.  Let's see if you have some matching,

 {{{
 ...
 d34b4d98accb38c0f9e50178c6f1b473128e8cb51d10199b1afdc0a03041cd50  tor-
 browser-linux64-7.0a2_ar.mar
 4f922462983456bbeca4187d56c04a239e8a65a00e4d6762010bcfa26dc48af1  tor-
 browser-linux64-7.0a2_ar.tar.xz
 93ab3c2b9cf7ba23090a39a6679aeecd923c31714747c8e1ed4cebed101b70fb  tor-
 browser-linux64-7.0a2_de.mar
 752ef758e23970aeff7011269064e07e4921bb4d8e2a19f68ff3b36723abbdda  tor-
 browser-linux64-7.0a2_de.tar.xz
 0bf42106f2ec9d4c2cee689b5c8293449fbb2915c6e52c47e564f8cd7da26c3d  tor-
 browser-linux64-7.0a2_en-US.mar
 1d673966ab4561ac75fde485b0481c0cb128bbda882f284b638949df995412e0  tor-
 browser-linux64-7.0a2_en-US.tar.xz
 ...
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21748 [Obfuscation/Snowflake]: Snowflake breaks nightly builds as of March 15

[Tor Bug Tracker & Wiki]

#21748: Snowflake breaks nightly builds as of March 15
---+--
 Reporter:  gk |  Owner:  arlolra
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Major  | Resolution:
 Keywords:  tbb-7.0-must-nightly   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by gk):

 Alright, I guess we can parallelize that. I started one as well.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21583 [Core Tor/Stem]: Crypto nonce must be bytes instead of string for python3

[Tor Bug Tracker & Wiki]

#21583: Crypto nonce must be bytes instead of string for python3
---+
 Reporter:  feignix|  Owner:  atagar
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by feignix):

 No issues :)
 Glad that it has been fixed now

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21748 [Obfuscation/Snowflake]: Snowflake breaks nightly builds as of March 15

[Tor Bug Tracker & Wiki]

#21748: Snowflake breaks nightly builds as of March 15
---+--
 Reporter:  gk |  Owner:  arlolra
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Major  | Resolution:
 Keywords:  tbb-7.0-must-nightly   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by arlolra):

 I just force pushed `121de1ca` to the above branch and started a build to
 confirm.

 Sorry for having wasted your time.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21748 [Obfuscation/Snowflake]: Snowflake breaks nightly builds as of March 15

[Tor Bug Tracker & Wiki]

#21748: Snowflake breaks nightly builds as of March 15
---+--
 Reporter:  gk |  Owner:  arlolra
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Major  | Resolution:
 Keywords:  tbb-7.0-must-nightly   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by arlolra):

 {{{
 ../../webrtc/base/task_queue_libevent.cc:182:50: error: ignoring return
 value of 'ssize_t write(int, const void*, size_t)', declared with
 attribute warn_unused_result [-Werror=unused-result]
 3292 write(reply_pipe_, , sizeof(message));
 }}}

 Darn, sorry, I must have removed `treat_warnings_as_errors=false` :(

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21748 [Obfuscation/Snowflake]: Snowflake breaks nightly builds as of March 15

[Tor Bug Tracker & Wiki]

#21748: Snowflake breaks nightly builds as of March 15
---+--
 Reporter:  gk |  Owner:  arlolra
 Type:  defect | Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Major  | Resolution:
 Keywords:  tbb-7.0-must-nightly   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by gk):

 I am ov `fd2b35184753fdef8dcca11040b6416567c9896a` and made `make prep-
 alpha` and `mkbundle-linux.sh versions.alpha`. The build fails in step
 4/7. The log is attached.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21832 [Core Tor/Stem]: test_set_process_name failed.

[Tor Bug Tracker & Wiki]

#21832: test_set_process_name failed.
---+
 Reporter:  meto   |  Owner:  atagar
 Type:  defect | Status:  closed
 Priority:  Very Low   |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Trivial| Resolution:  fixed
 Keywords:  testing|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by atagar):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Great, thanks Denis! Fix merged.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21558 [Core Tor/Stem]: Add Ed25519 support

[Tor Bug Tracker & Wiki]

#21558: Add Ed25519 support
---+-
 Reporter:  patrickod  |  Owner:  atagar
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by patrickod):

 Fantastic! Excited to see it merged. Thanks for shepherding it into
 master!

 I'll have a look at the changes that you committed on top of my commits
 for some code style  feedback and the like to prevent the need for such
 refactors for future patches, but if you have any other feedback on the
 patch that'd be very welcome :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21583 [Core Tor/Stem]: Crypto nonce must be bytes instead of string for python3

[Tor Bug Tracker & Wiki]

#21583: Crypto nonce must be bytes instead of string for python3
---+
 Reporter:  feignix|  Owner:  atagar
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by atagar):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Hi feignix, very sorry about the long delay! Been busy focusing on a big
 branch the last several weeks. That said, I really hate dropping the ball
 on a pull request like this - sorry about that. :(

 This was fixed within the ed25519 certificate branch I merged yesterday.
 Thanks for the catch!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21834 [Applications/Tor Browser]: ExcludeExitNodes settings ignored

[Tor Bug Tracker & Wiki]

#21834: ExcludeExitNodes settings ignored
--+---
 Reporter:  JoeDiFostar   |  Owner:
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: 0.2.9.10
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by JoeDiFostar):

 * version:  Tor: unspecified => Tor: 0.2.9.10


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18100 [Core Tor/Tor]: src/or/connection_edge.c typo

[Tor Bug Tracker & Wiki]

#18100: src/or/connection_edge.c typo
-+-
 Reporter:  jirib|  Owner:
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.9
 Severity:  Normal   | Resolution:
 Keywords:  isaremoved, nickwants029, lorax, |  Actual Points:
  tor-03-unspecified-201612  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * status:  needs_revision => needs_review
 * milestone:  Tor: unspecified => Tor: 0.3.1.x-final


Comment:

 Thanks for analyzing and testing, d4fq0fQAgoJ.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21834 [Applications/Tor Browser]: ExcludeExitNodes settings ignored

[Tor Bug Tracker & Wiki]

#21834: ExcludeExitNodes settings ignored
--+---
 Reporter:  JoeDiFostar   |  Owner:
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by JoeDiFostar):

 > I assume you are editing the correct torrc file?

 Well it does produce a log file per your instructions so it should be.

 > Does ExcludeNodes work correctly?

 I don't use it.

 > Can you enable tor logging (send it to a file) and see if anything
 interesting is logged during > startup? Adding the following to your torrc
 should work: Log notice file E:\torlog.txt

 Here we go:

 Mar 30 11:03:15.000 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) opening
 new log file.
 Mar 30 11:03:15.072 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) running
 on Windows 7 with Libevent 2.0.22-stable, OpenSSL 1.0.2k and Zlib 1.2.8.
 Mar 30 11:03:15.087 [notice] Tor can't help you if you use it wrong! Learn
 how to be safe at https://www.torproject.org/download/download#warning
 Mar 30 11:03:15.103 [notice] Read configuration file "E:\Program Files
 (x86)\Tor Browser\Browser\TorBrowser\Data\Tor\torrc-defaults".
 Mar 30 11:03:15.103 [notice] Read configuration file "E:\Program Files
 (x86)\Tor Browser\Browser\TorBrowser\Data\Tor\torrc".
 Mar 30 11:03:15.150 [notice] Opening Socks listener on 127.0.0.1:9150
 Mar 30 11:03:15.150 [notice] Opening Control listener on 127.0.0.1:9151
 Mar 30 11:03:15.000 [notice] Parsing GEOIP IPv4 file E:\Program Files
 (x86)\Tor Browser\Browser\TorBrowser\Data\Tor\geoip.
 Mar 30 11:03:15.000 [notice] Parsing GEOIP IPv6 file E:\Program Files
 (x86)\Tor Browser\Browser\TorBrowser\Data\Tor\geoip6.
 Mar 30 11:03:16.000 [notice] Bootstrapped 0%: Starting
 Mar 30 11:03:18.000 [notice] Bootstrapped 80%: Connecting to the Tor
 network
 Mar 30 11:03:18.000 [notice] New control connection opened from 127.0.0.1.
 Mar 30 11:03:28.000 [notice] Bootstrapped 85%: Finishing handshake with
 first hop
 Mar 30 11:03:28.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
 Mar 30 11:03:29.000 [notice] Tor has successfully opened a circuit. Looks
 like client functionality is working.
 Mar 30 11:03:29.000 [notice] Bootstrapped 100%: Done
 Mar 30 11:03:29.000 [notice] Tor 0.2.9.10 (git-1f6c8eda0073f464) opening
 log file.
 Mar 30 11:03:30.000 [notice] New control connection opened from 127.0.0.1.
 Mar 30 11:03:38.000 [notice] New control connection opened from 127.0.0.1.
 Mar 30 11:03:39.000 [notice] New control connection opened from 127.0.0.1.
 Mar 30 11:12:40.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $9D6AE1BD4FDF39721CE908966E79E16F9BFCCF2F~Necto at
 93.115.95.201. Retrying on a new circuit.
 Mar 30 11:12:56.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $E43A346CB81DDF364B6FF68235AFADBA0E8692B8~HSLtor
 at 192.36.27.7. Retrying on a new circuit.
 Mar 30 11:13:12.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit
 $88487BDD980BF6E72092EE690E8C51C0AA4A538C~DigiGesTor2e1 at 176.10.104.243.
 Retrying on a new circuit.
 Mar 30 11:13:36.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $A44AE029015BA6FE0E9B90075C55617E0CD1E22B~kramse2
 at 185.129.62.63. Retrying on a new circuit.
 Mar 30 11:13:52.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $A041B285B228241C3185483EEF42F0BC96D40BFB~sowinetz
 at 91.223.82.156. Retrying on a new circuit.
 Mar 30 11:14:49.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit
 $97FCFABC0F8EB5FB9EAC3BC35F6C2DAE9E243ADC~calliprhugenasty09 at
 46.166.148.176. Retrying on a new circuit.
 Mar 30 11:15:06.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $5F482A48F88D2F9922CC2CCF98B9F326019862D0~Necto3
 at 93.115.95.204. Retrying on a new circuit.
 Mar 30 11:15:22.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit
 $5D5817EA15062AC623F9F60F388C649BEFE946EA~niftytexasmouse at
 151.80.238.152. Retrying on a new circuit.
 Mar 30 11:15:38.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit
 $0818DAE0E2DDF795AEDEAC60B15E71901084F281~edwardsnowden1 at 109.163.234.8.
 Retrying on a new circuit.
 Mar 30 11:15:55.000 [notice] We tried for 15 seconds to connect to
 '[scrubbed]' using exit $C656B41AEFB40A141967EBF49D6E69603C9B4A11~marcuse2
 at 178.20.55.18. Retrying on a new circuit.
 Mar 30 11:23:04.000 [notice] Owning controller connection has closed --
 exiting now.
 

Re: [tor-bugs] #21837 [Applications/Tor Browser]: Fix reproducibility issues in Firefox 52 accessibility code for Windows

[Tor Bug Tracker & Wiki]

#21837: Fix reproducibility issues in Firefox 52 accessibility code for Windows
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  defect  | Status:  new
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorBrowserTeam201703, tbb-7.0-must  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by cypherpunks):

 Something like
 {{{
   mkdir widl32 && cd widl32
   find -type f -print0 | xargs -0 touch --date="$REFERENCE_DATETIME"
   ../../mingw-w64-git/mingw-w64-tools/widl/configure
 --prefix=$INSTDIR/mingw-w64 --target=i686-w64-mingw32
   make $MAKEOPTS
   make install
 }}}
 ?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21834 [Applications/Tor Browser]: ExcludeExitNodes settings ignored

[Tor Bug Tracker & Wiki]

#21834: ExcludeExitNodes settings ignored
--+---
 Reporter:  JoeDiFostar   |  Owner:
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by mcs):

 * status:  reopened => needs_information
 * component:  - Select a component => Applications/Tor Browser


Comment:

 I am setting the component to Tor Browser for now, although if this is
 really happening it is probably a core tor issue.

 I cannot reproduce this problem using TB 6.5.1 on OSX (I don't have access
 to a Windows system at the moment).
 * I assume you are editing the correct torrc file?
 * Does ExcludeNodes work correctly?
 * Can you enable tor logging (send it to a file) and see if anything
 interesting is logged during startup? Adding the following to your torrc
 should work: `Log notice file E:\torlog.txt`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #20680 [Applications/Tor Browser]: Rebase Tor Browser patches to 52 ESR

[Tor Bug Tracker & Wiki]

#20680: Rebase Tor Browser patches to 52 ESR
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703, tbb-7.0-must-nightly |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by gk):

 Let's start the review:

 `aacb4ae907f93c8ad07b4ac5141a181348a2530c`:
 1) There is "Bug 18884: Disable Loop extension" mentioned in the commit
 message but there is no sign of that one in the `.mozconfig files anymore
 2) f161c394e049a440637f06ba87dd6be6f73479bb should get merged keeping the
 bug 17858... in the commit message
 3) I cleaned up my extension signing patch a bit and moved the ICU support
 for Windows out; it should be in the `.mozconfig-mingw` directly (I have
 no clue which I thought that would be a good idea to add that piece to the
 extension signing patch, it is not); see my `bug_20680_icu_fixup` branch
 (https://gitweb.torproject.org/user/gk/tor-
 browser.git/log/?h=bug_20680_icu_fixup) for splitting up that patch

 `7a2928fb53ee51714a825cdcadc749274495a9ab`:
 1) Merge 2345b6f3aab2f26a3ce04cf482651bec0879e86b + mention bug in commit
 message
 2) Merge a3e507a2300e7bd8a9db14d2d2901cbee1c356b9 + mention bug in commit
 message
 3) Merge f99ab094e5daa9df1e541644fbc8afde745e3443 + mention bug in commit
 message
 4) `pref("gfx.xrender.enabled",false);` is already included in ESR52, no
 need to set it again

 `e0213fac01fb1fc9f0949490d652c6ae979d6bd4`: not needed anymore

 `046b74f2dfd53b29b3e4515c2533244b6924f69e`: good
 `0bd71cd9f84185c71d91784467293585d46e6367`: good
 `0eb5695b4a48b94ac98c076d4640fcfa64fdc832`: good
 `44755f47a01eb3623227df9124a93226d034b75e`: good
 `746cfdbfabce6ed31bbd58d46deaefa0ccabd1fd`: looks okay; I was wondering
 what to do with the remaining `COMPONENTS_SHIM_ACCESSED_BY_CONTENT`
 places. I guess keeping them is fine as this is Telemetry related which we
 disable anyway?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21736 [Applications/Tor Messenger]: Do not keep account/timestamp when copy-pasting message containing an URL

[Tor Bug Tracker & Wiki]

#21736: Do not keep account/timestamp when copy-pasting message containing an 
URL
+-
 Reporter:  dgoulet |  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-

Comment (by sukhbir):

 Replying to [comment:4 huyvq]:
 > > I think the simplest solution is to make these elements unselectable.
 >
 > It's not. The simplest solution is to change some default message
 template prefs provided by IB:
 >
 > `messenger.conversations.selections.actionMessagesTemplate`
 > `messenger.conversations.selections.contentMessagesTemplate`
 > `messenger.conversations.selections.systemMessagesTemplate`.

 (FWIW, we do the same for TorBirdy:
 https://gitweb.torproject.org/torbirdy.git/tree/components/torbirdy.js#n306)

 So yeah, seems like a good idea.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18847 [Applications/Tor Browser]: Get our patches for cross-compiling ICU on Windows upstreamed

[Tor Bug Tracker & Wiki]

#18847: Get our patches for cross-compiling ICU on Windows upstreamed
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 We are done here actually. One patch got upstreamed, the other one
 obsolete due to upstream changes.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #21838 [Applications/Tor Browser]: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step

[Tor Bug Tracker & Wiki]

#21838: Gitian VM creation fails on Ubuntu 16.x machines in the unmount step
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-gitian
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 There have been reports that creating Gitian VMs on Ubuntu 16.x machines
 fails with error messages like:
 {{{
 2016-10-06 15:11:05,650 INFO: umount: /tmp/tmpxmUBiv/: target is busy
 2016-10-06 15:11:05,651 INFO: (In some cases useful info about
 processes that
 2016-10-06 15:11:05,651 INFO:  use the device is found by
 lsof(8) or fuser(1).)
 2016-10-06 15:11:05,651 ERROR   : Process (['umount', '/tmp/tmpxmUBiv/'])
 returned 32. stdout: , stderr: umount: /tmp/tmpxmUBiv/: target is busy
 (In some cases useful info about processes that
  use the device is found by lsof(8) or fuser(1).)

 Traceback (most recent call last):
   File "/usr/local/bin/vmbuilder", line 24, in 
 cli.main()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/contrib/cli.py",
 line 228, in main
 hypervisor.install_os()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/hypervisor.py",
 line 70, in install_os
 self.call_hooks('install_bootloader', self.chroot_dir, self.disks)
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/distro.py", line
 69, in call_hooks
 self.cleanup()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/distro.py", line
 44, in cleanup
 self._cleanup_cbs.pop(0)()
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/disk.py", line
 409, in umount
 run_cmd('umount', self.mntpath)
   File "/usr/local/lib/python2.7/dist-packages/VMBuilder/util.py", line
 120, in run_cmd
 raise VMBuilderException, "Process (%s) returned %d. stdout: %s,
 stderr: %s" % (args.__repr__(), status, mystdout.buf, mystderr.buf)
 VMBuilder.exception.VMBuilderException: Process (['umount',
 '/tmp/tmpxmUBiv/']) returned 32. stdout: , stderr: umount:
 /tmp/tmpxmUBiv/: target is busy
 (In some cases useful info about processes that
  use the device is found by lsof(8) or fuser(1).)

 qemu-img: target-wheezy-i386.qcow2: Could not open 'base-
 wheezy-i386.qcow2': No such file or directory
 i386 wheezy VM creation failed
 }}}

 And, indeed, for some reason there seem to be still resources used:
 {{{
 /dev/dm-12 on /tmp/tmp9k2g2E type ext3 (rw,relatime,data=ordered)
 /dev/sda1 on /tmp/tmp9k2g2E/tmp/vmbuilder-grub/tmpUE0GzK type ext4
 (rw,relatime,errors=remount-ro,data=ordered)
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #21837 [Applications/Tor Browser]: Fix reproducibility issues in Firefox 52 accessibility code for Windows

[Tor Bug Tracker & Wiki]

#21837: Fix reproducibility issues in Firefox 52 accessibility code for Windows
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  TorBrowserTeam201703,
 Severity:  Normal   |  tbb-7.0-must
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Somehow timestamps are sneaking in into the accessibility code when
 building Firefox 52 for Windows:

 `IA2Marshal.dll`
 {{{
 --- /dev/fd/63  2017-03-30 12:00:38.614322868 +0200
 +++ /dev/fd/62  2017-03-30 12:00:38.614322868 +0200
 @@ -11,7 +11,7 @@
  00a0: 0022 0100 0004  0014  0010   ."..
  00b0: 0030   1068 0010  0002   .0.h
  00c0: 0400  0100  0400     
 -00d0: 0090 0100 0004  3503 0200 0200   5...
 +00d0: 0090 0100 0004  e6e1 0100 0200   
  00e0:  2000 0010   1000 0010   .. .
  00f0:   1000  00b0  c100   
  0100: 00c0  d009  00f0  5086   P...
 @@ -3487,8 +3487,8 @@
  d9e0: 540b  1a00 ff7f 3801  0800 3900  T...8.9.
  d9f0:  4372 6561 7465 6420 6279 2057 4944  ..Created by WID
  da00: 4c20 7665 7273 696f 6e20 312e 3620 6174  L version 1.6 at
 -da10: 2057 6564 204d 6172 2032 3920 3134 3a31   Wed Mar 29 14:1
 -da20: 393a 3137 2032 3031 370a 0a57 1300 65c2  9:17 2017..W..e.
 +da10: 2057 6564 204d 6172 2032 3920 3131 3a35   Wed Mar 29 11:5
 +da20: 323a 3537 2032 3031 370a 0a57 1300 19a0  2:57 2017..W
  da30: db58 5757 1300 2b02 0007 5757 0300   .XWW..+...WW
  da40:  5757 0300 feff  5757 1800   ..WW..WW
  da50:     3000  4000   0...@...
 }}}
 `Accessible.tlb`
 {{{
 --- /dev/fd/63  2017-03-30 11:59:24.421999852 +0200
 +++ /dev/fd/62  2017-03-30 11:59:24.421999852 +0200
 @@ -136,8 +136,8 @@
  0870: 0800    0800 3900  4372  ..9...Cr
  0880: 6561 7465 6420 6279 2057 4944 4c20 7665  eated by WIDL ve
  0890: 7273 696f 6e20 312e 3620 6174 2057 6564  rsion 1.6 at Wed
 -08a0: 204d 6172 2032 3920 3134 3a31 393a 3136   Mar 29 14:19:16
 -08b0: 2032 3031 370a 0a57 1300 64c2 db58 5757   2017..W..d..XWW
 +08a0: 204d 6172 2032 3920 3131 3a35 323a 3537   Mar 29 11:52:57
 +08b0: 2032 3031 370a 0a57 1300 19a0 db58 5757   2017..W.XWW
  08c0: 1300 2b02 0007 5757 1800     ..+...WW
  08d0:   3000  4000     0...@...
  08e0: 4800  4800  0c00  9c00   H...H...
 }}}

 I guess as a fallback we could disable accessibility support, in case we
 find no other viable solution.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21240 [Applications/Tor Browser]: Create patches to fix mingw-w64 compilation of Firefox ESR 52

[Tor Bug Tracker & Wiki]

#21240: Create patches to fix mingw-w64 compilation of Firefox ESR 52
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703, GeorgKoppen201703R,  |
  tbb-7.0-must-nightly   |
Parent ID:  #21147   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by gk):

 * keywords:
 ff52-esr, tbb-7.0-must, TorBrowserTeam201703, GeorgKoppen201703,
 tbb-7.0-must-nightly
 =>
 ff52-esr, tbb-7.0-must, TorBrowserTeam201703, GeorgKoppen201703R,
 tbb-7.0-must-nightly
 * status:  new => needs_review


Comment:

 The tor-browser changes are in my `bug_21240` (the last 6 patches). The
 tor-browser-bundle changes are in my `bug_21240_v2`
 (https://gitweb.torproject.org/user/gk/tor-browser-
 bundle.git/commit/?h=bug_21240_v2=546273fb78b4dc7bf346505bf6262bc779dacb2c).
 The change in #18831 is needed as well.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18831 [Applications/Tor Browser]: We need Yasm >= 1.2.0 to build ESR 52

[Tor Bug Tracker & Wiki]

#18831: We need Yasm >= 1.2.0 to build ESR 52
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-gitian, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703, GeorgKoppen201703R,  |
  tbb-7.0-must-nightly   |
Parent ID:  #21240   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by gk):

 * parent:  #21147 => #21240


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21730 [Metrics/Metrics website]: Include metrics-lib's JavaDocs on the Metrics website

[Tor Bug Tracker & Wiki]

#21730: Include metrics-lib's JavaDocs on the Metrics website
-+
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by karsten):

 * status:  needs_review => closed
 * resolution:   => fixed


Comment:

 Great, that works!  Merged to master.  Thanks!  Closing.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21836 [- Select a component]: meek-azure seems broken

[Tor Bug Tracker & Wiki]

#21836: meek-azure seems broken
--+-
 Reporter:  cypherpunks   |  Owner:
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 Ignore this error. Error seems to have resolved itself.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21836 [- Select a component]: meek-azure seems broken

[Tor Bug Tracker & Wiki]

#21836: meek-azure seems broken
--+-
 Reporter:  cypherpunks   |  Owner:
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by cypherpunks):

 * status:  new => closed
 * resolution:   => invalid


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21736 [Applications/Tor Messenger]: Do not keep account/timestamp when copy-pasting message containing an URL

[Tor Bug Tracker & Wiki]

#21736: Do not keep account/timestamp when copy-pasting message containing an 
URL
+-
 Reporter:  dgoulet |  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-

Comment (by huyvq):

 > I think the simplest solution is to make these elements unselectable.

 It's not. The simplest solution is to change some default message template
 prefs provided by IB:

 `messenger.conversations.selections.actionMessagesTemplate`
 `messenger.conversations.selections.contentMessagesTemplate`
 `messenger.conversations.selections.systemMessagesTemplate`.

 Given that we can change these templates to make timestamp unable to be
 copied/pasted, should we change `"privacy.use_utc_timezone"` to `false`
 for better UX?
 Relate to #17619

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #21836 [- Select a component]: meek-azure seems broken

[Tor Bug Tracker & Wiki]

#21836: meek-azure seems broken
--+-
 Reporter:  cypherpunks   |  Owner:
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 I am in a country where meek is the only thing that works. Amazon is much
 less stable than Azure for me normally, so thank you very much for keeping
 Azure alive - it is the only way to stay vaguely safe anymore.

 I was using Azure with no issues on TorBrowser v6.5.1 an hour or so before
 this event. Then, some time after Mar 29 2017 2230UTC I tried to reconnect
 and the connection failed on the SSL handshake. I examined the traffic
 pattern using a traffic visualizer during the connection and all that
 occurred was a single pulse and then the connection died.

 Nothing had been changed on my system - no updates, or firewall changes or
 anything else significant. To be sure, I tested on another machine which
 had not been used that day, but that had worked last time I used it a day
 earlier. Like the other machine, it also had a similar rapid connection
 failure. I am almost certain this is not an issue linked to my local
 machines and either is linked to the underlying bridge, something
 Microsoft has changed or something local authorities have done to break
 the Azure server. However, if it is caused by local authorities, I am a
 little unsure why only Azure would be broken.

 Amazon, as I said, sort of works here, but can be very unstable and almost
 unusably slow as it is for me right now. If someone could just check to
 see if anything has happened to the Azure server, it would be greatly
 appreciated!





 LOG SAMPLE:

 Opening Socks listener on 127.0.0.1:9150
 [NOTICE] Bootstrapped 5%: Connecting to directory server
 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server
 [WARN] Problem bootstrapping. Stuck at 10%: Finishing handshake with
 directory server. (DONE; DONE; count 1; recommendation warn; host
 97700DFE9F483596DDA6264C4D7DF7641E1E39CE at 0.0.2.0:3)
 [WARN] 1 connections have failed:
 [WARN]  1 connections died in state handshaking (TLS) with SSL state
 SSLv2/v3 read server hello A in HANDSHAKE
 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 Closing old Socks listener on 127.0.0.1:9150
 [NOTICE] Delaying directory fetches: DisableNetwork is set.
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control
 network connections. Shutting down all existing connections.
 [NOTICE] Opening Socks listener on 127.0.0.1:9150
 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection
 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus
 [NOTICE] new bridge descriptor 'TorLandMeek' (fresh):
 $B9E7141C594AF25699E0079C1F0146F409495296~TorLandMeek at 0.0.2.0

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #21835 [Community/Tor Support]: Add information about hostingcompany that offers Tor Relays / Exit node hosting

[Tor Bug Tracker & Wiki]

#21835: Add information about hostingcompany that offers Tor Relays / Exit node
hosting
---+--
 Reporter:  sweg   |  Owner:  phoul
 Type:  enhancement| Status:  new
 Priority:  Low|  Milestone:
Component:  Community/Tor Support  |Version:  Tor: unspecified
 Severity:  Trivial|   Keywords:  Hosting
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 https://box.cock.ly

 When asked about their policies about hosting a Tor Exit node - the answer
 was:

 "Just keep the data under 1TB/month, otherwhise I dont give a fuck"

 Contact information can be found: https://vc.gg


 They actually run some internal services over tor:
 https://vc.gg/blog/announcing-the-iron-dong-hidden-service-backup-
 system.html

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #18831 [Applications/Tor Browser]: We need Yasm >= 1.2.0 to build ESR 52

[Tor Bug Tracker & Wiki]

#18831: We need Yasm >= 1.2.0 to build ESR 52
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-gitian, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703, GeorgKoppen201703R,  |
  tbb-7.0-must-nightly   |
Parent ID:  #21147   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by gk):

 Replying to [comment:8 cypherpunks]:
 > Ubuntu 12.04 LTS (Precise Pangolin) will be EOLed in less than a month
 https://lists.ubuntu.com/archives/ubuntu-security-
 announce/2017-March/003777.html.

 Yes, we have #18691 for that issue (although we might want to switch to
 Jessie while we are at it). For now it is faster just to add Yasm 1.2.0
 support, though, I think. We need to get nightly builds going ASAP. I am
 fine if we try switching away from 12.04 latter in the alpha cycle.

 > Also why not https://bugzilla.mozilla.org/show_bug.cgi?id=1113450?

 Because the idea was to keep the version diff as small as possible to
 avoid possible issues with a version that is "too new".

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #21833 [Applications/Tor Browser]: libvirt Changes in 16.10 bust check-prequisites.py

[Tor Bug Tracker & Wiki]

#21833: libvirt Changes in 16.10 bust check-prequisites.py
---+---
 Reporter:  tom|  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_review
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-gitian, TorBrowserTeam201703R  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by gk):

 * status:  new => needs_review
 * keywords:   => tbb-gitian, TorBrowserTeam201703R


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs