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

2017-03-13 Thread 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by arthuredelstein):

 A further small correction:
 ​https://github.com/arthuredelstein/tor-browser/commits/20680+8

--
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] #13018 [Applications/Tor Browser]: Math routines are OS fingerprintable

2017-03-13 Thread Tor Bug Tracker & Wiki
#13018: Math routines are OS fingerprintable
-+-
 Reporter:  mikeperry|  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-fingerprinting-os-version,   |  Actual Points:
  ff31-esr   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by yawning):

 A few notes:

  * A quick check with the browser console gives me the impression that
 simple JS math expressions are evaluated with 64 bit intermediaries (as
 opposed to 80 bit).  I am uncertain about the JS JIT behavior.  `(1.0 +
 Number.EPSILON * 0.5) + Number.EPSILON * 0.5`)

  * Assuming calls are made to libm (or equivalent) blindly, the results on
 each system are library version and implementation dependent.  A
 particularly egregious example would be the output of `double sin(double
 x);` being flat out wrong for glibc < 2.19 for certain values.  MS's VC++
 runtime is less wrong for a different set of certain values, but is still
 wrong.  This probably applies to most transcendental functions.

  * Even if we fix the JS that calls into libm, higher level apis that just
 happen to do math are not guaranteed to give the correct results,
 depending on how the native code it's called into is written or built.  If
 we can assume that x87 is never used at all, then we'd still need to check
 for things like ` rsqrtss`.

--
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] #21723 [Applications/Tor Browser]: Fix inconsistent generation of MOZ_MACBUNDLE_ID

2017-03-13 Thread Tor Bug Tracker & Wiki
#21723: Fix inconsistent generation of MOZ_MACBUNDLE_ID
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201703R |  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Replying to [comment:2 mcs]:
 > Thanks for working on this. I have not tested this, but a quick glance
 at the uses of MOZ_MACBUNDLE_NAME within the browser code tells me we may
 not want to force it to lowercase because doing so will change our .app
 bundle from TorBrowser.app to torbrowser.app which is is less OSX-like and
 may also require changes to our packaging scripts, etc.

 You're right, I didn't notice that this was a different variable.
 I reverted this change.

 > MOZ_MACBUNDLE_ID should definitely be fixed though,

 I have revised this patch in my branch fix-macos-bundle-id-v2.
 It now removes all invalid characters, not just spaces.

 I tested it using:
 `echo "Tor Browser" | tr 'A-Z' 'a-z' | tr -dc 'a-z-'`
 on macOS and Ubuntu.

 The `[]` are unnecessary on modern tr, and lead to unexpected results when
 used with `tr -d`.

 `a-z` might not work when configure is run in a non-English locale, we can
 replace them with octal if this is a concern. (I expect this is not a
 practical issue, because otherwise the existing `tr [A-Z] [a-z]` would
 have failed.)

 > and I like org.torproject.torbrowser better than org.mozilla.torbrowser
 (but that will require a larger patch or scarier build config changes).

 This can be implemented by passing the following argument to Firefox's
 configure:
 `--with-distribution-id=org.torproject`

 Please see my branch `distribution-torproject` on
 https://github.com/teor2345/tor-browser-build.git for this change.

--
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] #17670 [Applications/Tor Browser]: Mac OSX mistakes Tor as Firefox default browser

2017-03-13 Thread Tor Bug Tracker & Wiki
#17670: Mac OSX mistakes Tor as Firefox default browser
--+--
 Reporter:  patrickbateman|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Replying to [comment:7 mcs]:
 > Replying to [comment:6 teor]:
 > > I don't know how to fix the Meek Tor Browser CFBundleSignature or
 CFBundleIdentifier. Is the Meek Tor Browser generated by the build
 scripts?
 >
 > The Meek Tor Browser is just another instance of Tor Browser in which
 the firefox binary is started with a --invisible flag and a different
 browser profile. Things used to be different though; a symlink'd copy was
 used in the past. It would be good to know if there is still a way for a
 "crippled" Tor Browser to be opened via Adium or another application.

 I opened #21732 to track this.

--
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] #21732 [Applications/Tor Browser]: Stop the Meek Tor Browser opening links or documents on macOS

2017-03-13 Thread Tor Bug Tracker & Wiki
#21732: Stop the Meek Tor Browser opening links or documents on macOS
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #17670
   Points:|   Reviewer:
  Sponsor:|
--+--
 Sometimes, the meek Tor Browser instance opens links or documents on
 macOS, when those links or documents should be opened in the regular Tor
 Browser.

 This has happened in the past on macOS, but we don't know whether it is
 still reproducible.

--
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] #21724 [Applications/Tor Browser]: Distinguish between Tor Browser and Firefox when macOS opens documents

2017-03-13 Thread Tor Bug Tracker & Wiki
#21724: Distinguish between Tor Browser and Firefox when macOS opens documents
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201703R |  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 Replying to [comment:3 mcs]:
 > While I do not object to this change, we should test and see if this
 change is needed. I have the impression (but no hard data) that the
 creator code is not used by OSX and that only the bundle ID is important.

 Apple has deprecated the creator code, but still uses it in their
 implementation for backwards-compatibility reasons.

 They are not mentioned at all in:
 
https://developer.apple.com/library/content/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html

 But here's how I can reproduce the Tor Browser / Firefox confusion on
 macOS 10.12.3:
 1. Install Firefox and Tor Browser
 2. `touch empty.html`
 3. In Finder, Get Info on empty.html
 4. Set "Open With" to Tor Browser
 5. Make sure both Firefox and Tor Browser are not running
 6. Open empty.html with the Finder
 (Either Firefox or Tor Browser will open depending on their order in the
 LaunchServices database, which depends on installation and maybe previous
 view/open order, and then if Tor Browser opens, Tor Launcher fails to
 handle the open request, so the default browser will open instead, see
 #20105)
 7. Make sure Firefox is running and Tor Browser is not running
 8. Open empty.html with the Finder
 (Firefox opens, even though we said to Open in Tor Browser)
 9. Make sure Tor Browser is running and Firefox is not running
 10. Open empty.html with the Finder
 (Tor Browser opens)
 11. Make sure Tor Browser and Firefox are both running
 12. Open empty.html with the Finder
 (Either Firefox or Tor Browser will open depending on their order in the
 LaunchServices database, which depends on installation and maybe previous
 view/open/launch order)

 What I expect to happen is that Tor Browser opens every time, and Firefox
 or the default browser do not open.

 > And I do not think Apple maintains a registry any more.

 Yes, this is true. But we should try not to conflict with Mozilla's
 potential future uses, if any.

--
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] #20105 [Applications/Tor Browser]: Selecting Open With TorBrowser on a Mac Opens the File in Default Browser Instead

2017-03-13 Thread Tor Bug Tracker & Wiki
#20105: Selecting Open With TorBrowser on a Mac Opens the File in Default 
Browser
Instead
--+--
 Reporter:  hdub  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * parent:   => #17670


Comment:

 Let's put these all under the top-level task

--
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] #21731 [Internal Services/Service - lists]: Archives not showing up on tor-community-team list

2017-03-13 Thread Tor Bug Tracker & Wiki
#21731: Archives not showing up on tor-community-team list
---+-
 Reporter:  alison |  Owner:  qbi
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by arma):

 * owner:   => qbi
 * component:  - Select a component => Internal Services/Service - lists


--
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] #21709 [Applications/Tor Browser]: Upgrade Go to 1.7.5

2017-03-13 Thread Tor Bug Tracker & Wiki
#21709: Upgrade Go to 1.7.5
--+
 Reporter:  dcf   |  Owner:  tbb-team
 Type:  task  | 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 dcf):

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


--
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] #21731 [- Select a component]: Archives not showing up on tor-community-team list

2017-03-13 Thread Tor Bug Tracker & Wiki
#21731: Archives not showing up on tor-community-team list
--+-
 Reporter:  alison|  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 The archives function is enabled, but the archives aren't there.

--
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] #19316 [Applications/Tor Browser]: Make sure our updates are dealing with SSE requirement properly

2017-03-13 Thread Tor Bug Tracker & Wiki
#19316: Make sure our updates are dealing with SSE requirement properly
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 Replying to [comment:10 mcs]:
 > Replying to [comment:7 boklm]:
 > > Replying to [comment:1 mcs]:
 > > > Similar to the minSupportedOSVersion update manifest attribute that
 we added for the Mac OS 10.6 issue (see
 https://trac.torproject.org/projects/tor/ticket/13047#comment:3), we
 should add support for a new attribute such as: `minInstructionSet="SSE2"`
 > >
 > > I attached a first version of a patch to do that, but I did not test
 it yet, so it may not work.
 >
 > It seems like we just need one attribute in the update manifest, e.g.,
 minSupportedInstructionSet.
 >
 > Also, I think your patch is missing a !. Maybe just do something like:
 > {{{
 > if (!this.unsupported &&
 update.hasAttribute("minSupportedInstructionSet")) {
 >   let minInstructionSet =
 update.getAttribute("minSupportedInstructionSet");
 >   if (['MMX', 'SSE', 'SSE2', 'SSE3',
 >'SSE4A', 'SSE4_1', 'SSE4_2'].indexOf(minInstructionSet) >= 0) {
 >   try {
 > this.unsupported = !Services.sysinfo.getProperty("has" +
 minInstructionSet);
 >   } catch (e) {}
 > }
 > }}}
 >
 > (untested).

 This looks better, thanks.


 > > I think there will still be an issue with people upgrading to the new
 ESR52 version from Tor Browser <= 6.5.1 (skipping the version that added
 support for the minInstructionSet attribute), as their browser will not
 know this attribute. If we want to avoid this, we will need to change the
 `update_2` from the updates URL to `update_3` (similar to what we did in
 #13047).
 >
 > Do we really need to change to update3? We are not changing the request
 URL. We should add support for the new instruction set attribute to TB
 6.5.2 and then advertise to older Windows browsers an update to 6.5.2.
 Then, after that update is done, the 6.5.2 browser will recognize the new
 attribute and make the appropriate instruction set check. Mozilla does
 this kind of thing once in a while; they call it a step-wise update or
 flag day or something ;)

 I think we have no easy way to continue advertising 6.5.2 to older Windows
 browsers after 7.0 is released, with what we use to generate the update
 responses files. We can add support for that, but it will probably require
 keeping a copy of the 6.5.2 mar files when generating update response
 files for many of the future releases. I think an easier way to do that is
 changing the update url to `update_3` in 6.5.2, and not advertising 7.0 in
 `update_2`. We can also add `update_2` -> `update_3` redirects for the
 Linux and OSX URLs so that Linux and OSX browsers are updated to the
 latest version directly.

--
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] #21267 [Applications/Tor Browser]: e10s compatibility for Torbutton's content sizer

2017-03-13 Thread Tor Bug Tracker & Wiki
#21267: e10s compatibility for Torbutton's content sizer
-+-
 Reporter:  mcs  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-torbutton, ff52-esr, |  Actual Points:
  tbb-7.0-must, TorBrowserTeam201703R|
Parent ID:  #21201   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by arthuredelstein):

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


--
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] #21267 [Applications/Tor Browser]: e10s compatibility for Torbutton's content sizer

2017-03-13 Thread Tor Bug Tracker & Wiki
#21267: e10s compatibility for Torbutton's content sizer
-+-
 Reporter:  mcs  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-torbutton, ff52-esr, |  Actual Points:
  tbb-7.0-must, TorBrowserTeam201703R|
Parent ID:  #21201   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by arthuredelstein):

 Replying to [comment:12 mcs]:
 > r=brade, r=mcs
 > The backout patch looks good to us.

 Thanks for the review. I added the patch to my #21201 patch.

--
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] #19316 [Applications/Tor Browser]: Make sure our updates are dealing with SSE requirement properly

2017-03-13 Thread Tor Bug Tracker & Wiki
#19316: Make sure our updates are dealing with SSE requirement properly
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by mcs):

 Replying to [comment:7 boklm]:
 > Replying to [comment:1 mcs]:
 > > Similar to the minSupportedOSVersion update manifest attribute that we
 added for the Mac OS 10.6 issue (see
 https://trac.torproject.org/projects/tor/ticket/13047#comment:3), we
 should add support for a new attribute such as: `minInstructionSet="SSE2"`
 >
 > I attached a first version of a patch to do that, but I did not test it
 yet, so it may not work.

 It seems like we just need one attribute in the update manifest, e.g.,
 minSupportedInstructionSet.

 Also, I think your patch is missing a !. Maybe just do something like:
 {{{
 if (!this.unsupported &&
 update.hasAttribute("minSupportedInstructionSet")) {
   let minInstructionSet =
 update.getAttribute("minSupportedInstructionSet");
   if (['MMX', 'SSE', 'SSE2', 'SSE3',
'SSE4A', 'SSE4_1', 'SSE4_2'].indexOf(minInstructionSet) >= 0) {
   try {
 this.unsupported = !Services.sysinfo.getProperty("has" +
 minInstructionSet);
   } catch (e) {}
 }
 }}}

 (untested).

 > I think there will still be an issue with people upgrading to the new
 ESR52 version from Tor Browser <= 6.5.1 (skipping the version that added
 support for the minInstructionSet attribute), as their browser will not
 know this attribute. If we want to avoid this, we will need to change the
 `update_2` from the updates URL to `update_3` (similar to what we did in
 #13047).

 Do we really need to change to update3? We are not changing the request
 URL. We should add support for the new instruction set attribute to TB
 6.5.2 and then advertise to older Windows browsers an update to 6.5.2.
 Then, after that update is done, the 6.5.2 browser will recognize the new
 attribute and make the appropriate instruction set check. Mozilla does
 this kind of thing once in a while; they call it a step-wise update or
 flag day or something ;)

--
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] #17670 [Applications/Tor Browser]: Mac OSX mistakes Tor as Firefox default browser

2017-03-13 Thread Tor Bug Tracker & Wiki
#17670: Mac OSX mistakes Tor as Firefox default browser
--+--
 Reporter:  patrickbateman|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 Replying to [comment:6 teor]:
 > I don't know how to fix the Meek Tor Browser CFBundleSignature or
 CFBundleIdentifier. Is the Meek Tor Browser generated by the build
 scripts?

 The Meek Tor Browser is just another instance of Tor Browser in which the
 firefox binary is started with a --invisible flag and a different browser
 profile. Things used to be different though; a symlink'd copy was used in
 the past. It would be good to know if there is still a way for a
 "crippled" Tor Browser to be opened via Adium or another application.

--
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] #21723 [Applications/Tor Browser]: Fix inconsistent generation of MOZ_MACBUNDLE_ID

2017-03-13 Thread Tor Bug Tracker & Wiki
#21723: Fix inconsistent generation of MOZ_MACBUNDLE_ID
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201703R |  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 Thanks for working on this. I have not tested this, but a quick glance at
 the uses of MOZ_MACBUNDLE_NAME within the browser code tells me we may not
 want to force it to lowercase because doing so will change our .app bundle
 from TorBrowser.app to torbrowser.app which is is less OSX-like and may
 also require changes to our packaging scripts, etc.

 MOZ_MACBUNDLE_ID should definitely be fixed though, and I like
 org.torproject.torbrowser better than org.mozilla.torbrowser (but that
 will require a larger patch or scarier build config 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

Re: [tor-bugs] #21724 [Applications/Tor Browser]: Distinguish between Tor Browser and Firefox when macOS opens documents

2017-03-13 Thread Tor Bug Tracker & Wiki
#21724: Distinguish between Tor Browser and Firefox when macOS opens documents
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201703R |  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 While I do not object to this change, we should test and see if this
 change is needed. I have the impression (but no hard data) that the
 creator code is not used by OSX and that only the bundle ID is important.
 And I do not think Apple maintains a registry any more.

--
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] #21729 [Core Tor/Tor]: make dedicated log file perms less verbose

2017-03-13 Thread Tor Bug Tracker & Wiki
#21729: make dedicated log file perms less verbose
--+
 Reporter:  toralf|  Owner:
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.0.4-rc
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by toralf):

 The content might be something like:

 Log files should be written only by the owner, be read-only for the group
 and forbidden to read for all others.

--
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] #21729 [Core Tor/Tor]: make dedicated log file perms less verbose

2017-03-13 Thread Tor Bug Tracker & Wiki
#21729: make dedicated log file perms less verbose
--+
 Reporter:  toralf|  Owner:
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.0.4-rc
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 Sure, may as well tighten this up.  Got time to write a changes file?

--
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] #21682 [Core Tor/Tor]: memory leak at shutdown

2017-03-13 Thread Tor Bug Tracker & Wiki
#21682: memory leak at shutdown
+
 Reporter:  cypherpunks |  Owner:  nickm
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:  Tor: 0.3.0.x-final
Component:  Core Tor/Tor|Version:  Tor: unspecified
 Severity:  Minor   | Resolution:  fixed
 Keywords:  regression memory-leak  |  Actual Points:  0
Parent ID:  | Points:  0
 Reviewer:  |Sponsor:
+
Changes (by nickm):

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


Comment:

 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] #21334 [Core Tor/Tor]: prop224: Update prop224 HS desriptor generation code to produce the latest descriptor format

2017-03-13 Thread Tor Bug Tracker & Wiki
#21334: prop224: Update prop224 HS desriptor generation code to produce the 
latest
descriptor format
--+
 Reporter:  asn   |  Owner:  asn
 Type:  enhancement   | Status:  closed
 Priority:  Very High |  Milestone:  Tor:
  |  0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  tor-hs, prop224, review-group-16  |  Actual Points:
Parent ID:| Points:  3
 Reviewer:  nickm |Sponsor:  SponsorR-
  |  must
--+
Changes (by nickm):

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


Comment:

 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] #21693 [Core Tor/Tor]: prop224 HS descriptors do wasteful double-base64 encoding

2017-03-13 Thread Tor Bug Tracker & Wiki
#21693: prop224 HS descriptors do wasteful double-base64 encoding
+
 Reporter:  asn |  Owner:
 Type:  task| Status:  new
 Priority:  Medium  |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs prop224  |  Actual Points:
Parent ID:  | Points:  4
 Reviewer:  |Sponsor:  SponsorR-can
+
Changes (by nickm):

 * parent:  #21334 =>


--
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] #21651 [Core Tor/Tor]: prop140/compression: Refactor directory cache spooling code

2017-03-13 Thread Tor Bug Tracker & Wiki
#21651: prop140/compression: Refactor directory cache spooling code
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  0.3.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201703, prop140  |  Actual Points:  1
Parent ID:  | Points:  3
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by nickm):

 * status:  accepted => needs_review
 * actualpoints:   => 1


Comment:

 See branch `spooling` in my public repository.  The code here is already
 covered by the unit tests combined with the chutney integration tests, but
 please let me know if you think it could use more testing.

--
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] #21730 [Metrics/Metrics website]: Include metrics-lib's JavaDocs on the Metrics website

2017-03-13 Thread Tor Bug Tracker & Wiki
#21730: Include metrics-lib's JavaDocs on the Metrics website
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 We should include metrics-lib's JavaDocs on the Metrics website, possibly
 at `https://metrics.torproject.org/metrics-lib/*`.  We'll likely want to
 automate this using Ant and possibly a Git submodule.  For that we could
 either build metrics-lib as part of metrics-web, or we could just generate
 the docs for metrics-lib's sources in metrics-web's build file.  Once we
 have this Git-and-Ant magic in place we should update
 [https://gitweb.torproject.org/metrics-web.git/tree/website/web/WEB-INF
 /metrics-lib.jsp metrics-lib.jsp] and link to the JavaDocs, once in the
 jumbotron and once more in the "Next steps" section.

--
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] #21729 [Core Tor/Tor]: make dedicated log file perms less verbose

2017-03-13 Thread Tor Bug Tracker & Wiki
#21729: make dedicated log file perms less verbose
--+-
 Reporter:  toralf|  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.0.4-rc
 Severity:  Minor |   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 I think, that the log file permissions are too weak in moment, this helps:

 {{{
 tfoerste@t44 ~/devel/tor $ cat /tmp/log640.patch
 diff --git a/src/common/log.c b/src/common/log.c
 index 5f7151b..f679336 100644
 --- a/src/common/log.c
 +++ b/src/common/log.c
 @@ -1086,7 +1086,7 @@ add_file_log(const log_severity_list_t *severity,
 const char *filename,
int open_flags = O_WRONLY|O_CREAT;
open_flags |= truncate_log ? O_TRUNC : O_APPEND;

 -  fd = tor_open_cloexec(filename, open_flags, 0644);
 +  fd = tor_open_cloexec(filename, open_flags, 0640);
if (fd<0)
  return -1;
if (tor_fd_seekend(fd)<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

Re: [tor-bugs] #21379 [Metrics/metrics-lib]: Metrics-lib web-site

2017-03-13 Thread Tor Bug Tracker & Wiki
#21379: Metrics-lib web-site
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 There, we now have a [https://metrics.torproject.org/metrics-lib.html
 metrics-lib page] on Metrics.  That concludes this ticket.  It doesn't
 mean we can't improve it, though, but that can happen in new tickets.
 Thanks, everyone!  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] #17380 [Applications/Tor Browser]: Splitting the build of each components

2017-03-13 Thread Tor Bug Tracker & Wiki
#17380: Splitting the build of each components
--+--
 Reporter:  boklm |  Owner:  boklm
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201703  |  Actual Points:
Parent ID:  #17379| Points:
 Reviewer:|Sponsor:  Sponsor4
--+--

Comment (by boklm):

 snowflake has been added, but only for linux-x86_64 for now. On linux-i686
 I still have an error trying to build it:
 {{{
 # _/var/tmp/build/snowflake-6cecd31fd896/client
 ./rendezvous.go:77: undefined: webrtc.SessionDescription
 ./rendezvous.go:78: undefined: webrtc.SessionDescription
 ./rendezvous.go:118: undefined: webrtc.Configuration
 }}}
 I think this issue might be related to building it in an x86_64 container.

--
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] #21267 [Applications/Tor Browser]: e10s compatibility for Torbutton's content sizer

2017-03-13 Thread Tor Bug Tracker & Wiki
#21267: e10s compatibility for Torbutton's content sizer
-+-
 Reporter:  mcs  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-torbutton, ff52-esr, |  Actual Points:
  tbb-7.0-must, TorBrowserTeam201703R|
Parent ID:  #21201   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by mcs):

 r=brade, r=mcs
 The backout patch looks good to us.

--
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

2017-03-13 Thread 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by arthuredelstein):

 Replying to [comment:26 gk]:
 > ESR 52 is out. Could you rebase the patches once more to the up-to-date
 Mozilla branch? FWIW: we have an official branch now in gecko-dev for
 that. There are a bunch of rebase conflicts and I'd like to review the
 final patches.

 Yes -- for the record, here's the branch rebased to gecko-dev/esr52:
 https://github.com/arthuredelstein/tor-browser/commits/20680+6

 And here is the same branch with fixups squashed:
 https://github.com/arthuredelstein/tor-browser/commits/20680+7

--
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] [Tor Bug Tracker & Wiki] Batch modify: #21673, #21651, #21646, #21644, ...

2017-03-13 Thread Tor Bug Tracker & Wiki
Batch modification to #21673, #21651, #21646, #21644, #21643, #13339, #21645, 
#21677, #21650, #21649, #21648, #21647 by dgoulet:
keywords to prop140

--
Tickets 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] [Tor Bug Tracker & Wiki] Batch modify: #21668, #21667, #21666, #21665, ...

2017-03-13 Thread Tor Bug Tracker & Wiki
Batch modification to #21668, #21667, #21666, #21665, #21664, #21663, #21662 by 
ahf:
keywords to prop278

Comment:
Add prop278 keyword.

--
Tickets 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] [Tor Bug Tracker & Wiki] Batch modify: #20699, #20594, #18098

2017-03-13 Thread Tor Bug Tracker & Wiki
Batch modification to #20699, #20594, #18098 by dgoulet:
milestone to Tor: 0.3.2.x-final

Comment:
We think it's not realistic for 031.

--
Tickets 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] #16861 [Core Tor/Tor]: Pad Tor connections to collapse netflow records

2017-03-13 Thread Tor Bug Tracker & Wiki
#16861: Pad Tor connections to collapse netflow records
-+-
 Reporter:  mikeperry|  Owner:
 |  mikeperry
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  028-triage, 028-triaged, |  Actual Points:
  pre028-patch, 201511-deferred, |
  201512-deferred, tor-guard, TorCoreTeam-   |
  postponed-201604, nickm-deferred-20160905, |
  review-group-9, nickm-deferred-20161005,   |
  review-group-16|
Parent ID:   | Points:  2
 Reviewer:  nickm|Sponsor:
-+-

Comment (by mikeperry):

 FYI this branch and the subtickets were rebased on to master a week or so
 ago in mikeperry/netflow_padding-v6-rebased
 (0b572b90f77bb466d8e1946aa6b0ff2fd131ca4d)

--
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] #19048 [Applications/Tor Browser]: Review Firefox Developer Docs and Undocumented bugs since FF45esr

2017-03-13 Thread Tor Bug Tracker & Wiki
#19048: Review Firefox Developer Docs and Undocumented bugs since FF45esr
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703, GeorgKoppen201703|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by gk):

 Replying to [comment:12 mcs]:
 > And here are our notes for Firefox 49:
 >
 > a) Graphite font rendering has been re-enabled. We need to decide if we
 want to disable it again or not.

 I opened #21726.

 > b) Mozilla switched to compiling with Intel SSE2. We could do the same,
 although it would mean that Tor Browser would not run on some really old
 CPUs. Mozilla modified their Windows installer to notify and refuse to
 install if the CPU does not support SSE2.
 >  https://bugzilla.mozilla.org/show_bug.cgi?id=1271759

 The updater part is #19316 and the installer #21704.

 > c) Kathy and I cannot think of any fingerprinting or linkability risks
 associated with the Web Speech API, but it is a big new thing:
 >  https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_API
 >  https://bugzilla.mozilla.org/show_bug.cgi?id=1268633

 Yeah, I think this is fine. Both synthesis and recognition seem to be off
 anyway. pref("media.webspeech.synth.enabled", false);
 pref("media.webspeech.recognition.enable", false);

 > d) We should verify that the "Network ID" is not even computed when
 Telemetry is disabled.  At least I would feel better if it was not.
 >  https://bugzilla.mozilla.org/show_bug.cgi?id=1240932

 #21727. Might have sandboxing implications as well as it needs
 /proc/net/arp access on Linux e.g.

 > e) The Bookmarks Toolbar is automatically shown when the user adds a
 bookmark to it. This will change the window size, but maybe this is used
 rarely enough that we do not care?
 >  https://bugzilla.mozilla.org/show_bug.cgi?id=1219788

 Hm. I think that falls under #16456

 > f) The window.isSecureContext API is interesting but may not add any
 fingerprinting or linkability risks. We should think about whether
 features that are being made "HTTPS only" should also be available on
 .onion sites.
 >  https://developer.mozilla.org/en-US/docs/Web/API/Window/isSecureContext

 Yes, this is a nice thing to look at, I opened #21728.

 > g) As part of our release procedures, do we double-check the HPKP
 expiration? Mozilla seems to have bugs for each release, e.g.,
 >  https://bugzilla.mozilla.org/show_bug.cgi?id=1307530

 No, we don't right now. Mozilla has HPKP enabled for addons.mozilla.org
 and other measures implemented
 (https://bugzilla.mozilla.org/show_bug.cgi?id=1303127#c13). I think that's
 okay until we solve this properly.

 Other things I have:

 h) Flyweb landed which seems crazy (https://wiki.mozilla.org/FlyWeb and
 https://hacks.mozilla.org/2016/09/flyweb-pure-web-cross-device-
 interaction) but it is disabled in ESR 52 (`dom.flyweb.enabled` is
 `false`).

 i) Canvas CSS/SVG filters are enabled by default
 (https://bugzilla.mozilla.org/show_bug.cgi?id=1173545). We have #16341 for
 that.

--
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] #21728 [Applications/Tor Browser]: Features that are made "HTTPS-only" should be available on .onion sites as well

2017-03-13 Thread Tor Bug Tracker & Wiki
#21728: Features that are made "HTTPS-only" should be available on .onion sites 
as
well
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Firefox 49 is adding an `isSecureContext` attribute
 (https://developer.mozilla.org/en-US/docs/Web/API/Window/isSecureContext)
 we should make sure it returns `true` on .onion sites 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] #21667 [Core Tor/Tor]: Prop278: Handle new headers in directory.c

2017-03-13 Thread Tor Bug Tracker & Wiki
#21667: Prop278: Handle new headers in directory.c
---+
 Reporter:  ahf|  Owner:  ahf
 Type:  task   | Status:  accepted
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+
Changes (by ahf):

 * owner:   => ahf
 * status:  new => accepted


--
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] #21725 [Internal Services/Schleuder]: Add the following to tor-security@ Schleuer list

2017-03-13 Thread Tor Bug Tracker & Wiki
#21725: Add the following to tor-security@ Schleuer list
-+-
 Reporter:  dgoulet  |  Owner:  hiro
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Schleuder  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by dgoulet):

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


--
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] #21727 [Applications/Tor Browser]: Investigate network ID feature in ESR 52

2017-03-13 Thread Tor Bug Tracker & Wiki
#21727: Investigate network ID feature in ESR 52
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ff52-esr
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Mozilla landed a network identification ID feature in Firefox 49
 (https://bugzilla.mozilla.org/show_bug.cgi?id=1240932). We probably don't
 want that. At least we should investigate it closer and maybe don't let an
 ID get computed at least when Telemetry is disabled.

 Note: this has probably consequences for (Linux) sandboxing at least as it
 needs access to /proc/net/arp.

--
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] #21726 [Applications/Tor Browser]: Get graphite back into the security slider

2017-03-13 Thread Tor Bug Tracker & Wiki
#21726: Get graphite back into the security slider
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-torbutton, tbb-
 Severity:  Normal   |  security-slider, ff52-esr
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 We removed disabled graphite support in Tor Browser following Mozilla due
 to security concerns. We should let it be governed again by our security
 slider (Mozilla's bug is
 https://bugzilla.mozilla.org/show_bug.cgi?id=1271262).

--
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] #21272 [Metrics]: Onionperf deployment

2017-03-13 Thread Tor Bug Tracker & Wiki
#21272: Onionperf deployment
-+--
 Reporter:  hiro |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by hiro):

 Update:
 I have changed the onionperf source name on papillare as onionperf. I was
 chatting w the tpa team and they would prefer not having to change the dns
 to op-de. If we can stick with onionperf as service name and subdomain we
 are good, otherwise I'll bump them again.
 Hopefully the ports are correct now.
 Will finish deleting old files when we will check the new results
 tomorrow, to compare.

--
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] #20105 [Applications/Tor Browser]: Selecting Open With TorBrowser on a Mac Opens the File in Default Browser Instead

2017-03-13 Thread Tor Bug Tracker & Wiki
#20105: Selecting Open With TorBrowser on a Mac Opens the File in Default 
Browser
Instead
--+--
 Reporter:  hdub  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by brade):

 * cc: brade (added)
 * owner:  brade => tbb-team
 * component:  Applications/Tor Launcher => Applications/Tor Browser


--
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] #21725 [Internal Services/Schleuder]: Add the following to tor-security@ Schleuer list

2017-03-13 Thread Tor Bug Tracker & Wiki
#21725: Add the following to tor-security@ Schleuer list
-+--
 Reporter:  dgoulet  |  Owner:  hiro
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Schleuder  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Key fingerprint = F65C E37F 04BA 5B36 0AE6  EE17 C218 5258 19F7 8451
 uid   [  full  ] Roger Dingledine 

 Key fingerprint = 2133 BC60 0AB1 33E1 D826  D173 FE43 009C 4607 B1FB
 uid   [  undef ] Nick Mathewson 

 Key fingerprint = 35CD 74C2 4A9B 15A1 9E1A  81A1 9437 3AA9 4B7C 3223
 uid   [  undef ] Georg Koppen 
 -BEGIN PGP SIGNATURE-

 iQF8BAEBCABmBQJYxq9UXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
 ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCNzQ0MTdFRERGMjJBQzlGOUU5MEY0OTE0
 MkU4NkEyQTExRjQ4RDM2AAoJEELoaioR9I02AQ4H/24m3Kxf0m2c1gFgqk0TnLoL
 vJm19cpfLTTThXseVEUBLl4pgYp3iePMTErB91AXnMQHg5782eK5hdG55+l4iTHq
 dx8GWKlu8dcNT47Q0Fbi2Qi0RckYS1memoMdB5huQtwVQCRnF40kOquT/H9wgE3U
 lkdmGrF3Ij36pIysp/vuSgDZZXod0oZFERzqDbmw9gKMVbGRijUjJq5YGVFfo44a
 K98SYutnIqHasVG8n7D2Mn8WE2Lb74X+1m7pLBN/T1r20XDrTMeXnRJYHWJWxtGf
 4FrUehc8Y4Gn3ckFtw8GmIuPyIOHu0TgmKTiQ5qlqMIXVjChicJqltvF3ysIKQs=
 =tvc/
 -END PGP SIGNATURE-
 }}}

--
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] #20321 [Applications/Tor Launcher]: Quit Tor Browser Menu Option Does Not Work from Launcher on Mac OS

2017-03-13 Thread Tor Bug Tracker & Wiki
#20321: Quit Tor Browser Menu Option Does Not Work from Launcher on Mac OS
---+---
 Reporter:  cypherpunks|  Owner:  brade
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Minor  | Resolution:
 Keywords:  tbb-usability  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by brade):

 * cc: mcs (added)


--
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] #21546 [Applications/Tor Browser]: Adapt Tor Launcher to TBB/FF52ESR

2017-03-13 Thread Tor Bug Tracker & Wiki
#21546: Adapt Tor Launcher to TBB/FF52ESR
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703R  |
Parent ID:  #20680   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by brade):

 r=brade, r=mcs

--
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] #21682 [Core Tor/Tor]: memory leak at shutdown

2017-03-13 Thread Tor Bug Tracker & Wiki
#21682: memory leak at shutdown
+
 Reporter:  cypherpunks |  Owner:  nickm
 Type:  defect  | Status:  merge_ready
 Priority:  Medium  |  Milestone:  Tor: 0.3.0.x-final
Component:  Core Tor/Tor|Version:  Tor: unspecified
 Severity:  Minor   | Resolution:
 Keywords:  regression memory-leak  |  Actual Points:  0
Parent ID:  | Points:  0
 Reviewer:  |Sponsor:
+
Changes (by dgoulet):

 * status:  needs_review => merge_ready


Comment:

 lgtm;

--
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] #21687 [Applications/Tor Browser]: Make sure prefetch in the network predictor adheres to design guidelines

2017-03-13 Thread Tor Bug Tracker & Wiki
#21687: Make sure prefetch in the network predictor adheres to design guidelines
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff52-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor4
--+--

Comment (by gk):

 "Adhering to our Tor Browser design guidelines" could mean as well making
 sure it is (still disabled), see: #16633 for the predictor isolation.

--
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] #21334 [Core Tor/Tor]: prop224: Update prop224 HS desriptor generation code to produce the latest descriptor format

2017-03-13 Thread Tor Bug Tracker & Wiki
#21334: prop224: Update prop224 HS desriptor generation code to produce the 
latest
descriptor format
--+
 Reporter:  asn   |  Owner:  asn
 Type:  enhancement   | Status:
  |  merge_ready
 Priority:  Very High |  Milestone:  Tor:
  |  0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs, prop224, review-group-16  |  Actual Points:
Parent ID:| Points:  3
 Reviewer:  nickm |Sponsor:  SponsorR-
  |  must
--+

Comment (by asn):

 Replying to [comment:14 nickm]:
 > It looks like my comments were all addressed; please feel free to squash
 now.  If possible, please base the squash on the same starting point as
 "bug21334_v2", so that I can run "git diff bug21334_v2 bug21334_v3" and
 confirm that they are the same?  Once that's done and the tickets
 mentioned in the comments on gitlab are opened, I'm happy to merge this.
 >
 > Also, in the future, please consider using fixup! or squash! rather than
 TOSQUASH: "git-rebase" can handle those automatically.

 Hey Nick,

 I pushed `bug21334_v3` in my repo. The diff should be identical to my v2
 branch.

 I also opened #21693 for the double-base64 issue as requested, and I
 started working on a PoC for it. It's quite messy due to the nature of the
 change and the `char*->uint8_t` pointer madness, but I hope to have a
 draft ready at some point this week.

--
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] #21641 [Core Tor/Tor]: Prop274: Rotate onion keys less frequently

2017-03-13 Thread Tor Bug Tracker & Wiki
#21641: Prop274: Rotate onion keys less frequently
---+
 Reporter:  nickm  |  Owner:  ahf
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201703  |  Actual Points:  2.1
Parent ID: | Points:  2
 Reviewer: |Sponsor:  Sponsor4
---+
Changes (by ahf):

 * status:  accepted => needs_review
 * actualpoints:   => 2.1


Comment:

 I've added a patch set that is ready for review in my Gitlab branch
 'bugs/21641': https://gitlab.com/ahf/tor/commits/bugs/21641

--
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] #21272 [Metrics]: Onionperf deployment

2017-03-13 Thread Tor Bug Tracker & Wiki
#21272: Onionperf deployment
-+--
 Reporter:  hiro |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by hiro):

 Hi Karsten,
 Sure I will delete all the old measurements starting from the day before
 yesterday. Regarding papillare, the host and dns names where the bits that
 I was missing. Will have that changed. :)
 -Silvia

--
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] #21272 [Metrics]: Onionperf deployment

2017-03-13 Thread Tor Bug Tracker & Wiki
#21272: Onionperf deployment
-+--
 Reporter:  hiro |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 hiro, I looked at the data and have two questions:

  - It seems that the .tpf files produced by OnionPerf don't show whether
 connections were made to port 80 (and forwarded by firewall rules) or were
 made to port 8080.  But we should only use data from measurements to port
 80, or we'll compare two different measurements.  Can you delete older
 measurements from before you changed that?

  - The OnionPerf source name (`papillare`) and DNS name (`onionperf`) of
 `https://onionperf.torproject.org/papillare-5242880-2017-03-12.tpf` don't
 match, which is something we implicitly require on CollecTor (which you
 couldn't know).  Ideally, we'd stick with the naming scheme of the other
 instances and rename both to `op-de`.  That's probably easiest to
 understand for users who will see these source names on Tor Metrics and
 would rightfully ask what a papillare is.  Can you change the name of both
 OnionPerf instance and in the DNS entry?

 Thanks!

--
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] #21724 [Applications/Tor Browser]: Distinguish between Tor Browser and Firefox when macOS opens documents

2017-03-13 Thread Tor Bug Tracker & Wiki
#21724: Distinguish between Tor Browser and Firefox when macOS opens documents
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201703R |  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * cc: brade, mcs (added)
 * status:  new => needs_review
 * keywords:   => 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

Re: [tor-bugs] #17670 [Applications/Tor Browser]: Mac OSX mistakes Tor as Firefox default browser

2017-03-13 Thread Tor Bug Tracker & Wiki
#17670: Mac OSX mistakes Tor as Firefox default browser
--+--
 Reporter:  patrickbateman|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 See #21724 for the CFBundleSignature change from MOZB to MOZT.

 See #21723 for a fix to the space in the Tor Browser CFBundleIdentifier.

 I don't know how to fix the Meek Tor Browser CFBundleSignature or
 CFBundleIdentifier. Is the Meek Tor Browser generated by the build
 scripts?

--
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] #21724 [Applications/Tor Browser]: Distinguish between Tor Browser and Firefox when macOS opens documents

2017-03-13 Thread Tor Bug Tracker & Wiki
#21724: Distinguish between Tor Browser and Firefox when macOS opens documents
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--

Comment (by teor):

 If we do use this, we should register MOZT with Apple, and ask mozilla if
 they want us to use a completely separate identifier instead (like TORB).

--
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] #21724 [Applications/Tor Browser]: Distinguish between Tor Browser and Firefox when macOS opens documents

2017-03-13 Thread Tor Bug Tracker & Wiki
#21724: Distinguish between Tor Browser and Firefox when macOS opens documents
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #17670
   Points:|   Reviewer:
  Sponsor:|
--+--
 Please see my branch fix-macos-bundle-signature on
 https://github.com/teor2345/tor-browser.git , which deals with the core
 issue of #17670, the MOZB CFBundleSignature change.

--
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] #21723 [Applications/Tor Browser]: Fix inconsistent generation of MOZ_MACBUNDLE_ID

2017-03-13 Thread Tor Bug Tracker & Wiki
#21723: Fix inconsistent generation of MOZ_MACBUNDLE_ID
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201703R |  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:   => TorBrowserTeam201703R
 * cc: mcs, brade (added)
 * status:  new => needs_review


--
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] #21723 [Applications/Tor Browser]: Fix inconsistent generation of MOZ_MACBUNDLE_ID

2017-03-13 Thread Tor Bug Tracker & Wiki
#21723: Fix inconsistent generation of MOZ_MACBUNDLE_ID
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #17670
   Points:|   Reviewer:
  Sponsor:|
--+--
 Please see my branch fix-macos-bundle-id on https://github.com/teor2345
 /tor-browser.git

 This appears to be a Mozilla bug, we should upstream it.

--
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] #21721 [User Experience/Website]: Update Tor Browser design doc on website

2017-03-13 Thread Tor Bug Tracker & Wiki
#21721: Update Tor Browser design doc on website
-+
 Reporter:  gk   |  Owner:  hiro
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by gk):

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


Comment:

 Fixed with commit 371a8cfadd290f2d66d164b074688b23b5af0998 (yay!) (Note I
 committed that one this time myself directly to `master` to fix #21718.
 That was an exception.)

--
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] #21718 [Internal Services/Service - git]: git-rw.torproject.org is out of sync with git.torproject.org for webwml repo

2017-03-13 Thread Tor Bug Tracker & Wiki
#21718: git-rw.torproject.org is out of sync with git.torproject.org for webwml
repo
-+
 Reporter:  gk   |  Owner:  tor-gitadm
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by Sebastian):

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


--
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] #21718 [Internal Services/Service - git]: git-rw.torproject.org is out of sync with git.torproject.org for webwml repo

2017-03-13 Thread Tor Bug Tracker & Wiki
#21718: git-rw.torproject.org is out of sync with git.torproject.org for webwml
repo
-+
 Reporter:  gk   |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by Sebastian):

 The desync was probably caused by a kernel update on git.tpo. Fixed now,
 thanks for reporting

--
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] #21718 [Internal Services/Service - git]: git-rw.torproject.org is out of sync with git.torproject.org for webwml repo

2017-03-13 Thread Tor Bug Tracker & Wiki
#21718: git-rw.torproject.org is out of sync with git.torproject.org for webwml
repo
-+
 Reporter:  gk   |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by boklm):

 Replying to [comment:1 teor]:
 > This also breaks cloning the repository:
 > {{{
 > $ git clone https://git.torproject.org/tor-browser.git/
 > Cloning into 'tor-browser'...
 > remote: Counting objects: 5042617, done.
 > remote: Compressing objects: 100% (2208/2208), done.
 > remote: Total 5042617 (delta 1652), reused 0 (delta 0)
 > Receiving objects: 100% (5042617/5042617), 1.16 GiB | 318.00 KiB/s,
 done.
 > Resolving deltas: 100% (4125718/4125718), done.
 > warning: remote HEAD refers to nonexistent ref, unable to checkout.
 > $ cd tor-browser/
 > $ git checkout master
 > error: pathspec 'master' did not match any file(s) known to git.
 > $ git branch
 > }}}

 This is expected. The repository does not have a `master` branch, so you
 need to checkout one after cloning.

 >
 > (`git branch` lists no branches)

 This is because there is no local branches after cloning, but `git branch
 -r` should list some remote ones.

--
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] #21340 [Applications/Tor Browser]: Identify and backport new patches from Firefox

2017-03-13 Thread Tor Bug Tracker & Wiki
#21340: Identify and backport new patches from Firefox
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703   |
Parent ID:  #20680   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by gk):

 Replying to [comment:4 gk]:
 > As to the patches with substantial conflicts: we would want to have
 those. (Or write our own).

 Although the network predictor is currently disabled. Thus here we should
 weigh the benefits with the complexity the new code introduces (we have
 #16633 for that fwiw; we might need to look at #16633/#16625 again.
 Especially: "The seer does not record any data, nor does it take any
 action, when in private browsing mode." seems worth to contemplate as we
 are in permanent private browsing mode.

--
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] #21718 [Internal Services/Service - git]: git-rw.torproject.org is out of sync with git.torproject.org for webwml repo

2017-03-13 Thread Tor Bug Tracker & Wiki
#21718: git-rw.torproject.org is out of sync with git.torproject.org for webwml
repo
-+
 Reporter:  gk   |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by teor):

 Oops, just ignore me, there's no master branch. Total newbie.

--
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] #21718 [Internal Services/Service - git]: git-rw.torproject.org is out of sync with git.torproject.org for webwml repo

2017-03-13 Thread Tor Bug Tracker & Wiki
#21718: git-rw.torproject.org is out of sync with git.torproject.org for webwml
repo
-+
 Reporter:  gk   |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by teor):

 Hmm, this is broken on git-rw, maybe it's a separate issue:
 {{{
 $ mv tor-browser tor-browser-broken
 $ git clone --reference tor-browser-broken --dissociate git@git-
 rw.torproject.org:tor-browser.git
 Checking connectivity: 5042617, done.
 Counting objects: 5042617, done.
 Delta compression using up to 4 threads.
 Compressing objects: 100% (865560/865560), done.
 Writing objects: 100% (5042617/5042617), done.
 Total 5042617 (delta 4125718), reused 5042617 (delta 4125718)
 warning: remote HEAD refers to nonexistent ref, unable to checkout.
 }}}

--
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] #21718 [Internal Services/Service - git]: git-rw.torproject.org is out of sync with git.torproject.org for webwml repo

2017-03-13 Thread Tor Bug Tracker & Wiki
#21718: git-rw.torproject.org is out of sync with git.torproject.org for webwml
repo
-+
 Reporter:  gk   |  Owner:  tor-gitadm
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by teor):

 This also breaks cloning the repository:
 {{{
 $ git clone https://git.torproject.org/tor-browser.git/
 Cloning into 'tor-browser'...
 remote: Counting objects: 5042617, done.
 remote: Compressing objects: 100% (2208/2208), done.
 remote: Total 5042617 (delta 1652), reused 0 (delta 0)
 Receiving objects: 100% (5042617/5042617), 1.16 GiB | 318.00 KiB/s, done.
 Resolving deltas: 100% (4125718/4125718), done.
 warning: remote HEAD refers to nonexistent ref, unable to checkout.
 $ cd tor-browser/
 $ git checkout master
 error: pathspec 'master' did not match any file(s) known to git.
 $ git branch
 }}}

 (`git branch` lists no branches)

--
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] #21272 [Metrics]: Onionperf deployment

2017-03-13 Thread Tor Bug Tracker & Wiki
#21272: Onionperf deployment
-+--
 Reporter:  hiro |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 iwakeh, patch looks good, pushed to [https://gitweb.torproject.org/karsten
 /metrics-db.git/log/?h=task-21272 my task-21272 branch].  Thanks!  Do you
 want to change anything else, or can I squash and merge?

 hiro: now looking at new data...

--
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] #21614 [Metrics]: JavaDoc should contain the version number

2017-03-13 Thread Tor Bug Tracker & Wiki
#21614: JavaDoc should contain the version number
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Yes, your suggestions about having the version in the middle and only add
 the git-revision in case of dev versions makes sense.

 Please review [https://gitweb.torproject.org/user/iwakeh/metrics-
 base.git/commit/?h=task-21614&id=e130139e1a551bcf3e6437a85799590600f4b096
 this patch].

 Example:
 {{{
 DescripTor 1.6.0 API Documentation
 DescripTor 1.6.0-dev.abcdefg API Documentation
 }}}

 I would want to wait with adding the override options until we really saw
 a use case.

--
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] #21704 [Applications/Tor Browser]: Warn users when installing Tor Browser based on ESR 52 on not SSE2 capable Windows machines

2017-03-13 Thread Tor Bug Tracker & Wiki
#21704: Warn users when installing Tor Browser based on ESR 52 on not SSE2 
capable
Windows machines
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff52-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor4
--+--

Comment (by yawning):

 #13018 would be a compelling reason to drop non-SSE2 support everywhere
 since the situation would be considerably less bad.

--
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

2017-03-13 Thread 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   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by gk):

 ESR 52 is out. Could you rebase the patches once more to the up-to-date
 Mozilla branch? FWIW: we have an official branch now in gecko-dev for
 that. There are a bunch of rebase conflicts and I'd like to review the
 final patches.

--
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] #21635 [Metrics/Atlas]: add new column for icons that do not represent tor spec flags

2017-03-13 Thread Tor Bug Tracker & Wiki
#21635: add new column for icons that do not represent tor spec flags
---+--
 Reporter:  cypherpunks|  Owner:  RaBe
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by RaBe):

 * status:  assigned => needs_review


--
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] #21636 [Metrics/Atlas]: Add a NoEdConsensus flag to Atlas

2017-03-13 Thread Tor Bug Tracker & Wiki
#21636: Add a NoEdConsensus flag to Atlas
---+--
 Reporter:  teor   |  Owner:  RaBe
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by RaBe):

 * status:  new => assigned
 * owner:  irl => RaBe


--
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] #21635 [Metrics/Atlas]: add new column for icons that do not represent tor spec flags

2017-03-13 Thread Tor Bug Tracker & Wiki
#21635: add new column for icons that do not represent tor spec flags
---+--
 Reporter:  cypherpunks|  Owner:  RaBe
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by RaBe):

 * owner:  irl => RaBe
 * status:  needs_review => assigned


--
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] #21367 [Metrics/Atlas]: mark platform string red (or in some other obvious way) if recommended_version field is not true

2017-03-13 Thread Tor Bug Tracker & Wiki
#21367: mark platform string red (or in some other obvious way) if
recommended_version field is not true
---+--
 Reporter:  cypherpunks|  Owner:  RaBe
 Type:  enhancement| Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by RaBe):

 * owner:  irl => RaBe
 * status:  needs_review => assigned


--
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] #21272 [Metrics]: Onionperf deployment

2017-03-13 Thread Tor Bug Tracker & Wiki
#21272: Onionperf deployment
-+--
 Reporter:  hiro |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Replying to [comment:29 iwakeh]:
 > Sure, I'll add a patch.

 This
 
[https://gitweb.torproject.org/user/iwakeh/collector.git/commit/?h=task-21272-2&id=883d0d8a6634c82e2097a404ca6049cfd2c3de19
 change] is indeed shorter than its description.

 (Just noticed, I accidentally, slipped in a filename length readability
 tweak, too.)

--
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] #21367 [Metrics/Atlas]: mark platform string red (or in some other obvious way) if recommended_version field is not true

2017-03-13 Thread Tor Bug Tracker & Wiki
#21367: mark platform string red (or in some other obvious way) if
recommended_version field is not true
---+--
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by teor):

 Replying to [comment:20 RaBe]:
 > By moving this icon to its own column in #21635, I think it's quite
 noticeable even in black :) We don't want the red = bad = blacklisting
 thing we talked about starting in comment:11...

 OK, let's see how it goes :-)

--
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] #21367 [Metrics/Atlas]: mark platform string red (or in some other obvious way) if recommended_version field is not true

2017-03-13 Thread Tor Bug Tracker & Wiki
#21367: mark platform string red (or in some other obvious way) if
recommended_version field is not true
---+--
 Reporter:  cypherpunks|  Owner:  irl
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by RaBe):

 By moving this icon to its own column in #21635, I think it's quite
 noticeable even in black :) We don't want the red = bad = blacklisting
 thing we talked about starting in comment:11...

--
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] #6355 [Metrics/Atlas]: Distinguish between running relays and non-running relays which last had the Running flag

2017-03-13 Thread Tor Bug Tracker & Wiki
#6355: Distinguish between running relays and non-running relays which last had
the Running flag
---+--
 Reporter:  karsten|  Owner:  RaBe
 Type:  enhancement| Status:  needs_review
 Priority:  High   |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by RaBe):

 * status:  assigned => needs_review


--
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] #6355 [Metrics/Atlas]: Distinguish between running relays and non-running relays which last had the Running flag

2017-03-13 Thread Tor Bug Tracker & Wiki
#6355: Distinguish between running relays and non-running relays which last had
the Running flag
---+--
 Reporter:  karsten|  Owner:  RaBe
 Type:  enhancement| Status:  assigned
 Priority:  High   |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by RaBe):

 * owner:  phw => RaBe
 * status:  needs_review => assigned


--
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] #21722 [Internal Services/Service - git]: Do you want to move the old torbrowser to git attic?

2017-03-13 Thread Tor Bug Tracker & Wiki
#21722: Do you want to move the old torbrowser to git attic?
-+
 Reporter:  teor |  Owner:  tor-gitadm
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by gk):

 * owner:  tbb-team => tor-gitadm
 * component:  Applications/Tor Browser => Internal Services/Service - git
 * type:  defect => enhancement


Comment:

 Sounds good to me. I guess that's a task for the git folks? (moving that
 there)

--
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] #21704 [Applications/Tor Browser]: Warn users when installing Tor Browser based on ESR 52 on not SSE2 capable Windows machines (was: Warn users when installing Tor Browser based on ESR

2017-03-13 Thread Tor Bug Tracker & Wiki
#21704: Warn users when installing Tor Browser based on ESR 52 on not SSE2 
capable
Windows machines
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff52-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor4
--+--
Description changed by gk:

Old description:

> We should be proactive and warn users of installing Tor Browser 52 on
> machines not capable of SSE 2. See:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1271759 installer adaptions
> Mozilla made. And I guess we can check that in our Linux start script as
> well (see: comment:2:ticket:19316).

New description:

 We should be proactive and warn users of installing Tor Browser 52 on
 Windows machines not capable of SSE 2. See:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1271759 installer adaptions
 Mozilla made. We can check that in our Linux start script later with the
 advent of ESR 59 based Tor Browsers as well (see: comment:2:ticket:19316).

--

--
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] #21704 [Applications/Tor Browser]: Warn users when installing Tor Browser based on ESR 52 on not SSE2 capable machines

2017-03-13 Thread Tor Bug Tracker & Wiki
#21704: Warn users when installing Tor Browser based on ESR 52 on not SSE2 
capable
machines
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff52-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor4
--+--

Comment (by gk):

 Replying to [comment:2 cypherpunks]:
 > Well, it seems you've decided to follow Mozilla blindly in all its
 decisions, good or bad. But it's a cul-de-sac.
 > Is there any chance that you could change your mind?
 > If Mozilla is doing something wrong in a hurry, and you see it, why
 don't you tell them about it?
 > If they want to make supplementary things mandatory (e.g. SSE2), when
 other FOSS devs are doing the opposite, why don't you mind?
 > If they advertise the worst proprietary things in history (SSE2, needed
 to be "fixed" by SSE3, and Pentium 4, yes, even Intel confirmed that) in
 2017(!), why nobody asks what's going on?
 > So, having ESR52-based TBB cross-compiled and operational (w/o SSE2),
 why do you still drag those ### patches into Tor Browser, even when
 Mozilla requires them for Windows only?
 > Don't break the rules, please.

 Thanks for pointing this out. Actually, we only want to have this for
 Windows right now, as Linux at least won't break until ESR 59
 (https://bugzilla.mozilla.org/show_bug.cgi?id=1274196). I am updating the
 ticket accordingly.

--
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] #19316 [Applications/Tor Browser]: Make sure our updates are dealing with SSE requirement properly

2017-03-13 Thread Tor Bug Tracker & Wiki
#19316: Make sure our updates are dealing with SSE requirement properly
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 It seems like all macOS Intel machines are SSE2 capable, so we are fine in
 that regard.

--
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] #21722 [Applications/Tor Browser]: Do you want to move the old torbrowser to git attic?

2017-03-13 Thread Tor Bug Tracker & Wiki
#21722: Do you want to move the old torbrowser to git attic?
--+--
 Reporter:  teor  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 It's confusing to have similar names in git:
 * https://gitweb.torproject.org/torbrowser.git/
 * https://gitweb.torproject.org/tor-browser.git/

--
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] #19316 [Applications/Tor Browser]: Make sure our updates are dealing with SSE requirement properly

2017-03-13 Thread Tor Bug Tracker & Wiki
#19316: Make sure our updates are dealing with SSE requirement properly
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  new => needs_revision


Comment:

 Replying to [comment:7 boklm]:
 > Replying to [comment:1 mcs]:
 > > Similar to the minSupportedOSVersion update manifest attribute that we
 added for the Mac OS 10.6 issue (see
 https://trac.torproject.org/projects/tor/ticket/13047#comment:3), we
 should add support for a new attribute such as: `minInstructionSet="SSE2"`
 >
 > I attached a first version of a patch to do that, but I did not test it
 yet, so it may not work.
 >
 > I think there will still be an issue with people upgrading to the new
 ESR52 version from Tor Browser <= 6.5.1 (skipping the version that added
 support for the minInstructionSet attribute), as their browser will not
 know this attribute. If we want to avoid this, we will need to change the
 `update_2` from the updates URL to `update_3` (similar to what we did in
 #13047).

 The plan sounds good to me. I think we should be less strict here, though:
 it seems SSE2 is only required for Windows builds with ESR 52. The Linux
 bug is https://bugzilla.mozilla.org/show_bug.cgi?id=1274196 which will
 land in Firefox 53. I am not sure about OS X. The tracking bug for the
 update on Mozilla's side is:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1274196 and there is a way to
 detect SSE2 support for Linux using UpdateUtils code included in Firefox:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1277359.

--
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] #21614 [Metrics]: JavaDoc should contain the version number

2017-03-13 Thread Tor Bug Tracker & Wiki
#21614: JavaDoc should contain the version number
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 How about we add the revision to -dev versions only, but not to released
 versions?  So, "DescripTor 1.6.0 API Documentation" and "DescripTor
 1.6.0-dev 5b1db5d API Documentation"?

 Speaking of, your patch appends the version as in: "DescripTor API
 Documentation 1.6.0-dev", but the version seems a bit out of place there
 at the end.  How about we put together the `doctitle` in `base.xml` by
 using `"${implementation-title} ${release-version} API Documentation"`,
 possibly with the option to override it?  Plus the revision.

--
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] #21719 [Applications/Tor Browser]: Can't copy (Ctrl+C) and make search (Ctrl+F) by formulae on feynmanlectures.caltech.edu. FF 18.0.2 works fine

2017-03-13 Thread Tor Bug Tracker & Wiki
#21719: Can't copy (Ctrl+C) and make search (Ctrl+F) by formulae on
feynmanlectures.caltech.edu. FF 18.0.2 works fine
--+---
 Reporter:  Ilya_SpongeBob|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by cypherpunks):

 F*ck, endless loop after selecting one of the formulas!
 By millions of requests of
 {{{
 [03-13 09:03:27] Torbutton INFO: tor SOCKS:
 https://cdn.mathjax.org/mathjax/2.7-latest/fonts/HTML-
 CSS/TeX/png/Math/Italic/120/006D.png?V=2.7.0 via
 caltech.edu:896f45c4d4b9c1cebc4b41da97c45822
 }}}
 and then
 {{{
 A script on this page may be busy, or it may have stopped responding. You
 can stop the script now, open the script in the debugger, or let the
 script continue.

 Script: http://cdn.mathjax.org/mathjax…output/HTML-CSS/jax.js?V=2.7.0:19
 }}}
 after stopping the script
 {{{
 09:04:22.640 Error: Script terminated by timeout at:
 .initHTML@http://cdn.mathjax.org/mathjax/2.7-latest/jax/output/HTML-
 CSS/jax.js?V=2.7.0:19:20303
 .Translate@http://cdn.mathjax.org/mathjax/2.7-latest/jax/output/HTML-
 CSS/jax.js?V=2.7.0:19:16388
 
MathJax.Hub.processOutput@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config
 =TeX-AMS_HTML:19:40486
 
CALLBACK.prototype.execute@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config
 =TeX-AMS_HTML:19:3232
 CALLBACK/cb@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-
 AMS_HTML:19:2794
 AFTER@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-
 AMS_HTML:19:6677
 
MathJax.Hub.processError@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config
 =TeX-AMS_HTML:19:41513
 
MathJax.Hub.processOutput@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config
 =TeX-AMS_HTML:19:40892
 
CALLBACK.prototype.execute@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config
 =TeX-AMS_HTML:19:3232
 CALLBACK/cb@http://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-
 AMS_1 jax.js:19:20303
 09:04:22.670 TypeError: this.sink is null1 network-monitor.js:275:5
 }}}

--
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] #21721 [User Experience/Website]: Update Tor Browser design doc on website

2017-03-13 Thread Tor Bug Tracker & Wiki
#21721: Update Tor Browser design doc on website
-+--
 Reporter:  gk   |  Owner:  hiro
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by gk):

 * status:  new => needs_review


Comment:

 `bug_21721`
 
(https://gitweb.torproject.org/user/gk/webwml.git/commit/?h=bug_21721&id=371a8cfadd290f2d66d164b074688b23b5af0998)
 in my personal webwml repo has the fix up for review and merge.

--
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] #17670 [Applications/Tor Browser]: Mac OSX mistakes Tor as Firefox default browser

2017-03-13 Thread Tor Bug Tracker & Wiki
#17670: Mac OSX mistakes Tor as Firefox default browser
--+--
 Reporter:  patrickbateman|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * cc: brad, and (removed)
 * cc: brade (added)


--
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] #21721 [User Experience/Website]: Update Tor Browser design doc on website

2017-03-13 Thread Tor Bug Tracker & Wiki
#21721: Update Tor Browser design doc on website
-+--
 Reporter:  gk   |  Owner:  hiro
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 We finally managed to update our Tor Browser design doc in #15988. Now
 let's get that on the website.

--
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] #17670 [Applications/Tor Browser]: Mac OSX mistakes Tor as Firefox default browser

2017-03-13 Thread Tor Bug Tracker & Wiki
#17670: Mac OSX mistakes Tor as Firefox default browser
--+--
 Reporter:  patrickbateman|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * cc: mcs, brad, and (added)


Comment:

 Replying to [comment:3 teor]:
 > This is still a bug, it was reported again in #20105.
 >
 > Are we ever going to fix it?

 I hope so. It would go faster if we had a patch we could review.

 That said and re-reading this ticket, it seems to me that the issue could
 be solved by just adding the proper values to our `Info.plist` files. Is
 that correct?

--
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] #21272 [Metrics]: Onionperf deployment

2017-03-13 Thread Tor Bug Tracker & Wiki
#21272: Onionperf deployment
-+--
 Reporter:  hiro |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by hiro):

 Also measurements are up on tpo: https://onionperf.torproject.org/
 Still some finishing touches, but looks good.

--
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] #21719 [Applications/Tor Browser]: Can't copy (Ctrl+C) and make search (Ctrl+F) by formulae on feynmanlectures.caltech.edu. FF 18.0.2 works fine

2017-03-13 Thread Tor Bug Tracker & Wiki
#21719: Can't copy (Ctrl+C) and make search (Ctrl+F) by formulae on
feynmanlectures.caltech.edu. FF 18.0.2 works fine
--+---
 Reporter:  Ilya_SpongeBob|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * status:  new => needs_information
 * keywords:   => tbb-usability


Comment:

 Hm, and this works in a vanilla Firefox 45 ESR?

--
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] #21340 [Applications/Tor Browser]: Identify and backport new patches from Firefox

2017-03-13 Thread Tor Bug Tracker & Wiki
#21340: Identify and backport new patches from Firefox
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201703   |
Parent ID:  #20680   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-
Changes (by gk):

 * keywords:  TorBrowserTeam2017R => ff52-esr, tbb-7.0-must,
 TorBrowserTeam201703
 * status:  needs_review => needs_revision


Comment:

 I have not looked closely at the patches but for now we don't need
 {{{
 334690 Isolate AlternateService mappings by Origin Attributes
 1334693 Investigate and isolate SPDY/HTTP2 state by first-party domain
 when privacy.firstparty.isolate = true
 }}}
 .
 We have H2 and SPDY still disabled and will have to audit it first for
 other issues. We can then apply the backported patches (if we get to that
 before esr59).

 As to the patches with substantial conflicts: we would want to have those.
 (Or write our own).

--
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] #21272 [Metrics]: Onionperf deployment

2017-03-13 Thread Tor Bug Tracker & Wiki
#21272: Onionperf deployment
-+--
 Reporter:  hiro |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by hiro):

 Proxy forward up for op-nl and op-us

--
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] #13747 [Applications/Tor Browser]: Block non .onion content on .onion addresses

2017-03-13 Thread Tor Bug Tracker & Wiki
#13747: Block non .onion content on .onion addresses
--+--
 Reporter:  legind|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-security  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Resolved #21713 as duplicate.

--
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] #21713 [Applications/Tor Browser]: onion only mode

2017-03-13 Thread Tor Bug Tracker & Wiki
#21713: onion only mode
--+---
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

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


Comment:

 Duplicate of #13747.

--
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] #21712 [Applications/Tor Browser]: Is our patch for #19212 still necessary in ESR52?

2017-03-13 Thread Tor Bug Tracker & Wiki
#21712: Is our patch for #19212 still necessary in ESR52?
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Replying to [ticket:21712 arthuredelstein]:
 > I reverted the patch from #19212 and saw no crash. But I need to rebuild
 TBB/ESR45 without the patch and try to reproduce the crash so I know I am
 doing the test correctly.

 You don't need to rebuild it, Tor Browser 6.0 has the issue. It got fixed
 in 6.0.1. I just retested an old 6.0 on my machine and I still can
 reproduce the crash as outlined in #19212.

--
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] #20105 [Applications/Tor Launcher]: Selecting Open With TorBrowser on a Mac Opens the File in Default Browser Instead

2017-03-13 Thread Tor Bug Tracker & Wiki
#20105: Selecting Open With TorBrowser on a Mac Opens the File in Default 
Browser
Instead
---+---
 Reporter:  hdub   |  Owner:  brade
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by teor):

 Replying to [comment:4 cypherpunks]:
 > Replying to [comment:2 teor]:
 > > This is a Tor Browser bug, and a Tor Launcher bug.
 > >
 > > And the exact behaviour also depends on:
 > > * if Firefox is installed or not,
 > >   * if installed, which of Tor Browser or Firefox is registered under
 the Firefox 'Bundle creator OS Type code' MOZB (#17670),
 > > * if Tor Browser is already open or not (that is, whether Tor Launcher
 or Tor Browser handles the open document request), and
 > > * if Tor Browser or Firefox or some other browser is the default
 system browser.
 > >
 > > We can focus on the Tor Launcher bug in this ticket: Tor Launcher
 should handle the Open Document request, and pass it on to Tor Browser
 once it finishes launching. If it doesn't handle the Open, macOS will try
 to open it in the default browser instead.
 >
 > This issue is not just with Firefox as the default browser. Try it with
 Chrome as the default browser; it will open a Tor Browser instance if
 there isn't already one running, but the file is opened in Chrome.

 Yes, as I said, this issue happens when the default browser is some other
 browser than Firefox or Tor Browser.

 But the exact behaviour depends on whether Firefox is installed, because
 macOS confuses Firefox with Tor Browser in some circumstances.

--
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] #1922 [Core Tor/Tor]: torrc.d-style configuration directories

2017-03-13 Thread Tor Bug Tracker & Wiki
#1922: torrc.d-style configuration directories
-+-
 Reporter:  aa138346 |  Owner:
 |  Jigsaw52
 Type:  enhancement  | Status:
 |  assigned
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, intro,   |  Actual Points:
  tor-03-unspecified-201612  |
Parent ID:   | Points:  medium
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 Thanks!
 Just a reminder that before we merge this feature, we'll want some unit
 tests for it.

--
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] #21715 [Core Tor/Tor]: Possible error in the Tor manual (section "NumEntryGuards NUM")

2017-03-13 Thread Tor Bug Tracker & Wiki
#21715: Possible error in the Tor manual (section "NumEntryGuards NUM")
---+
 Reporter:  moe-szyslak-0  |  Owner:
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.1.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  easy doc   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by teor):

 * owner:  hiro =>
 * status:  new => assigned
 * keywords:  Tor Project: manual => easy doc
 * milestone:   => Tor: 0.3.1.x-final


--
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] #21716 [Core Tor/Tor]: Avoid recursive call to routerlist_remove_old_routers via router_rebuild_store (was: duplicate log output)

2017-03-13 Thread Tor Bug Tracker & Wiki
#21716: Avoid recursive call to routerlist_remove_old_routers via
router_rebuild_store
--+
 Reporter:  anstein   |  Owner:
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy intro|  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * status:  new => assigned
 * component:  Applications/Orbot => Core Tor/Tor
 * keywords:   => easy intro
 * points:   => 0.5
 * milestone:   => Tor: 0.3.2.x-final
 * owner:  n8fr8 =>


Comment:

 This is not a duplicate logging bug, and it's in tor, not orbot.

 It is due to a recursive call to routerlist_remove_old_routers via
 router_rebuild_store.

 Still, we should fix it eventually, because it's confusing, and recursive
 calls lead to subtle bugs and complex call graphs.

--
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

  1   2   >