Re: [tor-bugs] #26048 [Applications/Tor Browser]: potentially confusing "restart to update" message in ESR60 (was: potential confusing "restart to update" message in ESR60)

[Tor Bug Tracker & Wiki]

#26048: potentially confusing "restart to update" message in ESR60
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

--
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] #26045 [Applications/Tor Browser]: Create a new MAR signing key for ESR60

[Tor Bug Tracker & Wiki]

#26045: Create a new MAR signing key for ESR60
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  reopened
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  TorBrowserTeam201805,|  Actual Points:
  GeorgKoppen201805  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by sysrqb):

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


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

Re: [tor-bugs] #24515 [Applications/Tor Browser]: Make the script for downloading missing MAR files smarter

[Tor Bug Tracker & Wiki]

#24515: Make the script for downloading missing MAR files smarter
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by arthuredelstein):

 * cc: arthuredelstein (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] #25694 [Applications/Tor Browser]: Activity 3.1: Improve the user experience of updating Tor Browser

[Tor Bug Tracker & Wiki]

#25694: Activity 3.1: Improve the user experience of updating Tor Browser
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "1.1.png" 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] #25694 [Applications/Tor Browser]: Activity 3.1: Improve the user experience of updating Tor Browser

[Tor Bug Tracker & Wiki]

#25694: Activity 3.1: Improve the user experience of updating Tor Browser
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "1.2.png" removed.


--
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] #25694 [Applications/Tor Browser]: Activity 3.1: Improve the user experience of updating Tor Browser

[Tor Bug Tracker & Wiki]

#25694: Activity 3.1: Improve the user experience of updating Tor Browser
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by antonela):

 * Attachment "1.2.png" 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] #26054 [Applications/Tor Browser]: Make sure to create incrementals from previously signed MAR files

[Tor Bug Tracker & Wiki]

#26054: Make sure to create incrementals from previously signed MAR files
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-rbm
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 When creating incremental files we check right now only that MAR files
 from previous versions specified in `torbrowser_incremental_from` are
 *available*. However, this can happen if one only has built those previous
 versions with MAR files still locally available. In that case, though,
 we'll create the wrong MAR files for macOS as those previously built MAR
 files do not contain the content signing bits.

 We could be smarter and check whether the previously built MAR files are
 signed and only use them in that case for generating the incremental MAR
 files. Otherwise we would discard them and download the signed ones, as we
 do if no previously built MAR files are available locally.

--
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] #25543 [Applications/Tor Browser]: Rebase Tor Browser patches for ESR60

[Tor Bug Tracker & Wiki]

#25543: Rebase Tor Browser patches for ESR60
--+-
 Reporter:  gk|  Owner:  arthuredelstein
 Type:  task  | Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201805  |  Actual Points:
Parent ID:  #25741| Points:
 Reviewer:|Sponsor:
--+-

Comment (by mcs):

 I just attached a fixup patch `0001-fixup-Bug-4234-Use-the-Firefox-Update-
 Process-for-To.patch` that removes some code that hunts around in the
 Windows registry to decide whether to append `=1` to the update
 check URL. Arthur, please include this fixup when you create a new branch.

 For Firefox, the registry keys that are checked are set by Mozilla's
 installer. This means that they will never be set for Tor Browser, which
 also means it is a waste of time to look for them.

--
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] #25383 [Metrics/Website]: Deprecate stats.html and stats/*.csv files

[Tor Bug Tracker & Wiki]

#25383: Deprecate stats.html and stats/*.csv files
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * owner:  metrics-team => karsten
 * status:  new => accepted


Comment:

 Replying to [comment:14 irl]:
 > I believe you have just described a method of implementing the two CSV
 files for the two use cases I wanted to make sure we supported. (:

 Excellent! I'll put this on my list of things to implement then. When I
 have something, I'll put it here for review. 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] #26055 [Core Tor/DocTor]: Expire entries from 2016-01 to 2018-01 from the dirauth reject list

[Tor Bug Tracker & Wiki]

#26055: Expire entries from 2016-01 to 2018-01 from the dirauth reject list
-+--
 Reporter:  dgoulet  |  Owner:  atagar
 Type:  task | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by dgoulet):

 * status:  new => needs_review


Comment:

 See branch `ticket26055`

 https://gitweb.torproject.org/user/dgoulet/doctor.git/log/?h=ticket26055

--
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] #23883 [Core Tor/Tor]: document how to get Travis CI running on your fork of tor (was: document how to get Travis or GitLab CI running on your fork of tor)

[Tor Bug Tracker & Wiki]

#23883: document how to get Travis CI running on your fork of tor
-+-
 Reporter:  catalyst |  Owner:  Hello71
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  new-developers, tor-ci, tor-doc, |  Actual Points:
  034-roadmap-subtask, 034-triage-20180328,  |
  034-included-20180328  |
Parent ID:  #25550   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor3
-+-
Changes (by catalyst):

 * status:  needs_revision => merge_ready


Comment:

 Thanks! Looks good to me.

 Edited ticket title to narrow scope to Travis.

--
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] #16472 [Applications/Tor Browser]: Upgrade Binutils to 2.25+ for Tor Browser builds

[Tor Bug Tracker & Wiki]

#16472: Upgrade Binutils to 2.25+ for Tor Browser builds
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_information
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, boklm201805,|  Actual Points:
  TorBrowserTeam201805   |
Parent ID:  #12968   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 After bisecting, it seems the issue is starting with commit
 `13e570f80cbfb299a8858ce6830e91a6cb40ab7b`:
 https://sourceware.org/git/?p=binutils-
 gdb.git;a=commitdiff;h=13e570f80cbfb299a8858ce6830e91a6cb40ab7b

--
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] #24659 [Core Tor/Tor]: Wrap our sha2 interface in Rust which implements the appropriate traits

[Tor Bug Tracker & Wiki]

#24659: Wrap our sha2 interface in Rust which implements the appropriate traits
-+-
 Reporter:  isis |  Owner:  isis
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-crypto, review-group-34,   |  Actual Points:
  034-triage-20180328|
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  Sponsor3-can
-+-

Comment (by isis):

 Replying to [comment:21 isis]:
 > Replying to [comment:19 nickm]:
 > > How about
 > >
 > > 5. Merge, but don't write any code that requires our hash functions
 until we have the linking issues solved?
 >
 > Your call! I'm not sure the linking issues (cf. #25386) are going to be
 resolved anytime soon though.
 >
 > Marking as merge_ready.

 Err, to be clear, the branch is `bug24659_r1`
 [https://gitweb.torproject.org/user/isis/tor.git/log/?h=bug24659_r1 here].

--
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] #25761 [Core Tor/Tor]: hs: Reload signal (HUP) doesn't remove a disabled service

[Tor Bug Tracker & Wiki]

#25761: hs: Reload signal (HUP) doesn't remove a disabled service
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  032-backport, 033-backport, tor-hs,  |  Actual Points:
  regression |
Parent ID:   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => needs_revision
 * reviewer:   => dgoulet


Comment:

 lgtm;

 But you need to base your branch on 032 for backport.

--
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] #25993 [Core Tor/Tor]: Improve deliberate test coverage for addressmap_get_virtual_address()

[Tor Bug Tracker & Wiki]

#25993: Improve deliberate test coverage for addressmap_get_virtual_address()
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, tor-tests-coverage, tor- |  Actual Points:
  tests-unit |
Parent ID:  #25908   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor3-can
-+-
Changes (by catalyst):

 * status:  needs_review => merge_ready


Comment:

 Code change look good to me!  I left a comment on GitHub with some
 suggestions about the wording of a comment.

 I haven't fully confirmed that every new test does what it claims to do,
 but it looks likely that the coverage flapping for the .0 and .255 case is
 gone.

--
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] #24659 [Core Tor/Tor]: Wrap our sha2 interface in Rust which implements the appropriate traits

[Tor Bug Tracker & Wiki]

#24659: Wrap our sha2 interface in Rust which implements the appropriate traits
-+-
 Reporter:  isis |  Owner:  isis
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-crypto, review-group-34,   |  implemented
  034-triage-20180328|  Actual Points:
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  Sponsor3-can
-+-
Changes (by nickm):

 * status:  merge_ready => 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

Re: [tor-bugs] #24659 [Core Tor/Tor]: Wrap our sha2 interface in Rust which implements the appropriate traits

[Tor Bug Tracker & Wiki]

#24659: Wrap our sha2 interface in Rust which implements the appropriate traits
-+-
 Reporter:  isis |  Owner:  isis
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-crypto, review-group-34,   |  Actual Points:
  034-triage-20180328|
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  Sponsor3-can
-+-

Comment (by nickm):

 Merged the rebased bug24659_r2, along with tor-rust-dependencies update.

--
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] #26055 [Core Tor/DocTor]: Expire entries from 2016-01 to 2018-01 from the dirauth reject list

[Tor Bug Tracker & Wiki]

#26055: Expire entries from 2016-01 to 2018-01 from the dirauth reject list
-+
 Reporter:  dgoulet  |  Owner:  atagar
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 This is the ticket for the DocTor patch to the `tracked_relays.cfg`
 module.

 Entries from 2016-01 up to 2018-01 will be expire from the current
 suggested reject list of the directory authorities.

 Similar to:
 
https://gitweb.torproject.org/doctor.git/tree/data/tracked_relays.cfg?id=b4fba470ba173c9ee6416334e6d42432db47240a
 and
 
https://gitweb.torproject.org/doctor.git/commit/?id=04cb543d11b3ab9f4c336ba9f3402f47c968a5b5

--
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] #26045 [Applications/Tor Browser]: Create a new MAR signing key for ESR60

[Tor Bug Tracker & Wiki]

#26045: Create a new MAR signing key for ESR60
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  invalid
 Keywords:  TorBrowserTeam201805,|  Actual Points:
  GeorgKoppen201805  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

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


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

Re: [tor-bugs] #26054 [Applications/Tor Browser]: Make sure to create incrementals from previously signed MAR files

[Tor Bug Tracker & Wiki]

#26054: Make sure to create incrementals from previously signed MAR files
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-rbm   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Description changed by gk:

Old description:

> When creating incremental files we check right now only that MAR files
> from previous versions specified in `torbrowser_incremental_from` are
> *available*. However, this can happen if one only has built those
> previous versions with MAR files still locally available. In that case,
> though, we'll create the wrong MAR files for macOS as those previously
> built MAR files do not contain the content signing bits.
>
> We could be smarter and check whether the previously built MAR files are
> signed and only use them in that case for generating the incremental MAR
> files. Otherwise we would discard them and download the signed ones, as
> we do if no previously built MAR files are available locally.

New description:

 When creating incremental MAR files we check right now only that MAR files
 from previous versions specified in `torbrowser_incremental_from` are
 *available*. However, this can happen if one only has built those previous
 versions with MAR files still locally available. In that case, though,
 we'll create the wrong MAR files for macOS as those previously built MAR
 files do not contain the content signing bits.

 We could be smarter and check whether the previously built MAR files are
 signed and only use them in that case for generating the incremental MAR
 files. Otherwise we would discard them and download the signed ones, as we
 do if no previously built MAR files are available locally.

--

--
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] #23886 [Core Tor/Tor]: Write FFI bindings and function pointers for ed25519-dalek

[Tor Bug Tracker & Wiki]

#23886: Write FFI bindings and function pointers for ed25519-dalek
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, rust-pilot, ed25519, tor-  |  Actual Points:
  crypto, crypto, 034-triage-20180328,   |
  034-removed-20180328, 035-proposed |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
 |  Sponsor3-can
-+-
Changes (by isis):

 * keywords:
 rust, rust-pilot, ed25519, tor-crypto, crypto, 034-triage-20180328,
 034-removed-20180328
 =>
 rust, rust-pilot, ed25519, tor-crypto, crypto, 034-triage-20180328,
 034-removed-20180328, 035-proposed
 * milestone:  Tor: unspecified => Tor: 0.3.5.x-final


Comment:

 Nominating for 0.3.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] #25549 [Core Tor/Tor]: Add tor CI config for AppVeyor

[Tor Bug Tracker & Wiki]

#25549: Add tor CI config for AppVeyor
-+-
 Reporter:  isis |  Owner:  saper
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, tor-testing, 034-roadmap-|  Actual Points:
  subtask, 034-triage-20180328,  |
  034-included-20180328  |
Parent ID:  #25550   | Points:  2
 Reviewer:  isis, catalyst   |Sponsor:
 |  Sponsor3
-+-
Changes (by isis):

 * status:  needs_review => needs_revision


Comment:

 Changing this back to needs_revision, since maybe there's something
 smarter we could do to get a not-mismatched OpenSSL on that system?

--
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] #24659 [Core Tor/Tor]: Wrap our sha2 interface in Rust which implements the appropriate traits

[Tor Bug Tracker & Wiki]

#24659: Wrap our sha2 interface in Rust which implements the appropriate traits
-+-
 Reporter:  isis |  Owner:  isis
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-crypto, review-group-34,   |  Actual Points:
  034-triage-20180328|
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  Sponsor3-can
-+-

Comment (by isis):

 Replying to [comment:23 isis]:
 > I've rebased onto the latest master in my `bug24659_r2` branch, let's
 wait and [https://travis-ci.org/isislovecruft/tor/builds/376514666 see if
 Travis passes]…

 I fixed a couple small issues that were breaking distcheck, and [https
 ://travis-ci.org/isislovecruft/tor/builds/376555016 it's passing now]
 (minus the Cargo offline builds). The corresponding tor-rust-dependencies
 branch is `add/digest` [https://github.com/isislovecruft/tor-rust-
 dependencies/tree/add/digest here].

--
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] #24658 [Core Tor/Tor]: Split/refactor crypto.h into smaller separate modules

[Tor Bug Tracker & Wiki]

#24658: Split/refactor crypto.h into smaller separate modules
-+-
 Reporter:  isis |  Owner:
 |  ffmancera
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-crypto, refactor, review-|  Actual Points:
  group-32, review-group-34, |
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:
 Reviewer:  nickm, isis  |Sponsor:
 |  Sponsor8-can
-+-
Changes (by isis):

 * reviewer:  nickm => nickm, isis


Comment:

 Setting myself as reviewer.

--
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] #24659 [Core Tor/Tor]: Wrap our sha2 interface in Rust which implements the appropriate traits

[Tor Bug Tracker & Wiki]

#24659: Wrap our sha2 interface in Rust which implements the appropriate traits
-+-
 Reporter:  isis |  Owner:  isis
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-crypto, review-group-34,   |  Actual Points:
  034-triage-20180328|
Parent ID:   | Points:  1
 Reviewer:  nickm|Sponsor:
 |  Sponsor3-can
-+-

Comment (by isis):

 I've rebased onto the latest master in my `bug24659_r2` branch, let's wait
 and [https://travis-ci.org/isislovecruft/tor/builds/376514666 see if
 Travis passes]…

--
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] #25543 [Applications/Tor Browser]: Rebase Tor Browser patches for ESR60

[Tor Bug Tracker & Wiki]

#25543: Rebase Tor Browser patches for ESR60
--+-
 Reporter:  gk|  Owner:  arthuredelstein
 Type:  task  | Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201805  |  Actual Points:
Parent ID:  #25741| Points:
 Reviewer:|Sponsor:
--+-
Changes (by mcs):

 * Attachment "0001-fixup-Bug-4234-Use-the-Firefox-Update-Process-for-
 To.patch" added.

 remove =1 code

--
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] #25543 [Applications/Tor Browser]: Rebase Tor Browser patches for ESR60

[Tor Bug Tracker & Wiki]

#25543: Rebase Tor Browser patches for ESR60
--+-
 Reporter:  gk|  Owner:  arthuredelstein
 Type:  task  | Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201805  |  Actual Points:
Parent ID:  #25741| Points:
 Reviewer:|Sponsor:
--+-

Comment (by arthuredelstein):

 Thanks to mcs and brade for the updater patches and fixups. Here's a new
 branch including them all, rebased to the latest Firefox 60 (which is now
 in mozilla/release).

--
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] #26042 [Core Tor/Tor]: Add a new option "RouteDNSTraffic" to prevent noobs from insecure way to use Tor.

[Tor Bug Tracker & Wiki]

#26042: Add a new option "RouteDNSTraffic" to prevent noobs from insecure way to
use Tor.
--+--
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  task  | Status:  reopened
 Priority:  High  |  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

 * status:  closed => reopened
 * cc: wanking@… (added)
 * resolution:  wontfix =>


--
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] #22343 [Applications/Tor Browser]: Save as... in the context menu results in using the catch-all circuit

[Tor Bug Tracker & Wiki]

#22343: Save as... in the context menu results in using the catch-all circuit
-+-
 Reporter:  gk   |  Owner:
 |  arthuredelstein
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  tbb-linkability, ff52-esr,   |  Actual Points:
  tbb-7.0-must, tbb-7.0-issues, tbb-regression,  |
  tbb-7.0-frequent, TorBrowserTeam201805 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:
 tbb-linkability, ff52-esr, tbb-7.0-must, tbb-7.0-issues, tbb-
 regression, tbb-7.0-frequent, TorBrowserTeam201805R
 =>
 tbb-linkability, ff52-esr, tbb-7.0-must, tbb-7.0-issues, tbb-
 regression, tbb-7.0-frequent, TorBrowserTeam201805
 * status:  needs_review => needs_revision


Comment:

 According to our meeting yesterday marking this as `needs_revision` as we
 should base the patch on ESR60.

--
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] #25993 [Core Tor/Tor]: Improve deliberate test coverage for addressmap_get_virtual_address()

[Tor Bug Tracker & Wiki]

#25993: Improve deliberate test coverage for addressmap_get_virtual_address()
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tor-ci, tor-tests-coverage, tor- |  Actual Points:
  tests-unit |
Parent ID:  #25908   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor3-can
-+-
Changes (by nickm):

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


Comment:

 Thanks for the review! I've added the comment you suggested in a new fixup
 commit on the branch, and then squashed it as `ticket25993_squashed` and
 merged the branch.

--
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] #25483 [Obfuscation/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
---+--
 Reporter:  arlolra|  Owner:  sukhbir
 Type:  project| Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201805   |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by sukhbir):

 So I tried building with clang 6 today just to confirm the theory that one
 of these bugs was fixed in clang 6.0.0 (and hope the other one was as well
 :) and ran into the following error. I replaced the precompiled clang
 webrtc with clang 6.0.0 but I didn't bother to set `clang_base_path` and
 just replaced it in the default lookup directory `third_party/llvm-
 build/Release+Asserts`.

 I will continue to debug this (and try with master instead of release as
 well) but if you have seen this before, please let me know. A quick search
 tells me this may be related to cross-compilation but I haven't found any
 solutions yet.

 {{{
 [188/2538] CC
 obj/third_party/libvpx/libvpx_intrinsics_avx/quantize_avx.obj
 [189/2538] CC obj/third_party/libvpx/libvpx_intrinsics_avx2/sad4d_avx2.obj
 FAILED: obj/third_party/libvpx/libvpx_intrinsics_avx2/sad4d_avx2.obj
 ../../third_party/llvm-build/Release+Asserts/bin/clang-cl --rsp-
 quoting=posix /nologo /showIncludes
 @obj/third_party/libvpx/libvpx_intrinsics_avx2/sad4d_avx2.obj.rsp /c
 ../../third_party/libvpx/source/libvpx/vpx_dsp/x86/sad4d_avx2.c
 /Foobj/third_party/libvpx/libvpx_intrinsics_avx2/sad4d_avx2.obj
 /Fd"obj/third_party/libvpx/libvpx_intrinsics_avx2_c.pdb"
 In file included from
 ../../third_party/libvpx/source/libvpx/vpx_dsp/x86/sad4d_avx2.c:10:
 In file included from /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/immintrin.h:134:
 /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/fmaintrin.h(73,10):  error:
 invalid conversion between vector type '__m128' (vector of 4 'float'
 values) and integer type 'int' of different size
   return (m128)builtin_ia32_vfmsubss3((v4sf)A, (v4sf)B, (v4sf)C);
 ^~~
 /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/fmaintrin.h(79,10):  error:
 invalid conversion between vector type '__m128d' (vector of 2 'double'
 values) and integer type 'int' of different size
   return (m128d)builtin_ia32_vfmsubsd3((v2df)A, (v2df)B, (v2df)C);
 ^~~~
 /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/fmaintrin.h(97,10):  error:
 invalid conversion between vector type '__m128' (vector of 4 'float'
 values) and integer type 'int' of different size
   return (m128)builtin_ia32_vfnmaddss3((v4sf)A, (v4sf)B, (v4sf)C);
 ^~~~
 /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/fmaintrin.h(103,10):  error:
 invalid conversion between vector type '__m128d' (vector of 2 'double'
 values) and integer type 'int' of different size
   return (m128d)builtin_ia32_vfnmaddsd3((v2df)A, (v2df)B, (v2df)C);
 ^
 /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/fmaintrin.h(121,10):  error:
 invalid conversion between vector type '__m128' (vector of 4 'float'
 values) and integer type 'int' of different size
   return (m128)builtin_ia32_vfnmsubss3((v4sf)A, (v4sf)B, (v4sf)C);
 ^~~~
 /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/fmaintrin.h(127,10):  error:
 invalid conversion between vector type '__m128d' (vector of 2 'double'
 values) and integer type 'int' of different size
   return (m128d)builtin_ia32_vfnmsubsd3((v2df)A, (v2df)B, (v2df)C);
 ^
 Note: including file:  /var/tmp/build/webrtc/src/third_party/llvm-
 build/Release+Asserts/lib/clang/6.0.0/include/fxsrintrin.h
 6 errors generated.
 [190/2538] CC
 obj/third_party/libvpx/libvpx_intrinsics_avx2/fwd_txfm_avx2.obj
 FAILED: obj/third_party/libvpx/libvpx_intrinsics_avx2/fwd_txfm_avx2.obj
 ../../third_party/llvm-build/Release+Asserts/bin/clang-cl --rsp-
 quoting=posix /nologo /showIncludes
 @obj/third_party/libvpx/libvpx_intrinsics_avx2/fwd_txfm_avx2.obj.rsp /c
 ../../third_party/libvpx/source/libvpx/vpx_dsp/x86/fwd_txfm_avx2.c
 

Re: [tor-bugs] #25549 [Core Tor/Tor]: Add tor CI config for AppVeyor

[Tor Bug Tracker & Wiki]

#25549: Add tor CI config for AppVeyor
-+-
 Reporter:  isis |  Owner:  saper
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, tor-testing, 034-roadmap-|  Actual Points:
  subtask, 034-triage-20180328,  |
  034-included-20180328  |
Parent ID:  #25550   | Points:  2
 Reviewer:  isis, catalyst   |Sponsor:
 |  Sponsor3
-+-

Comment (by saper):

 So, it seems, `--with-openssl-dir` fixed the OpenSSL versioning mismatch
 issue.

 
http://repo.or.cz/tor/appveyor.git/commitdiff/eb6231a97d4b864817df51886001aa8a41b28bac

--
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] #25483 [Obfuscation/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
---+--
 Reporter:  arlolra|  Owner:  sukhbir
 Type:  project| Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201805   |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by sukhbir):

 OK, I managed to resolve comment:28 (by properly linking), and
 unfortunately, the same error.

 {{{
 
/var/tmp/dist/mingw-w64/lib/gcc/x86_64-w64-mingw32/5.4.0/../../../../x86_64-w64-mingw32/lib/../lib/libstdc++.a
 (cow-stdexcept.o): In function `std::string::_M_data() const':
 
/var/tmp/build/gcc/x86_64-w64-mingw32/libstdc++-v3/src/c++11/../../../../gcc-5.4.0/libstdc++-v3/src/c++11
 /cow-stdexcept.cc:44: multiple definition of
 `std::logic_error::logic_error(std::logic_error const&)'
 /tmp/go-build842481917/github.com/keroserene/go-
 
webrtc/_obj/peerconnection.cc.o:peerconnection.cc:(.text$_ZNSt11logic_errorC2ERKS_[_ZNSt11logic_errorC2ERKS_]+0x0):
 first defined here
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x5a9): undefined
 reference to `cricket::AudioCodec::ToString() const'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x6de): undefined
 reference to `webrtc::RtpExtension::ToString() const'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x813): undefined
 reference to `cricket::DataCodec::ToString() const'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x8f5): undefined
 reference to `rtc::FatalMessage::FatalMessage(char const*, int)'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x96a): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xa1b): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xbf8): undefined
 reference to `rtc::FatalMessage::FatalMessage(char const*, int)'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xc6d): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xd20): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xdb1): undefined
 reference to `rtc::FatalMessage::FatalMessage(char const*, int)'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xe26): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xed5): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xf6d): undefined
 reference to `rtc::FatalMessage::FatalMessage(char const*, int)'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0xfe2): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x1094): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x112c): undefined
 reference to `rtc::FatalMessage::FatalMessage(char const*, int)'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x11a1): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 /tmp/go-build842481917/github.com/keroserene/go-
 webrtc/_obj/ctestenums.cc.o:ctestenums.cc:(.text+0x1254): undefined
 reference to `rtc::FatalMessage::~FatalMessage()'
 
/var/tmp/dist/mingw-w64/lib/gcc/x86_64-w64-mingw32/5.4.0/../../../../x86_64-w64-mingw32/bin/ld:
 $WORK/github.com/keroserene/go-webrtc/_obj/ctestenums.cc.o: bad reloc
 address 0xc0 in section `.rdata'
 }}}

 This was with clang 6.0.0; I will check with master later.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org

Re: [tor-bugs] #26053 [Core Tor/Stem]: controller.signal(stem.Signal.NEWNYM) gives error

[Tor Bug Tracker & Wiki]

#26053: controller.signal(stem.Signal.NEWNYM) gives  error
--+---
 Reporter:  cypherpunks   |  Owner:  atagar
 Type:  project   | Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Stem |Version:  Tor: 0.3.3.5-rc
 Severity:  Normal| Resolution:
 Keywords:  stem,enum,signal  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by atagar):

 * status:  new => needs_information


Comment:

 Hi cypherpunks, what version of Stem are you using? Works for me...

 {{{
 % python
 >>> import stem
 >>> stem.Signal.NEWNYM
 'NEWNYM'
 >>> stem.__version__
 '1.6.0-dev'
 }}}

--
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] #25549 [Core Tor/Tor]: Add tor CI config for AppVeyor

[Tor Bug Tracker & Wiki]

#25549: Add tor CI config for AppVeyor
-+-
 Reporter:  isis |  Owner:  saper
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, tor-testing, 034-roadmap-|  Actual Points:
  subtask, 034-triage-20180328,  |
  034-included-20180328  |
Parent ID:  #25550   | Points:  2
 Reviewer:  isis, catalyst   |Sponsor:
 |  Sponsor3
-+-

Comment (by saper):

 I wonder if that OpenSSL version check is that important, maybe it should
 be added to the autoconf tests?

 I try using `--with-openssl-dir` option, I hope that one works

--
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] #23883 [Core Tor/Tor]: document how to get Travis CI running on your fork of tor

[Tor Bug Tracker & Wiki]

#23883: document how to get Travis CI running on your fork of tor
-+-
 Reporter:  catalyst |  Owner:  Hello71
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  new-developers, tor-ci, tor-doc, |  implemented
  034-roadmap-subtask, 034-triage-20180328,  |  Actual Points:
  034-included-20180328  |
Parent ID:  #25550   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor3
-+-
Changes (by nickm):

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


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

[tor-bugs] #26056 [Core Tor/Stem]: Stem should optionally timeout when building circuits

[Tor Bug Tracker & Wiki]

#26056: Stem should optionally timeout when building circuits
---+
 Reporter:  pastly |  Owner:  atagar
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 I recently found out that `CircuitBuildTimeout
 10\nLearnCircuitBuildTimeout 0` doesn't always make your circuit build
 attempts timeout after 10 seconds. In an attemp to avoid repeating myself,
 I think the commit message[0] has a good summary of why.

 I would find it immensely useful if stem could optionally take a timeout
 on its `new_circuit` function that would raise an exception when the
 timeout is hit. For completeness, I imagine `new_circuit`'s sibling
 functions like `extend_circuit` should probably also take a timeout.

 For the time being, I've implemented a work around in sbws. I am providing
 the commit that makes the change in case it would be helpful for doing
 something similar in stem. I think it's messy, gross, and probably
 needlessly complicated. Do with it what you will :) I hope someday soon I
 can burn it with fire.

 [0]: https://github.com/pastly/simple-bw-
 scanner/commit/dc63ad05bb78bd81d68046688e6f08a717150b9f

--
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] #23231 [Applications/Tor Browser]: Error in STL wrappers when building Firefox 64-bit for Windows

[Tor Bug Tracker & Wiki]

#23231: Error in STL wrappers when building Firefox 64-bit for Windows
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorBrowserTeam201804, ff60-esr  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor4
+--
Changes (by gk):

 * keywords:  TorBrowserTeam201804, ff60-esr-will-have =>
 TorBrowserTeam201804, ff60-esr


Comment:

 Actually, we need to have at least a patch to remove the workaround in
 `tor-browser-build`, so let's move that again on our radar for ESR60.

--
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] #18287 [Applications/Tor Browser]: Use SHA-2 signature for Tor Browser setup executables

[Tor Bug Tracker & Wiki]

#18287: Use SHA-2 signature for Tor Browser setup executables
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201805,  |  Actual Points:
  GeorgKoppen201805  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-security, TorBrowserTeam201805 => tbb-security,
 TorBrowserTeam201805, GeorgKoppen201805
 * priority:  Medium => High


--
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] #22343 [Applications/Tor Browser]: Save as... in the context menu results in using the catch-all circuit

[Tor Bug Tracker & Wiki]

#22343: Save as... in the context menu results in using the catch-all circuit
-+-
 Reporter:  gk   |  Owner:
 |  arthuredelstein
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  tbb-linkability, ff52-esr,   |  Actual Points:
  tbb-7.0-must, tbb-7.0-issues, tbb-regression,  |
  tbb-7.0-frequent, TorBrowserTeam201805 |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * priority:  High => Medium


--
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] #25946 [Applications/Tor Browser]: There seems to be an issue with HTTPS Everywhere

[Tor Bug Tracker & Wiki]

#25946: There seems to be an issue with HTTPS Everywhere
--+
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by cypherpunks):

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


Comment:

 It hasn't happened for quiet some while, so closing for now.

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

Re: [tor-bugs] #25383 [Metrics/Website]: Deprecate stats.html and stats/*.csv files

[Tor Bug Tracker & Wiki]

#25383: Deprecate stats.html and stats/*.csv files
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Replying to [comment:12 irl]:
 > Are we strongly against the idea of providing two CSV files?

 I have been thinking a lot about this yesterday, and I think the answer
 is: yes.

 Providing two types of CSV files pretty much doubles our effort for adding
 new aggregations or graphs as well as changing or removing parts. I'd
 prefer the process for adding or improving graphs to get easier, not
 harder.

 Let's try to provide just one type of CSV files, assuming that we don't
 break existing, valid use cases.

 But let's find a way to stop providing our pre-aggregated statistics
 files. They are not the best interface that we can provide. And they are
 an interface that can become quite painful to maintain in the future.

 > I'd like to see the current CSV that only contains the data used to
 produce the plot, and then additionally the full CSV pre-filtering that
 would contain all the data.
 >
 > This would work for the use case where you want to do your own
 processing on the data and would also work for the use case where someone
 wanted to produce plots using the same data that we have already filtered
 and processed.
 >
 > For the full CSV file, a header would probably be useful. It may also be
 useful to have an HTML page that contains a list of all the available CSV
 files but the specifications for those files could be documented in the
 headers of the CSVs. We wouldn't need to list the individual pre-filtered
 CSV files on that page.

 Understood, I think.

 Here's another suggestion:

  4. We provide 1 CSV file per graph that is parameterized by default and
 that can also be requested without any parameters. The link on the graph
 page would contain the same parameters as the graph, so that the CSV file
 content would be pretty close to what's shown in the graph. Except that
 the file might contain a few more columns. But the header would explain
 those columns. And the header would also say that it's possible to drop
 parameters to get more data for different parameter combinations of this
 graph.

 Let's make this more concrete by adding sample data:

 The CSV link on the current [https://metrics.torproject.org/userstats-
 relay-country.html Relay users] graph page would read (line break added
 for visibility):

 {{{
 https://metrics.torproject.org/userstats-relay-country.csv?
 start=2018-02-07=2018-05-08=all=off
 }}}

 That first and last lines would be:

 {{{
 #
 # The Tor Project
 #
 # URL: https://metrics.torproject.org/userstats-relay-
 country.csv?start=2018-02-07=2018-05-08=all=off
 #
 # Insert some specification...
 #
 date,country,users,downturns,upturns,lower,upper
 2018-02-07,,4071868
 2018-02-08,,3815277
 2018-02-09,,4000274
 [...]
 2018-05-03,,2296101
 2018-05-04,,2341577
 2018-05-05,,2229328
 }}}

 Now, if someone's interested in date for all dates, a break-down by all
 possible countries, and possible censorship events, they'd simply take out
 all parameters and fetch the following file (link does not work yet):

 {{{
 https://metrics.torproject.org/userstats-relay-country.csv
 }}}

 The first and last lines would be:

 {{{
 #
 # The Tor Project
 #
 # URL: https://metrics.torproject.org/userstats-relay-country.csv
 #
 # Insert some specification...
 #
 date,country,users,downturns,upturns,lower,upper
 2011-03-06,a1,1443
 2011-03-06,a2,424
 2011-03-06,ae,8395
 [...]
 2018-05-06,zw,245,FALSE,FALSE,122,389
 2018-05-06,,2220344
 2018-05-06,??,25797
 }}}

 For comparison, the current CSV file, ''that we wouldn't provide
 anymore'', starts and ends with the following lines:

 {{{
 date,node,country,transport,version,lower,upper,clients,frac
 2011-03-06,relay,a1,1443,11
 2011-03-06,relay,a2,424,11
 2011-03-06,relay,ad,70,11
 [...]
 2018-05-06,bridge,,scramblesuit16,63
 2018-05-06,bridge,,snowflake3,63
 2018-05-06,bridge,??,1135,63
 }}}

 Note that the bridge user data would still be available on the various
 bridge users graphs.

 And we could discuss whether it makes sense to include the `frac` column
 in the relay users CSV file or not. If we include it, it would be there in
 the parameterized CSV file as well as the non-parameterized CSV file. I
 guess this is a trade-off between usability ("less is more") and
 usefulness ("more details can help").

 Thoughts?

--
Ticket URL: 

Re: [tor-bugs] #26030 [Metrics/Website]: Delete "Tor Messenger downloads and updates" section

[Tor Bug Tracker & Wiki]

#26030: Delete "Tor Messenger downloads and updates" section
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  enhancement  | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * type:  defect => enhancement


Comment:

 I have opened #26047 to produce the static analysis, and #26046 to update
 the text on the current webpage for now.

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

[tor-bugs] #26047 [Metrics/Analysis]: Create a static summary of the Tor Messenger statistics

[Tor Bug Tracker & Wiki]

#26047: Create a static summary of the Tor Messenger statistics
--+--
 Reporter:  irl   |  Owner:  metrics-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Metrics/Analysis  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:  #26030
   Points:|   Reviewer:
  Sponsor:|
--+--
 Before deleting the Tor Messenger page from the website in #26030, we
 should produce a static summary of the Tor Messenger statistics that can
 continue to be available once we have removed the dynamic 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

Re: [tor-bugs] #25318 [Applications/Quality Assurance and Testing]: Add Tor Browser nightly builds email notification

[Tor Bug Tracker & Wiki]

#25318: Add Tor Browser nightly builds email notification
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:  fixed
 Keywords:  TorBrowserTeam201805R, boklm201805   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Looks good, thanks. Merged to `master` (commit
 4580c03c937e8ccab86446d60a0d4ee29b7c07c8).

--
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] #26043 [Obfuscation/Snowflake]: building snowflake into a bundle of pluggable transports

[Tor Bug Tracker & Wiki]

#26043: building snowflake into a bundle of pluggable transports
---+
 Reporter:  hans   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by hans):

 The part I don't understand is the `node` code, that'll be quite difficult
 to use on Android.  Does Snowflake require the Javascript code to work?

--
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] #25555 [Applications/Tor Browser]: Reimplement Optimistic SOCKS feature

[Tor Bug Tracker & Wiki]

#2: Reimplement Optimistic SOCKS feature
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-preformance, ff60-esr,   |  Actual Points:
  TorBrowserTeam201805   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-preformance, ff60-esr => tbb-preformance, ff60-esr,
 TorBrowserTeam201805
 * priority:  Medium => High


--
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] #14952 [Applications/Tor Browser]: Audit HTTP/2 and SPDY if needed

[Tor Bug Tracker & Wiki]

#14952: Audit HTTP/2 and SPDY if needed
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  assigned
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-linkability, tbb-usability-  |  Actual Points:
  website, tbb-performance, ff60-esr,|
  TorBrowserTeam201805   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-linkability, tbb-usability-website, tbb-performance,
 ff60-esr =>
 tbb-linkability, tbb-usability-website, tbb-performance, ff60-esr,
 TorBrowserTeam201805


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

[Tor Bug Tracker & Wiki]

#22074: Review Firefox Developer Docs and Undocumented bugs since FF52esr
+--
 Reporter:  gk  |  Owner:  tbb-team
 Type:  task| Status:  new
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201805  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * priority:  Medium => Very High
 * keywords:  ff60-esr => ff60-esr, TorBrowserTeam201805
 * type:  defect => 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] #22176 [Applications/Tor Browser]: Review networking code for Firefox 60

[Tor Bug Tracker & Wiki]

#22176: Review networking code for Firefox 60
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201805,  |  Actual Points:
  GeorgKoppen201805  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  ff60-esr => ff60-esr, TorBrowserTeam201805, GeorgKoppen201805
 * priority:  Medium => High


--
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] #25702 [Applications/Tor Browser]: Activity 1.1 Update Tor Browser icon to follow design guidelines.

[Tor Bug Tracker & Wiki]

#25702: Activity 1.1 Update Tor Browser icon to follow design guidelines.
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team, tbb-mobile   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by gk):

 * priority:  Medium => High


--
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] #26046 [Metrics/Website]: Add text to the Tor Messenger downloads page to explain it is no longer developed

[Tor Bug Tracker & Wiki]

#26046: Add text to the Tor Messenger downloads page to explain it is no longer
developed
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:  #26030
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 This is an intermediate step on the path to #26030.

 https://blog.torproject.org/sunsetting-tor-messenger

--
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: #25543, #12968, #16472, #18867, ...

[Tor Bug Tracker & Wiki]

Batch modification to #25543, #12968, #16472, #18867, #21404, #21863, #22170, 
#22854, #23247, #23386, #23657, #24331, #24332, #24632, #24855, #24856, #25013, 
#25164, #25220, #25483, #25658, #25695, #25703, #25741 by gk:


Comment:
Move our roadmap tickets to May.

--
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: #25779, #25849

[Tor Bug Tracker & Wiki]

Batch modification to #25779, #25849 by gk:


Comment:
We need help from the network team with that. It's not necessary for the switch 
to ESR60, though.

--
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] #17965 [Applications/Tor Browser]: Isolate HPKP and HSTS to url bar domain

[Tor Bug Tracker & Wiki]

#17965: Isolate HPKP and HSTS to url bar domain
-+-
 Reporter:  mikeperry|  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-linkability, |  Actual Points:
  TorBrowserTeam201804, ff60-esr-will-have   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-linkability, TorBrowserTeam201804 => tbb-linkability,
 TorBrowserTeam201804, ff60-esr-will-have


--
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: #10394, #14205, #16341, #17252, ...

[Tor Bug Tracker & Wiki]

Batch modification to #10394, #14205, #16341, #17252, #18101, #18287, #18925, 
#19417, #20254, #20648, #21542, #21657, #21689, #21727, #21851, #22070, #22125, 
#22451, #22564, #23231, #23561, #23930, #24196, #24197, #24465, #24476, #24622, 
#25030, #25247, #25509, #25835 by gk:


Comment:
Moving remaining tickets to May.

--
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] #25693 [Applications/Tor Browser]: Activity 1.2: Make sure Firefox Photon UI works with our style guidelines

[Tor Bug Tracker & Wiki]

#25693: Activity 1.2: Make sure Firefox Photon UI works with our style 
guidelines
--+---
 Reporter:  isabela   |  Owner:  antonela
 Type:  defect| Status:  assigned
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor17
--+---
Changes (by gk):

 * priority:  Medium => High


--
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] #25483 [Obfuscation/Snowflake]: Windows reproducible build of snowflake

[Tor Bug Tracker & Wiki]

#25483: Windows reproducible build of snowflake
---+--
 Reporter:  arlolra|  Owner:  sukhbir
 Type:  project| Status:  assigned
 Priority:  High   |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201805   |  Actual Points:
Parent ID:  #19001 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by cypherpunks):

 * keywords:  TorbrowserTeam201804, TorBrowserTeam201805 =>
 TorBrowserTeam201805


--
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] #25383 [Metrics/Website]: Deprecate stats.html and stats/*.csv files

[Tor Bug Tracker & Wiki]

#25383: Deprecate stats.html and stats/*.csv files
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 Replying to [comment:13 karsten]:
 >  4. We provide 1 CSV file per graph that is parameterized by default and
 that can also be requested without any parameters. The link on the graph
 page would contain the same parameters as the graph, so that the CSV file
 content would be pretty close to what's shown in the graph. Except that
 the file might contain a few more columns. But the header would explain
 those columns. And the header would also say that it's possible to drop
 parameters to get more data for different parameter combinations of this
 graph.
 > [...]
 > Thoughts?

 I believe you have just described a method of implementing the two CSV
 files for the two use cases I wanted to make sure we supported. (:

--
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] #26043 [Obfuscation/Snowflake]: building snowflake into a bundle of pluggable transports

[Tor Bug Tracker & Wiki]

#26043: building snowflake into a bundle of pluggable transports
---+
 Reporter:  hans   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 We're making a lib to make using pluggable transports like this one really
 easy to use for Android devs. This involves building multiple projects
 into a single Android AAR library bundle, then selectively calling a
 method to start the specific transport.

 That requires that each transport's code does not have an exported main()
 function, though I think the `main()` function can be there, since this is
 loading the bundle as a shared library, not running it as an executable.
 This is my first time touching Go, so I'm open to suggestions. So I'm
 opening this issue to figure out how to make snowflake integratable.

 Here's the project for the piece that the Android dev interfaces with:
 https://github.com/guardianproject/AndroidPluggableTransportsDispatcher

 Here's the project where we build all of the various Go pluggable
 transports into the JNI bundle used by
 AndroidPluggableTransportsDispatcher:
 https://gitlab.com/eighthave/goptbundle

--
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] #22525 [Applications/Tor Browser]: content policy filter does not handle relative Locations

[Tor Bug Tracker & Wiki]

#22525: content policy filter does not handle relative Locations
-+-
 Reporter:  mcs  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-torbutton,   |  Actual Points:
  TorBrowserTeam201804, ff60-esr-will-have   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-torbutton, TorBrowserTeam201804 => tbb-torbutton,
 TorBrowserTeam201804, ff60-esr-will-have


--
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] #26044 [Applications/Tor Browser]: Create a new Tor Browser signing subkey

[Tor Bug Tracker & Wiki]

#26044: Create a new Tor Browser signing subkey
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  TorBrowserTeam201805,
 Severity:  Normal   |  GeorgKoppen201805
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 The currently used Tor Browser signing subkey expires in August. We should
 get a fresh one and use it in the next alpha.

--
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] #24632 [Applications/Tor Browser]: Update macOS toolchain for ESR 60

[Tor Bug Tracker & Wiki]

#24632: Update macOS toolchain for ESR 60
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, ff60-esr,   |  Actual Points:
  TorBrowserTeam201805, GeorgKoppen201805|
Parent ID:  #24631   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-rbm, ff60-esr, TorBrowserTeam201805 => tbb-rbm, ff60-esr,
 TorBrowserTeam201805, GeorgKoppen201805


--
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] #26045 [Applications/Tor Browser]: Create a new MAR signing key for ESR60

[Tor Bug Tracker & Wiki]

#26045: Create a new MAR signing key for ESR60
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  TorBrowserTeam201805,
 Severity:  Normal   |  GeorgKoppen201805
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Due to the new signing related code coming with ESR60 (which we intend to
 use instead of our own patch(es)), we need a new MAR signing key we want
 to ship with the first ESR60-based alpha. (See:
 https://lists.torproject.org/pipermail/tbb-dev/2018-April/000837.html item
 3)

--
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] #25817 [Applications/Tor Browser]: Add ansible scripts for setup of nigthly build server

[Tor Bug Tracker & Wiki]

#25817: Add ansible scripts for setup of nigthly build server
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  task| Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  boklm201805, TorBrowserTeam201805R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

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


Comment:

 Okay! Thanks for the explanation and fixups. I merged this to `master`
 (commit a2f565643d4c34a49712c37e3931dd6f80da7ba1). I think it would be
 worthwhile thinking about disentangling the *build* parts of the nightly
 builds from the *test* parts in `tor-browser-bundle-testsuite` but I am
 not feeling too strongly about 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] [Tor Bug Tracker & Wiki] Batch modify: #18925, #20254, #20648, #22451, ...

[Tor Bug Tracker & Wiki]

Batch modification to #18925, #20254, #20648, #22451, #24197, #24622, #25030 by 
gk:


Comment:
Moving my tickets.

--
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] #25804 [Obfuscation/Snowflake]: Domain fronting to App Engine stopped working

[Tor Bug Tracker & Wiki]

#25804: Domain fronting to App Engine stopped working
---+
 Reporter:  dcf|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  moat   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by cypherpunks):

 > Google's favicon retrieval service, which allows to retrieve one 16×16
 PNG at the time.
 Output PNG up to 256px, but you need to specify size.
 > duckduckgo.com=64

--
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] #25761 [Core Tor/Tor]: hs: Reload signal (HUP) doesn't remove a disabled service

[Tor Bug Tracker & Wiki]

#25761: hs: Reload signal (HUP) doesn't remove a disabled service
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  032-backport, 033-backport, tor-hs,  |  Actual Points:
  regression |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by asn):

 I think the fix here is to initialize `rend_service_staging_list` in
 `rend_service_prune_list()` instead of exiting the function:

 {{{
   if (!rend_service_staging_list) {
 - return;
 + rend_service_staging_list = smartlist_new();
   }
 }}}

 dgoulet what you think? does this fit the whole staging/pruning logic?

--
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] #23883 [Core Tor/Tor]: document how to get Travis or GitLab CI running on your fork of tor

[Tor Bug Tracker & Wiki]

#23883: document how to get Travis or GitLab CI running on your fork of tor
-+-
 Reporter:  catalyst |  Owner:  Hello71
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  new-developers, tor-ci, tor-doc, |  Actual Points:
  034-roadmap-subtask, 034-triage-20180328,  |
  034-included-20180328  |
Parent ID:  #25550   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor3
-+-

Comment (by Hello71):

 I decided to just point at https://docs.travis-ci.com/user/getting-started
 /#To-get-started-with-Travis-CI.

 I think we should have a page somewhere that shows the current team
 rotations. Here, I could write "if it doesn't work, ask #tor-dev or the
 current CI or community whatever member at .".

 Good point about specifying the network.

 I think this doesn't need a changes file per CodingStandards.md, since
 nobody will wonder "why did we add the documentation to use Travis". maybe
 "why did we use Travis", but not why document 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] #22176 [Applications/Tor Browser]: Review networking code for Firefox 60

[Tor Bug Tracker & Wiki]

#22176: Review networking code for Firefox 60
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201805,  |  Actual Points:
  GeorgKoppen201805  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * priority:  High => Very High


--
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] #23883 [Core Tor/Tor]: document how to get Travis or GitLab CI running on your fork of tor

[Tor Bug Tracker & Wiki]

#23883: document how to get Travis or GitLab CI running on your fork of tor
-+-
 Reporter:  catalyst |  Owner:  Hello71
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  new-developers, tor-ci, tor-doc, |  Actual Points:
  034-roadmap-subtask, 034-triage-20180328,  |
  034-included-20180328  |
Parent ID:  #25550   | Points:
 Reviewer:  catalyst |Sponsor:
 |  Sponsor3
-+-

Comment (by Hello71):

 amended commit pushed for review at same place.

--
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] #25540 [Applications/Tor Browser]: Stop building and distributing sandboxed-tor-browser binaries.

[Tor Bug Tracker & Wiki]

#25540: Stop building and distributing sandboxed-tor-browser binaries.
-+-
 Reporter:  yawning  |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, , ff60-esr, |  Actual Points:
  TorBrowserTeam201805   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-rbm => tbb-rbm, , ff60-esr, TorBrowserTeam201805


--
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] #26032 [Metrics/ExoneraTor]: suggestion URL is broken (duplicate [[]])

[Tor Bug Tracker & Wiki]

#26032: suggestion URL is broken (duplicate [[]])
+--
 Reporter:  cypherpunks |  Owner:  iwakeh
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * cc: metrics-team (added)
 * status:  accepted => needs_review


Comment:

 It seems the database query supplies some (or all; I didn't check the
 productive db) ipv6 addresses surrounded by brackets, but
 ExoneraTorServlet expects ipv6 addresses from the db to be without
 brackets, which causes the error.

 Please review
 [https://gitweb.torproject.org/user/iwakeh/exonerator.git/commit/?h=task-26032
 this patch] adding a test with various possible inputs and removing all
 superfluous brackets when creating suggestion links.

 Of course, the removal of brackets could also be placed elsewhere, for
 example into QueryResult, but the above patch puts this functionality
 close to the suggestion link generation, because this seems to be the only
 affected place.

--
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] #22176 [Applications/Tor Browser]: Review networking code for Firefox 60

[Tor Bug Tracker & Wiki]

#22176: Review networking code for Firefox 60
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201805,  |  Actual Points:
  GeorgKoppen201805  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 I wonder why the severity value doesn't match that of #21625

--
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] #25761 [Core Tor/Tor]: hs: Reload signal (HUP) doesn't remove a disabled service

[Tor Bug Tracker & Wiki]

#25761: hs: Reload signal (HUP) doesn't remove a disabled service
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  032-backport, 033-backport, tor-hs,  |  Actual Points:
  regression |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * status:  accepted => needs_review


Comment:

 Please check out branch `bug25761` for a v2 and v3 fix here.

--
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] #26049 [Applications/Tor Browser]: consider reducing the delay before the update prompt is displayed (ESR60)

[Tor Bug Tracker & Wiki]

#26049: consider reducing the delay before the update prompt is displayed 
(ESR60)
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 The doorhanger delay is controlled by the pref `app.update.promptWaitTime`
 which is defined in browser/branding/official/pref/firefox-branding.js

 The badge delay is controlled by `app.update.badgeWaitTime` in that same
 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] #25347 [Core Tor/Tor]: Tor keeps on trying the same overloaded guard over and over

[Tor Bug Tracker & Wiki]

#25347: Tor keeps on trying the same overloaded guard over and over
-+-
 Reporter:  teor |  Owner:  asn
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs,  |
  033-triage-20180320, 033-included-20180320,|
  035-roadmap-proposed   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * milestone:  Tor: 0.3.4.x-final => Tor: 0.3.5.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] #25783 [Core Tor/Tor]: Circuit creation loop when primary guards are unreachable

[Tor Bug Tracker & Wiki]

#25783: Circuit creation loop when primary guards are unreachable
--+
 Reporter:  asn   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.0.10
 Severity:  Normal| Resolution:
 Keywords:  tor-guard |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  SponsorV-can
--+
Changes (by asn):

 * milestone:  Tor: 0.3.4.x-final => Tor: 0.3.5.x-final


Comment:

 No time to debug and fix this during the 034 cycle. Let's go for 035.

--
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] #25544 [Core Tor/Tor]: Complete vanguard specification

[Tor Bug Tracker & Wiki]

#25544: Complete vanguard specification
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-guard, torspec, guard-   |  Actual Points:
  discovery, 034-roadmap-master, |
  034-triage-20180328, 034-included-20180328 |
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:
 |  SponsorV
-+-

Comment (by asn):

 Mike, how should we do this? Should we edit prop#247? Or should we edit
 `tor-spec.txt` (or some other spec file) to specify how `HS_VANGUARD`
 circuits currently work and how the vanguard script uses them? What do you
 think?

--
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] #26049 [Applications/Tor Browser]: consider reducing the delay before the update prompt is displayed (ESR60)

[Tor Bug Tracker & Wiki]

#26049: consider reducing the delay before the update prompt is displayed 
(ESR60)
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ff60-esr
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 After a browser update has been downloaded, users need to restart their
 browser to apply it. By default, a small badge is overlaid on the
 hamburger menu toolbar item to indicate that users should look in that
 menu for more info (where they will find a "Restart to update Tor Browser"
 menu item). In Tor Browser we have reduced the delay before the badge is
 displayed to zero.

 The badge is kind of subtle though, so after some period of time the
 doorhanger prompt that is being discussed in #26048 is displayed. The
 delay before the doorhanger is displayed is currently:
  Firefox 60 release channel: 8 days
  Tor Browser: 2 days
 Kathy and Mark think we should reduce it further, maybe as short as on
 hour or two. The tradeoff is that the doorhanger is "in your face" and
 will somewhat interrupt people's work (although they can continue to use
 the browser with it open, and they can dismiss it without applying the
 update).

--
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] #26004 [Core Tor/Tor]: Allow Tor to accept node_id at the end of a bandwidth file line

[Tor Bug Tracker & Wiki]

#26004: Allow Tor to accept node_id at the end of a bandwidth file line
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  fast-fix, 034-backport-maybe, 033|  Actual Points:
  -backport-maybe, 032-backport-maybe, 031   |
  -backport-maybe, 029-backport-maybe, tor-  |
  dirauth|
Parent ID:  #25925   | Points:
 Reviewer:  nickm|Sponsor:
-+-

Comment (by juga):

 Thanks for the review. Maybe log_warn should be lower, since in the spec
 we have so far we would allow files with empty bw lines?

--
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] #26035 [Metrics/Statistics]: Streamline sample quantile types used in the various modules

[Tor Bug Tracker & Wiki]

#26035: Streamline sample quantile types used in the various modules
+--
 Reporter:  karsten |  Owner:  metrics-team
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor13
+--

Comment (by iwakeh):

 Long description, true.

 Let's look at the postgresql implementation (using source of 9.6.8, but
 assuming it is not subject to frequent change,
 ./src/backend/utils/adt/orderedsetaggs.c).

 The computation of percentile_* as C-ish pseudo-code (which could easily
 be used for implementation in Java or python):
 {{{
 #!C
 /*
All values are sorted and indexed according to the order.
first and second are indices; val(k) is the value at index k;
percentile is the wanted percentile.  N is the count of values.
 */

 first = floor(percentile * N);
 second = ceil(percentile * N);
 /* if first==second the value of first is used. */
 if (first==second) {
   result = val(first);
 } else { /* if first and second differ the following interpolation is
 used. */
   proportion = (percentile * N) - first;
   /* the value is chosen between the values of first and second */
   result = val(first) + (proportion * (val(second) - val(first)));
 }

 /*---*/
 /* For comparison percentile_disc:  */
 result = val( ceil(N*percentile));
 }}}

 For values, where fractions make sense, e.g. seconds for onionperf
 results, the interpolation or continuous method could be used and for all
 else, e.g. user numbers etc., the simpler calculation (refered to as
 discontinuous) could be used.

 The classification R-x is not really a DIN and I wouldn't rely on an
 implementation without checking the source.
 Thus, using our own implementation in Java might be less trouble and
 smaller dependency counts/space used.  Python is not used anymore soon,
 and R is only used for the median and either could document the median
 calculation in R or implement the 0.5-percentile.

 Possible steps:
 * keep using postgresql percentile_cont
 * implement the equivalent Java functionality and replace commons-math, if
 this is the only functionality why it is included.
 * document percentile calculation once for Java together with postgresql
 * adapt the R median calculation, if necessary

--
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] #24456 [Core Tor/Tor]: Figure out what to do with the guardfraction feature

[Tor Bug Tracker & Wiki]

#24456: Figure out what to do with the guardfraction feature
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-dirauth, tor-guard, review-  |  Actual Points:
  group-32, review-group-33, review-group-34,|
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:  2
 Reviewer:  mikeperry|Sponsor:
-+-
Changes (by asn):

 * milestone:  Tor: 0.3.4.x-final => Tor: unspecified


Comment:

 Now that dirauths are not running the guardiness script anymore, we can
 defer this ticket for the future, until we are ready to potentially revive
 the guardiness feature.

--
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] #24658 [Core Tor/Tor]: Split/refactor crypto.h into smaller separate modules

[Tor Bug Tracker & Wiki]

#24658: Split/refactor crypto.h into smaller separate modules
-+-
 Reporter:  isis |  Owner:
 |  ffmancera
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-crypto, refactor, review-|  Actual Points:
  group-32, review-group-34, |
  033-triage-20180320, 033-included-20180320 |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
 |  Sponsor8-can
-+-
Changes (by ffmancera):

 * status:  new => needs_review


Comment:

 DH module done! Check my github branch
 [https://github.com/ffmancera/tor-1/tree/bug24658-dh_stream
 bug24658-dh_stream]. Here is the travis CI [https://travis-
 
ci.org/ffmancera/tor-1/builds/376390767?utm_source=github_status_medium=notification
 report]!

--
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] #26048 [Applications/Tor Browser]: potential confusing "restart to update" message in ESR60

[Tor Bug Tracker & Wiki]

#26048: potential confusing "restart to update" message in ESR60
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ff60-esr
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 The new doorhanger-based updater UI includes the following prompt:
  After a quick restart, Tor Browser will restore all your open tabs and
 windows that are not in Private Browsing mode.
 (this is updateRestart.message2 in locales/en-
 US/chrome/browser/browser.dtd).

 This message is potentially confusing because it implies that some tabs
 will be restored, but for most Tor Browser users nothing will be restored.
 Users may not realize that all of their windows are in 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] #26048 [Applications/Tor Browser]: potential confusing "restart to update" message in ESR60

[Tor Bug Tracker & Wiki]

#26048: potential confusing "restart to update" message in ESR60
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mcs):

 * Attachment "FF Nightly Update Prompt.png" added.

 sample update prompt (from Firefox 61.x Nightly)

--
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] #25540 [Applications/Tor Browser]: Stop building and distributing sandboxed-tor-browser binaries.

[Tor Bug Tracker & Wiki]

#25540: Stop building and distributing sandboxed-tor-browser binaries.
-+-
 Reporter:  yawning  |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-rbm, , ff60-esr, |  Actual Points:
  TorBrowserTeam201805   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Note to self: there are other rbm-tickets that will be a wontfix when
 closing this one.

--
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] #26048 [Applications/Tor Browser]: potential confusing "restart to update" message in ESR60

[Tor Bug Tracker & Wiki]

#26048: potential confusing "restart to update" message in ESR60
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 The prompt also includes a button labeled `Restart and Restore`.

--
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] #26048 [Applications/Tor Browser]: potential confusing "restart to update" message in ESR60

[Tor Bug Tracker & Wiki]

#26048: potential confusing "restart to update" message in ESR60
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 Here is what the prompt looks like in Firefox Nightly:

  [[Image(FF Nightly Update Prompt.png)]]

 It is the same in Tor Browser except both occurrences of the word
 "Nightly" are replaced with "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

Re: [tor-bugs] #24422 [Metrics/Website]: Look at Information Architecture for Tor Metrics

[Tor Bug Tracker & Wiki]

#24422: Look at Information Architecture for Tor Metrics
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:  #25404   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by irl):

 * Attachment "map.png" added.

 work in progress graph

--
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] #26031 [Metrics/Onionoo]: suspected bug in exit_addresses - no IPv6 addresses?

[Tor Bug Tracker & Wiki]

#26031: suspected bug in exit_addresses - no IPv6 addresses?
-+--
 Reporter:  cypherpunks  |  Owner:  metrics-team
 Type:  defect   | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by cypherpunks):

 * status:  new => needs_review


Comment:

 somewhat a duplicate of #16947

 to fix the onionoo side of this:

 remove "or IPv6" from the exit_addresses field description until #16947 is
 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] #26042 [Core Tor/Tor]: Add a new option "RouteDNSTraffic" to prevent noobs from insecure way to use Tor.

[Tor Bug Tracker & Wiki]

#26042: Add a new option "RouteDNSTraffic" to prevent noobs from insecure way to
use Tor.
--+-
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  task  | Status:  closed
 Priority:  High  |  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  wontfix
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by cypherpunks):

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


Comment:

 - analyzing exit traffic is a no-go
 - manipulating destinations clients defined is a no-go

 - you can not assume that everything on TCP/53 is DNS

--
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] #25870 [Core Tor/Tor]: Fix vanguard restrictions

[Tor Bug Tracker & Wiki]

#25870: Fix vanguard restrictions
--+
 Reporter:  mikeperry |  Owner:  (none)
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25546| Points:
 Reviewer:  asn   |Sponsor:
--+

Comment (by mikeperry):

 Ok. I added a commit to `mikeperry/bug25870_rebase` to document the path
 restriction changes in the manpage.

 There is also a small spec patch in `mikeperry/bug25870` in my torspec
 remote.

--
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] #26052 [Core Tor/Tor]: man page still says CacheIPv4DNS is on by default

[Tor Bug Tracker & Wiki]

#26052: man page still says CacheIPv4DNS is on by default
--+
 Reporter:  arma  |  Owner:  arma
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 in #24050 we made the SocksPort CacheIPv4DNS flag off by default, but we
 never fixed the man page to say it's off by default.

--
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] #26050 [Applications/Tor Browser]: achieve update "watershed" for ESR60-based Tor Browser

[Tor Bug Tracker & Wiki]

#26050: achieve update "watershed" for ESR60-based Tor Browser
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  ff60-esr
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Once Tor Browser is based on the ESR60 code, because of the switch to xz
 compression and SHA384-based signing for the MAR files, we will need to
 have an update "watershed" event. The purpose of this ticket is to track
 the things we need to do to make the watershed happen.

 Let's suppose that for our stable channel the first release that uses the
 new MAR format is 8.0. This means:
 * When an older version of Tor Browser (< 8.0) requests an update, it must
 receive an old format MAR file that will update it to 8.0. We must keep
 these MAR files around as long as we care about updating older browsers
 (probably a long time).
 * Newer versions of Tor Browser (>= 8.0) must receive new format MAR files
 (of course).

 Of course we will need to do this sooner for our alpha channel.

 My guess is that it will make things easier if we use a new location for
 the new update requests, e.g., from
 https://aus1.torproject.org/torbrowser/update_4.

 One useful thing to know is that setting `MAR_OLD_FORMAT=1` in the
 environment before running the `make_full_update.sh` or
 `make_incremental_update.sh` script causes the old bzip2 compression to be
 used when creating the MAR 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] #26052 [Core Tor/Tor]: man page still says CacheIPv4DNS is on by default

[Tor Bug Tracker & Wiki]

#26052: man page still says CacheIPv4DNS is on by default
--+
 Reporter:  arma  |  Owner:  arma
 Type:  defect| Status:  merge_ready
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by arma):

 * status:  assigned => merge_ready


Comment:

 My {{{bug26052}}} branch fixes this one.

--
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] #25750 [Applications/Tor Launcher]: update Tor Launcher for ESR 60

[Tor Bug Tracker & Wiki]

#25750: update Tor Launcher for ESR 60
+--
 Reporter:  mcs |  Owner:  brade
 Type:  defect  | Status:
|  needs_revision
 Priority:  Very High   |  Milestone:
Component:  Applications/Tor Launcher   |Version:
 Severity:  Normal  | Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201805  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by igt0):

 * cc: igt0 (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] #16947 [Core Tor/TorDNSEL]: TorDNSEL lacks support for IPv6 addresses

[Tor Bug Tracker & Wiki]

#16947: TorDNSEL lacks support for IPv6 addresses
---+
 Reporter:  ln5|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/TorDNSEL  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by cypherpunks):

 related: #26031

--
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] #26050 [Applications/Tor Browser]: achieve update "watershed" for ESR60-based Tor Browser

[Tor Bug Tracker & Wiki]

#26050: achieve update "watershed" for ESR60-based Tor Browser
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Not sure why I should write the obvious things, but:
 switch users of alpha channel to beta channel,
 switch users of release channel to esr channel.

--
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] #26007 [Core Tor/Tor]: Stop logging stack contents when reading a zero-length bandwidth file

[Tor Bug Tracker & Wiki]

#26007: Stop logging stack contents when reading a zero-length bandwidth file
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  033-must-maybe security-low  |  Actual Points:
  032-backport 031-backport 029-backport fast-   |
  fix|
Parent ID:  #25925   | Points:
 Reviewer:  asn  |Sponsor:
-+-

Comment (by juga):

 Thanks!, that was very useful.
 I changed the test following that, now in my branch `ticket26007_029_02`.

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