Re: [tor-bugs] #26972 [Core Tor/Tor]: Create CI task to ensure that all Rust files have been formatted with rustfmt

[Tor Bug Tracker & Wiki]

#26972: Create CI task to ensure that all Rust files have been formatted with
rustfmt
--+
 Reporter:  chelseakomlo  |  Owner:  teor
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust  |  Actual Points:
Parent ID:  #24629| Points:
 Reviewer:  teor  |Sponsor:
--+
Changes (by teor):

 * parent:   => #24629


Comment:

 I'm making #24629 the parent task, so I remember to do the merge.

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

Re: [tor-bugs] #26972 [Core Tor/Tor]: Create CI task to ensure that all Rust files have been formatted with rustfmt

[Tor Bug Tracker & Wiki]

#26972: Create CI task to ensure that all Rust files have been formatted with
rustfmt
--+
 Reporter:  chelseakomlo  |  Owner:  teor
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust  |  Actual Points:
Parent ID:| Points:
 Reviewer:  teor  |Sponsor:
--+
Changes (by teor):

 * status:  merge_ready => needs_revision


Comment:

 I'd like to merge this branch after #24629 merges.

 I'm happy to do the merge, it only affects 5d749e4bde:
 * install rustfmt in .travis.yml after the rewrite

 We should also:
 * print the rustfmt version, like we do for rustup in my 14ceee0fd1 in
 https://github.com/teor2345/tor.git

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

[tor-bugs] #27095 [Webpages]: tb-manual: Update Security Levels

[Tor Bug Tracker & Wiki]

#27095: tb-manual: Update Security Levels
-+
 Reporter:  traumschule  |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Webpages |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:  phoul
  Sponsor:   |
-+
 This commit incorporates following change to https://gitweb.torproject.org
 /tor-browser/user-manual.git

 "Security Levels" information should be updated to replace "High,
 Medium, Low" levels with the current "Safest, Safer, Standard"
 information/configuration.
 https://lists.torproject.org/pipermail/www-team/2018-June/000432.html

 C/media/security-slider/slider_window.png is changed. Note: To ensure that
 image and text are synchronized all languages and images need to be
 changed as well.

 Repository: https://git.schokokeks.org/tor-tb-manual.git/?tor-tb-
 manual.git

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

Re: [tor-bugs] #27090 [Core Tor/Tor]: Travis: enable lzma and zstd in configure, if available

[Tor Bug Tracker & Wiki]

#27090: Travis: enable lzma and zstd in configure, if available
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.5-alpha
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 Replying to [comment:1 teor]:
 > It turns out that we were never building with zstd on macOS, because the
 package config path wasn't set.
 >
 > The fix will be in my #24629 branches.

 We were never installing the package, because "brew install" installs or
 updates.

--
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] #24629 [Core Tor/Tor]: Activate osx builds on travis, at low priority

[Tor Bug Tracker & Wiki]

#24629: Activate osx builds on travis, at low priority
-+-
 Reporter:  teor |  Owner:  teor
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:   | Points:  0.5
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by teor):

 * status:  needs_revision => needs_review


Comment:

 Replying to [comment:29 catalyst]:
 > Thanks!  I'm commenting only on master, because I haven't looked at the
 others yet.
 >
 > This mostly looks good.
 >
 > `mkdir` in `before_install` should create
 `$TRAVIS_BUILD_DIR/src/rust/target`, not `$TRAVIS_BUILD_DIR/target`.

 Done in my 0.3.2 and later branches.

 > Please explicitly delete the `CARGO_HOME` settings from
 src/rust/tor_rust/include.am and src/test/test_rust.sh instead of merging
 the changes from #26038.  There are other changes in #26038 that I think
 we don't want...

 Done in my 0.3.2 branch, and re-done in 0.3.3 because a file moved.

 Replying to [comment:28 teor]:
 > Ok, so this was quite challenging to backport, because there were a lot
 of little bugs. But I think it is worth it to have working CI.

 (And it's good to have consistent CI as well.)

 Here are the revised branches I created:
 * travis-osx-029 contains:
   * the travis config rewrite
   * macOS support
 * fix a bug where missing macOS dependencies weren't being installed
 (#27090, but backported as a precaution)
   * ccache (#26952)
   * asciidoc (#27087)
   * the distcheck configure options fix (#27088) for consistency
   * It passes Travis:
 * https://travis-ci.org/teor2345/tor/builds/414029807
   * And the full matrix also passes Travis:
 * https://travis-ci.org/teor2345/tor/builds/414069609
   * (I added a changes file and fixed some typos after the linked builds)
 * travis-osx-032 also contains:
   * the lzma and zstd (macOS only) install from 0.3.1
   * make zstd actually work on macOS (#27090)
   * rust cargo online mode
   * rust cargo offline mode
   * backport src/test/test_rust.sh from master
 * stop setting $CARGO_HOME (#26497)
 * Fix $abs_top_srcdir in test_rust.sh (#27093)
   * Use cargo cache (#26952)
   * It passes Travis:
 * https://travis-ci.org/teor2345/tor/builds/414327375
   * And the full matrix also passes Travis:
 * https://travis-ci.org/teor2345/tor/builds/414328388
   * (I added a changes file and fixed some typos after the linked builds)
 * travis-osx-033 also contains:
   * stop setting $CARGO_HOME, but in a different include.am file (#26497)
   * use a consistent working directory in builds and tests (#26497)
 * I didn't backport this patch to 0.3.2, because it has a different
 (but consistent) working directory
   * Use TOR_RUST_DEPENDENCIES (the name changed in 0.3.3)
   * Check Rust with distcheck (backport from 0.3.4, not supported in
 0.3.2)
   * use --all-features in test_rust.sh for 0.3.3 and 0.3.4 (existing code)
   * It passes Travis:
 * https://travis-ci.org/teor2345/tor/builds/414349039
   * And the full matrix is running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414354578
 * travis-osx-034 also contains:
   * Check disable module dirauth with and without rust (#27088 fix)
   * It is running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414351195
   * And the full matrix is running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414354648
 * travis-osx-master also contains:
   * revert use --all-features in test_rust.sh for 0.3.3 and 0.3.4
   * It is running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414352231
   * And the full matrix is running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414354615

 I don't know if we want to fix #27091 in jenkins or in tor, I've asked
 weasel on IRC. We shouldn't merge until we work out how to fix jenkins.

--
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] #25269 [Core Tor/Tor]: Set codegen-units to 1 in src/rust/Cargo.toml to eke out every last drop of performance

[Tor Bug Tracker & Wiki]

#25269: Set codegen-units to 1 in src/rust/Cargo.toml to eke out every last 
drop of
performance
-+-
 Reporter:  cypherpunks  |  Owner:
 |  Backxwash
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, easy, 034-triage-20180328, |  Actual Points:
  034-removed-20180328, fast-fix, 035-triaged-   |
  in-20180711|
Parent ID:   | Points:  .1
 Reviewer:  nickm|Sponsor:
-+-
Changes (by chelseakomlo):

 * cc: chelseakomlo (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] #27094 [Webpages/Website]: dosc/en/debian: don't recommend specific keyserver

[Tor Bug Tracker & Wiki]

#27094: dosc/en/debian: don't recommend specific keyserver
--+
 Reporter:  traumschule   |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 We intend to work on the [[Website]] and made a tiny change to the debian
 howto to test the process.

 The repository is at https://git.schokokeks.org/tor-webwml.git/?tor-
 webwml.git

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

Re: [tor-bugs] #26337 [Core Tor/Tor]: Investigate making rust error types use the failure crate

[Tor Bug Tracker & Wiki]

#26337: Investigate making rust error types use the failure crate
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, technical-debt, tor-   |  Actual Points:
  modularity, 035-removed-20180711   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by chelseakomlo):

 * cc: chelseakomlo (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] #25628 [Core Tor/Tor]: Document our Rust coding standards for error/failure types

[Tor Bug Tracker & Wiki]

#25628: Document our Rust coding standards for error/failure types
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-doc, 034-triage-20180328,  |  Actual Points:
  034-removed-20180328   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-

Old description:

> Every crate which returns `Result`s or `Option` anywhere in its
> public interface should have an `errors.rs` module containing error types
> which implement either `Display` or `Debug`, and also `::failure::Fail`
> for making errors easier to work with between crates. See the `errors.rs`
> addition to the `protover` crate from #24031 for an example (doesn't have
> the `::failure::Fail` impl yet, because the failure crate is about to
> become 1.0.0 any day now).
>
> We should probably wait on this until failure is 1.0.0.

New description:

 Every crate which returns `Result`s or `Option` anywhere in its
 public interface should have an `errors.rs` module containing error types
 which implement either `Display` or `Debug`. See the `errors.rs` addition
 to the `protover` crate from #24031 for an example.

 In the future, when failure is 1.0.0, we should also require
 `::failure::Fail` for making errors easier to work with between crates.

--

Comment (by chelseakomlo):

 Edited ticket description to note that documenting the requirement of
 `::failure::Fail` for failure types will be a separate task once the
 `failure` crate reaches stability. See #26337 for more information.

--
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] #26337 [Core Tor/Tor]: Investigate making rust error types use the failure crate (was: make rust error types use the failure crate)

[Tor Bug Tracker & Wiki]

#26337: Investigate making rust error types use the failure crate
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, technical-debt, tor-   |  Actual Points:
  modularity, 035-removed-20180711   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-
Changes (by chelseakomlo):

 * status:  new => needs_information


Old description:

> As our Rust code increases, we'll eventually want a nicer way to convert
> between error types than we currently have.  We'll probably want to use
> boats's `failure` [https://crates.io/crates/failure crate].  They
> mentioned a while ago that they were going to make a 1.0.0 release soon,
> and afaict there's not really anything about the current release that is
> expected to change, so we can probably start working on this now-ish.

New description:

 As our Rust code increases, we'll eventually want a nicer way to convert
 between error types than we currently have.  We'll probably want to use
 boats's `failure` [https://crates.io/crates/failure crate].  They
 mentioned a while ago that they were going to make a 1.0.0 release soon,
 and afaict there's not really anything about the current release that is
 expected to change, so we can probably start working on this now-ish.

 [update] This ticket is pending stability of the `failure` crate and the
 direction of the error trait in Rust https://github.com/rust-
 lang/rfcs/pull/2504

--

--
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] #26337 [Core Tor/Tor]: make rust error types use the failure crate

[Tor Bug Tracker & Wiki]

#26337: make rust error types use the failure crate
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, technical-debt, tor-   |  Actual Points:
  modularity, 035-removed-20180711   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-

Comment (by chelseakomlo):

 Replying to [comment:4 cypherpunks3]:
 > Replying to [comment:1 chelseakomlo]:
 > > Is this going to be incorporated into the Rust standard library? If
 so, should we wait for it?
 >
 > [https://github.com/rust-lang-
 nursery/failure/commit/cad26ae30f8fb0ab3c119bc8589dd0bfc1029633 Nobody
 knows for sure. It's in flux apparently.] The "1.0 soon" plan was
 canceled.
 >
 > Also, should this be a child ticket of #25628?

 Thanks- I think waiting to see how this evolves is a good idea. I'll set
 this to "needs more information" 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] #26497 [Core Tor/Tor]: set CARGO_HOME correctly or stop using it

[Tor Bug Tracker & Wiki]

#26497: set CARGO_HOME correctly or stop using it
-+-
 Reporter:  catalyst |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.5-alpha
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-ci, 035-removed-20180711,  |  Actual Points:
  035-roadmap-proposed   |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * version:   => Tor: 0.3.1.5-alpha
 * milestone:  Tor: unspecified => 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] #27093 [Core Tor/Tor]: Consistently use ${abs_top_srcdir:-../../..} in test_rust.sh

[Tor Bug Tracker & Wiki]

#27093: Consistently use ${abs_top_srcdir:-../../..} in test_rust.sh
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.4.3-alpha
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  assigned => needs_review
 * version:  Tor: unspecified => Tor: 0.3.4.3-alpha


Comment:

 I put a patch for this in my #24629 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

[tor-bugs] #27093 [Core Tor/Tor]: Consistently use ${abs_top_srcdir:-../../..} in test_rust.sh

[Tor Bug Tracker & Wiki]

#27093: Consistently use ${abs_top_srcdir:-../../..} in test_rust.sh
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core |Version:  Tor: unspecified
  Tor/Tor|   Keywords:  not-just-linux, tor-ci, teor-was-
 Severity:  Normal   |  assigned, 034-triage-20180328,
 |  034-removed-20180328, 034-backport,
 |  035-removed-20180711, fast-fix
Actual Points:   |  Parent ID:  #24629
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Sometimes we just use ${abs_top_srcdir}

--
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] #24629 [Core Tor/Tor]: Activate osx builds on travis, at low priority

[Tor Bug Tracker & Wiki]

#24629: Activate osx builds on travis, at low priority
-+-
 Reporter:  teor |  Owner:  teor
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:   | Points:  0.5
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by teor):

 Let's deal with #26038 in a separate branch after these branches merge.

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

Re: [tor-bugs] #26038 [Core Tor/Tor]: Misc Rust/Cargo improvements (incl. use global cargo cache)

[Tor Bug Tracker & Wiki]

#26038: Misc Rust/Cargo improvements (incl. use global cargo cache)
+--
 Reporter:  Hello71 |  Owner:  Hello71
 Type:  enhancement | Status:  needs_revision
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  rust, 035-removed-20180711  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  isis|Sponsor:
+--
Changes (by teor):

 * status:  needs_information => needs_revision
 * parent:  #24629 =>


Comment:

 Based on the feedback in:
 https://trac.torproject.org/projects/tor/ticket/24629#comment:29
 https://trac.torproject.org/projects/tor/ticket/24629#comment:30

 I'm not going to try and merge this patch set into #24629.

 Once #24629 merges, please rebase this patch set on top of maint-0.3.2.

--
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] #25628 [Core Tor/Tor]: Document our Rust coding standards for error/failure types

[Tor Bug Tracker & Wiki]

#25628: Document our Rust coding standards for error/failure types
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-doc, 034-triage-20180328,  |  Actual Points:
  034-removed-20180328   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-

Comment (by cypherpunks3):

 Replying to [ticket:25628 isis]:
 > (doesn't have the `::failure::Fail` impl yet, because the failure crate
 is about to become 1.0.0 any day now).

 [https://github.com/rust-lang-
 nursery/failure/commit/cad26ae30f8fb0ab3c119bc8589dd0bfc1029633 Not
 anymore it's not.] See also #26337.

--
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] #10022 [Internal Services/Blog]: We need a new blogging system

[Tor Bug Tracker & Wiki]

#10022: We need a new blogging system
---+
 Reporter:  phobos |  Owner:  (none)
 Type:  project| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Internal Services/Blog |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  blog replacement upgrade www-team  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by traumschule):

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


Comment:

 this is obviously done. #17393 is a good choice to discuss the need of js
 maybe.

--
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] #23882 [Core Tor/Tor]: Investigate implementing a Rust allocator wrapping tor_malloc

[Tor Bug Tracker & Wiki]

#23882: Investigate implementing a Rust allocator wrapping tor_malloc
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  rust, rust-pilot,|  Actual Points:
  034-triage-20180328, 034-removed-20180328  |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-

Comment (by chelseakomlo):

 Replying to [comment:8 cypherpunks3]:
 > `GlobalAlloc` is now stable.
 >  https://doc.rust-lang.org/stable/std/alloc/trait.GlobalAlloc.html
 >  https://blog.rust-lang.org/2018/08/02/Rust-1.28.html

 Excellent, this is great news. Thanks for updating this ticket.

--
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] #26337 [Core Tor/Tor]: make rust error types use the failure crate

[Tor Bug Tracker & Wiki]

#26337: make rust error types use the failure crate
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, technical-debt, tor-   |  Actual Points:
  modularity, 035-removed-20180711   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-

Comment (by cypherpunks3):

 Replying to [comment:1 chelseakomlo]:
 > Is this going to be incorporated into the Rust standard library? If so,
 should we wait for it?

 [https://github.com/rust-lang-
 nursery/failure/commit/cad26ae30f8fb0ab3c119bc8589dd0bfc1029633 Nobody
 knows for sure. It's in flux apparently.] The "1.0 soon" plan was
 canceled.

 Also, should this be a child ticket of #25628?

--
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] #23882 [Core Tor/Tor]: Investigate implementing a Rust allocator wrapping tor_malloc

[Tor Bug Tracker & Wiki]

#23882: Investigate implementing a Rust allocator wrapping tor_malloc
-+-
 Reporter:  isis |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  rust, rust-pilot,|  Actual Points:
  034-triage-20180328, 034-removed-20180328  |
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
 |  Sponsor8-can
-+-

Comment (by cypherpunks3):

 `GlobalAlloc` is now stable.
  https://doc.rust-lang.org/stable/std/alloc/trait.GlobalAlloc.html
  https://blog.rust-lang.org/2018/08/02/Rust-1.28.html

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

Re: [tor-bugs] #25727 [Core Tor/Tor]: Add bool types to Rust coding standards guidelines

[Tor Bug Tracker & Wiki]

#25727: Add bool types to Rust coding standards guidelines
-+-
 Reporter:  isis |  Owner:  isis
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  torspec, rust, fast-fix, 035 |  Actual Points:
  -triaged-in-20180711   |
Parent ID:   | Points:  .1
 Reviewer:  catalyst |Sponsor:
 |  SponsorM-can
-+-

Comment (by catalyst):

 I left a comment on the RFC [https://github.com/rust-
 lang/rfcs/issues/992#issuecomment-389297983 here] back in May but haven't
 received a reply yet.

--
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] #27092 [Applications/TorBirdy]: Torbirdy Disabled Still Needs Tor to Fetch Emails in Thunderbird 60+

[Tor Bug Tracker & Wiki]

#27092: Torbirdy Disabled Still Needs Tor to Fetch Emails in Thunderbird 60+
---+---
 Reporter:  Luigi-B|  Owner:  sukhbir
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/TorBirdy  |Version:  Tor: unspecified
 Severity:  Normal |   Keywords:  Torbirdy, Thunderbird
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+---
 Just installed Thunderbird 60.0b10 and re-installed Torbirdy. After
 disabling it and shutting down Tor browser (OSX) I noticed that TB was not
 fetching any emails. Verified that Torbirdy was in fact disabled in add-
 ons. When I re-started Tor browser and tried again, it then fetched emails
 as normal. Restarted all applications and Mac, but problem persists.

--
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] #24629 [Core Tor/Tor]: Activate osx builds on travis, at low priority

[Tor Bug Tracker & Wiki]

#24629: Activate osx builds on travis, at low priority
-+-
 Reporter:  teor |  Owner:  teor
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:   | Points:  0.5
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by Hello71):

 Replying to [comment:29 catalyst]:

 (I think these comments should go in #26038, but I'm responding to them
 here because you made them here.)

 > Please explicitly delete the `CARGO_HOME` settings from
 src/rust/tor_rust/include.am and src/test/test_rust.sh instead of merging
 the changes from #26038.  There are other changes in #26038 that I think
 we don't want, like:
 > * deleting the `registry` setting in `[source.crates-io]` in
 src/rust/.cargo/config.in; I'm not sure whether this breaks anything, but
 I'd rather play it safe and leave it there until we know why we should
 delete it.

 I believe cargo vendor used to print this line a long time ago, and now it
 has been the default for some time, so they stopped printing it. I could
 be remembering wrong though.

 > * warning if `CARGO_HOME` is set; I'm not sure the added complexity is
 worth it, especially given that the checks are added in at least four
 places.

 This is not correct. My patch only checks if CARGO_HOME is set once. It is
 supposed to check separately if CARGO_HOME is a relative path at use time,
 on the basis that the user may have changed their CARGO_HOME since they
 used configure. However, it does this wrong, since it should actually
 error instead of just warn, and also there is more than one place that
 CARGO_HOME is used. I think I do agree that checking for relative path can
 be done a single time in configure with AC_ARG_VAR though.

 > * explicit setting of `target-dir` in `[build]` in
 src/rust/.cargo/config.in; this seems redundant with the explicit setting
 of `CARGO_TARGET_DIR` in various cargo invocations.
 >
 > We could use `target-dir` in the cargo config instead of explicitly
 setting `CARGO_TARGET_DIR` for each cargo invocation, but in that case we
 should make a comment that it assumes that cargo is always invoked from a
 specific directory (which it should be after this change set).

 This is also not correct, although it is my fault for writing a poor
 comment. Paths in cargo configuration are interpreted relative to the
 parent of the .cargo directory, so as long as the correct cargo config is
 read, the target will always be set to the same place. Therefore,
 "./target" is equivalent to writing "@abs_top_builddir@/src/rust/target".
 Whether it is read or not, however, is unrelated to CARGO_TARGET_DIR, but
 in fact the CARGO_HOME. I assume however that if you can set CARGO_HOME
 correctly then you can also set the current directory correctly.

--
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] #27053 [Core Tor/Stem]: Check controller's event error handling

[Tor Bug Tracker & Wiki]

#27053: Check controller's event error handling
---+
 Reporter:  atagar |  Owner:  atagar
 Type:  defect | Status:  new
 Priority:  Very High  |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Major  | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+

Comment (by atagar):

 Hi Mike, sorry for the delay. While looking into this I spotted another
 oversight I had to correct first (in particular, ControlMessage
 equality/hashing wasn't yet implemented). Pushed tests that repro the
 issues mentioned above...

 https://gitweb.torproject.org/stem.git/commit/?id=b557d09

 I'll push fixes for these in the next few days.

--
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] #27066 [Core Tor/Tor]: circuit_build_times_update_alpha(): Bug: Could not determine largest build time

[Tor Bug Tracker & Wiki]

#27066: circuit_build_times_update_alpha(): Bug: Could not determine largest 
build
time
---+---
 Reporter:  cstest |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.5.x-final
Component:  Core Tor/Tor   |Version:  Tor: 0.3.3.9
 Severity:  Normal | Resolution:
 Keywords:  034-backport 033-backport  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by mikeperry):

 Ok based on the above, my suspicions are accumulating around some kind of
 interaction between timed out circuits and the circuit failure limit,
 which would explain why your services stop working. I do not know where
 this CBT error is coming from though. #27049 is one way that it can
 happen, but if there are no loglines related to that, then something else
 must be happening.

 I also do not know why this limit is only affecting v3 services. Perhaps
 there is some v3-specific code that counts failures differently than v2.

 Are you able to run branches with additional logging and/or potential
 fixes? I have been unable to reproduce this on a v3-only service that is
 under continual use via synthetic wget activity.

--
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] #24629 [Core Tor/Tor]: Activate osx builds on travis, at low priority

[Tor Bug Tracker & Wiki]

#24629: Activate osx builds on travis, at low priority
-+-
 Reporter:  teor |  Owner:  teor
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:   | Points:  0.5
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by catalyst):

 Thanks!  I'm commenting only on master, because I haven't looked at the
 others yet.

 This mostly looks good.

 `mkdir` in `before_install` should create
 `$TRAVIS_BUILD_DIR/src/rust/target`, not `$TRAVIS_BUILD_DIR/target`.

 Please explicitly delete the `CARGO_HOME` settings from
 src/rust/tor_rust/include.am and src/test/test_rust.sh instead of merging
 the changes from #26038.  There are other changes in #26038 that I think
 we don't want, like:
 * deleting the `registry` setting in `[source.crates-io]` in
 src/rust/.cargo/config.in; I'm not sure whether this breaks anything, but
 I'd rather play it safe and leave it there until we know why we should
 delete it.
 * warning if `CARGO_HOME` is set; I'm not sure the added complexity is
 worth it, especially given that the checks are added in at least four
 places.
 * explicit setting of `target-dir` in `[build]` in
 src/rust/.cargo/config.in; this seems redundant with the explicit setting
 of `CARGO_TARGET_DIR` in various cargo invocations.

 We could use `target-dir` in the cargo config instead of explicitly
 setting `CARGO_TARGET_DIR` for each cargo invocation, but in that case we
 should make a comment that it assumes that cargo is always invoked from a
 specific directory (which it should be after this change set).

--
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] #26038 [Core Tor/Tor]: Misc Rust/Cargo improvements (incl. use global cargo cache)

[Tor Bug Tracker & Wiki]

#26038: Misc Rust/Cargo improvements (incl. use global cargo cache)
+--
 Reporter:  Hello71 |  Owner:  Hello71
 Type:  enhancement | Status:
|  needs_information
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  rust, 035-removed-20180711  |  Actual Points:
Parent ID:  #24629  | Points:
 Reviewer:  isis|Sponsor:
+--

Comment (by Hello71):

 1. remove source.crates-io.registry = 'https://github.com/rust-lang/crates
 .io-index'. I think this is obsolete.

 2. set target-dir = './target' instead of CARGO_TARGET_DIR, so we don't
 have to set that with cargo build and cargo test

 3. stop setting CARGO_HOME. warn if it is set for backwards compat, and
 error if it is a relative path. now that I think about it, maybe
 CARGO_HOME should be AC_ARG_VAR, but I don't think it really matters.

--
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] #26038 [Core Tor/Tor]: Misc Rust/Cargo improvements (incl. use global cargo cache)

[Tor Bug Tracker & Wiki]

#26038: Misc Rust/Cargo improvements (incl. use global cargo cache)
+--
 Reporter:  Hello71 |  Owner:  Hello71
 Type:  enhancement | Status:
|  needs_information
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  rust, 035-removed-20180711  |  Actual Points:
Parent ID:  #24629  | Points:
 Reviewer:  isis|Sponsor:
+--
Changes (by chelseakomlo):

 * status:  needs_review => needs_information


Comment:

 Please provide a list of the intended changes that this patch introduces,
 if there are more than changing to use a global Cargo cache.

--
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] #26038 [Core Tor/Tor]: Misc Rust/Cargo improvements (incl. use global cargo cache)

[Tor Bug Tracker & Wiki]

#26038: Misc Rust/Cargo improvements (incl. use global cargo cache)
+--
 Reporter:  Hello71 |  Owner:  Hello71
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  rust, 035-removed-20180711  |  Actual Points:
Parent ID:  #24629  | Points:
 Reviewer:  isis|Sponsor:
+--

Comment (by chelseakomlo):

 Can this ticket be closed if the fixes will be in #24629? Otherwise it
 would be helpful to have a clear summary of the additional intended
 changes and improvements for reviewing.

--
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] #26038 [Core Tor/Tor]: Misc Rust/Cargo improvements (incl. use global cargo cache)

[Tor Bug Tracker & Wiki]

#26038: Misc Rust/Cargo improvements (incl. use global cargo cache)
+--
 Reporter:  Hello71 |  Owner:  Hello71
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  rust, 035-removed-20180711  |  Actual Points:
Parent ID:  #24629  | Points:
 Reviewer:  isis|Sponsor:
+--
Changes (by chelseakomlo):

 * cc: chelseakomlo (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] #26950 [Metrics/Website]: Remove "Fraction of relays reporting onion-service statistics" graph after August 15

[Tor Bug Tracker & Wiki]

#26950: Remove "Fraction of relays reporting onion-service statistics" graph 
after
August 15
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  merge_ready => needs_review


Comment:

 Please review [https://gitweb.torproject.org/karsten/metrics-
 web.git/commit/?h=task-26998-26950&id=d3a572a0a04dd51ea9228337c8bf8d3c1744e73c
 commit d3a572a in my task-26998-26950 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] #26998 [Metrics/Website]: Make suggested changes to per-graph CSV files and deploy them after August 15

[Tor Bug Tracker & Wiki]

#26998: Make suggested changes to per-graph CSV files and deploy them after 
August
15
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  accepted => needs_review


Comment:

 Please review [https://gitweb.torproject.org/karsten/metrics-
 web.git/commit/?h=task-26998-26950&id=895a1113beb276a5a6526c2edfbc01769b803771
 commit 895a111 in my task-26998-26950 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] #27066 [Core Tor/Tor]: circuit_build_times_update_alpha(): Bug: Could not determine largest build time

[Tor Bug Tracker & Wiki]

#27066: circuit_build_times_update_alpha(): Bug: Could not determine largest 
build
time
---+---
 Reporter:  cstest |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.5.x-final
Component:  Core Tor/Tor   |Version:  Tor: 0.3.3.9
 Severity:  Normal | Resolution:
 Keywords:  034-backport 033-backport  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by cstest):

 Server was using v2 domains and because some attacker on tor level might
 be doing some tor wide non effective DDoS attack or trying to deanonymize
 users, during last couple of months I am finding lots of below log lines:

 {{{
 Hidden service . exceeded launch limit with 10 intro points in
 the last 11 seconds. Intro circuit launches are limited to 10 per 300
 seconds. [461 similar message(s) suppressed in last 300 seconds]
 }}}

 That's why I have tried v3 services because v3 domains are not listed
 publicly.

 In my torrc there are no ExcludeNodes or anything else that could have
 impact on path. Anyway, v2 domains were and are working fine. No
 configuration changes, just removed "HiddenServiceVersion 3" when
 generating new domains.

 Almost all those weird log lines started to appear after CBT warning,
 except above mentioned "exceeded launch limit with 10 intro points" and
 "Your network connection speed appears to have changed." which is related
 to probable v2 attack as I have said above.

 This issue happens only when v3 domains are activated, together with
 couple of v2 domains. There are no problems when only v2 domains are
 active. And it does not happen immediately but several hours after
 activating v3 domains. To repeat this it is not required only to generate
 100 v3 domains but users must keep trying to access them.

 As you can see in
 {{{
 Aug 07 00:02:15.000 [notice] Our hidden services received 41808 v2 and 18
 v3 INTRODUCE2 cells and attempted to launch 42259 rendezvous circuits.
 
 Aug 07 06:02:15.000 [notice] Our hidden services received 42361 v2 and
 1813 v3 INTRODUCE2 cells and attempted to launch 45315 rendezvous
 circuits.
 
 Aug 07 12:02:15.000 [notice] Our hidden services received 42549 v2 and
 4072 v3 INTRODUCE2 cells and attempted to launch 48084 rendezvous
 circuits.
 
 Aug 07 18:02:16.000 [notice] Our hidden services received 43651 v2 and
 13413 v3 INTRODUCE2 cells and attempted to launch 60870 rendezvous
 circuits.
 }}}

 number of v2 introduce cells decreased because during that period I have
 had only couple of v2 domains and number of v3 introduce cells increased
 even tho not a single user could connect through v3 domain after CBT
 issue. CBT issue appeared on "Aug 07 04:45:49.000".

 System clock was and is correct.

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

Re: [tor-bugs] #24629 [Core Tor/Tor]: Activate osx builds on travis, at low priority

[Tor Bug Tracker & Wiki]

#24629: Activate osx builds on travis, at low priority
-+-
 Reporter:  teor |  Owner:  teor
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:   | Points:  0.5
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => needs_revision


Comment:

 Ok, so this was quite challenging to backport, because there were a lot of
 little bugs. But I think it is worth it to have working CI.

 Here are the branches I created today:
 * travis-osx-029, which backports:
   * the travis config rewrite
   * macOS support
 * fix a bug where missing macOS dependencies weren't being installed
 (#27090, but backported as a precaution)
   * ccache (#26952)
   * asciidoc (#27087)
   * the distcheck configure options fix (#27088) for consistency
   * It passes Travis:
 * https://travis-ci.org/teor2345/tor/builds/414029807
   * A full matrix is running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414069609
 * travis-osx-032 backports:
   * the lzma and zstd (macOS only) install from 0.3.1
   * make zstd actually work on macOS (#27090)
   * rust cargo online mode
   * rust cargo offline mode
   * It's running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414067564
   * A full matrix is running in Travis:
 * https://travis-ci.org/teor2345/tor/builds/414071688

 I'm going to leave Travis to run overnight, and hopefully it's all
 successful in the morning. I expect 0.3.3 to take a little while, and then
 0.3.4 and 0.3.5 should be trivial.

--
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] #26961 [Applications/Tor Browser]: implement new user onboarding

[Tor Bug Tracker & Wiki]

#26961: implement new user onboarding
--+--
 Reporter:  mcs   |  Owner:  mcs
 Type:  defect| Status:  needs_review
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201808R |  Actual Points:
Parent ID:  #25695| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mcs):

 Here are a few notes for the UX Team / Antonela:
 * The onboarding requires a window that is at least 960 pixels wide;
 otherwise, it is not shown. Hopefully most of our users have a display
 that is wide enough.
 * We need a "watermark" icon (64x64 PNG). This is shown on about:tor after
 the user has completed all of the onboarding tasks. For now, Kathy and I
 put in a grayscale version of the Tor Browser globe icon (we know that a
 new browser icon is coming, so we didn't spend much time on this). The
 image that Firefox uses is here: https://dxr.mozilla.org/mozilla-
 esr60/source/browser/extensions/onboarding/content/img/watermark.svg
 * Firefox has a small icon for each of the onboarding tasks, shown to the
 left of the task name (see a screenshot here) https://techdows.com/wp-
 content/uploads/2017/06/Firefox-Photon-onboarding-tour-min.png). Your
 design has no icons, so we omitted them (but they could be added).
 * The Firefox onboarding code adds a checkmark to the left of the
 completed task's titles. Kathy and I made a PNG that is 15x15 pixels from
 Mozilla's image: https://dxr.mozilla.org/mozilla-
 esr60/source/browser/extensions/onboarding/content/img/icons_tour-
 complete.svg
 * We disabled onboarding notifications since we do not have a
 specification for the text (if enabled, these would appear at the bottom
 of the about:tor window to prompt users to look at onboarding tasks). Do
 we want notifications in a future version of this feature? We would need a
 notification title and message for each of the onboarding tasks. The
 English strings used by Firefox ESR60 are in the following file (search
 for `onboarding.notification.onboarding-tour`): https://dxr.mozilla.org
 /mozilla-esr60/source/browser/extensions/onboarding/locales/en-
 US/onboarding.properties There is also a button for each notification but
 in all cases Firefox ESR60 uses "Learn More" as the label (from
 `onboarding.button.learnMore` in that same properties 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] #27045 [Applications/Tor Browser]: Add option for firefox incremental builds

[Tor Bug Tracker & Wiki]

#27045: Add option for firefox incremental builds
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201808R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by boklm):

 * status:  new => needs_review
 * keywords:  tbb-rbm => tbb-rbm, TorBrowserTeam201808R


Comment:

 Branch `bug_27045_v3` is adding some information about this option in
 `README.HACKING` and `README.MAKEFILE`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_27045_v3&id=c4ef2e932320ca961a0bab8b454dae9c631e25a8

--
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] #27089 [Core Tor/Tor]: Update to August GeoIP2 database

[Tor Bug Tracker & Wiki]

#27089: Update to August GeoIP2 database
-+-
 Reporter:  karsten  |  Owner:  (none)
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client tor-relay 029-backport|  implemented
  032-backport 033-backport 034-must 035-must|  Actual Points:
  034-backport   |
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by nickm):

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


Comment:

 Merged to 0.2.9 and forward.

--
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] #27008 [Internal Services/Service - deb.tpo]: Remove ooniprobe and dependencies

[Tor Bug Tracker & Wiki]

#27008: Remove ooniprobe and dependencies
-+-
 Reporter:  irl  |  Owner:  irl
 Type:  task | Status:
 |  reopened
 Priority:  Very High|  Milestone:
Component:  Internal Services/Service - deb.tpo  |Version:
 Severity:  Critical | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hellais):

 * priority:  Medium => 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] #27008 [Internal Services/Service - deb.tpo]: Remove ooniprobe and dependencies

[Tor Bug Tracker & Wiki]

#27008: Remove ooniprobe and dependencies
-+-
 Reporter:  irl  |  Owner:  irl
 Type:  task | Status:
 |  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - deb.tpo  |Version:
 Severity:  Critical | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by hellais):

 * status:  closed => reopened
 * resolution:  fixed =>
 * severity:  Normal => Critical


Comment:

 @irl I thought we had agreed to not make any changes to the packages (or
 removing them until) we had a clear path forward.

 We currently advertise deb.torproject.org as the preferred installation
 method for OONI Probe on linux system to use the deb.torproject.org
 repository.

 Can you please revert this change ASAP.

 Before removing the packages we need to:

 1. Come up with a path forward for the new OONI package as discussed above
 2. Implement a new package for it
 3. Update the docs on the OONI website mentioning the new installation
 method
 4. Write instructions on how users can migrate to the new package

--
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] #27091 [Core Tor/Tor]: Configure jenkins with CARGO_HOME in a writeable directory

[Tor Bug Tracker & Wiki]

#27091: Configure jenkins with CARGO_HOME in a writeable directory
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  032-backport, 033-backport,  |  Actual Points:
  034-backport   |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:
 not-just-linux, tor-ci, teor-was-assigned, 034-triage-20180328,
 034-removed-20180328, 034-backport, 035-removed-20180711, fast-fix
 => 032-backport, 033-backport, 034-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

[tor-bugs] #27091 [Core Tor/Tor]: Configure jenkins with CARGO_HOME in a writeable directory

[Tor Bug Tracker & Wiki]

#27091: Configure jenkins with CARGO_HOME in a writeable directory
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  not-just-linux, tor-ci, teor-was-
 Severity:  Normal   |  assigned, 034-triage-20180328,
 |  034-removed-20180328, 034-backport,
 |  035-removed-20180711, fast-fix
Actual Points:   |  Parent ID:  #24629
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Or develop a workaround in the tor build scripts.

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

Re: [tor-bugs] #27090 [Core Tor/Tor]: Travis: enable lzma and zstd in configure, if available

[Tor Bug Tracker & Wiki]

#27090: Travis: enable lzma and zstd in configure, if available
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.5-alpha
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  assigned => needs_review
 * version:   => Tor: 0.3.1.5-alpha


Comment:

 It turns out that we were never building with zstd on macOS, because the
 package config path wasn't set.

 The fix will be in my #24629 branches.

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

[tor-bugs] #27090 [Core Tor/Tor]: Travis: enable lzma and zstd in configure, if available

[Tor Bug Tracker & Wiki]

#27090: Travis: enable lzma and zstd in configure, if available
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:  assigned
 Priority:  Medium   |  Milestone:  Tor: 0.3.5.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  not-just-linux, tor-ci, teor-was-
 Severity:  Normal   |  assigned, 034-triage-20180328,
 |  034-removed-20180328, 034-backport,
 |  035-removed-20180711, fast-fix
Actual Points:   |  Parent ID:  #24629
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Otherwise, we can break lzma or zstd detection without knowing 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] #26848 [Core Tor/sbws]: Create Debian package for sbws

[Tor Bug Tracker & Wiki]

#26848: Create Debian package for sbws
---+-
 Reporter:  juga   |  Owner:  juga
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  sbws 1.0 (MVP must)
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #25925 | Points:
 Reviewer: |Sponsor:
---+-

Comment (by juga):

 Updates:

 After the comments about `tor-` namespace by micah here, ulrike in the
 ITP, weasel in #tor-project channel, and irl in the ITP and here:
 1. we are not going to use `tor-` for the Debian package
 2. the Debian package description has been updated to clarify the scanner
 is for Tor and intented to be run be run only by dirauths or researchers
 in test networks.

 Also, a new policy page has been created regarding deb.tpo [0], and it's
 required to have a package in Debian archive to have it also in deb.tpo.
 irl is already reviewing the package, and would help to get it into Debian
 archive.

 Thanks all of you for your comments and suggestions.

 [0]
 
https://trac.torproject.org/projects/tor/wiki/org/operations/Infrastructure/deb.torproject.org

--
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] #27087 [Core Tor/Tor]: Run a single asciidoc build in Travis

[Tor Bug Tracker & Wiki]

#27087: Run a single asciidoc build in Travis
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  assigned => needs_review


Comment:

 This feature will be in my #24629 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] #26998 [Metrics/Website]: Make suggested changes to per-graph CSV files and deploy them after August 15

[Tor Bug Tracker & Wiki]

#26998: Make suggested changes to per-graph CSV files and deploy them after 
August
15
-+--
 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:  assigned => accepted


Comment:

 Grabbing.

--
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] #27089 [Core Tor/Tor]: Update to August GeoIP2 database

[Tor Bug Tracker & Wiki]

#27089: Update to August GeoIP2 database
-+-
 Reporter:  karsten  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client tor-relay 029-backport|  Actual Points:
  032-backport 033-backport 034-must 035-must|
  034-backport   |
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by teor):

 * keywords:  tor-client tor-relay 029-backport 032-backport 033-backport
 034-must =>
 tor-client tor-relay 029-backport 032-backport 033-backport 034-must
 035-must 034-backport
 * reviewer:   => teor
 * status:  needs_review => merge_ready
 * milestone:  Tor: 0.2.9.x-final => Tor: 0.3.5.x-final


Comment:

 It looks ok to me!

--
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] #27089 [Core Tor/Tor]: Update to August GeoIP2 database

[Tor Bug Tracker & Wiki]

#27089: Update to August GeoIP2 database
-+-
 Reporter:  karsten  |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client tor-relay 029-backport|  Actual Points:
  032-backport 033-backport 034-must |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by karsten):

 * status:  new => needs_review


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

[tor-bugs] #27089 [Core Tor/Tor]: Update to August GeoIP2 database

[Tor Bug Tracker & Wiki]

#27089: Update to August GeoIP2 database
-+-
 Reporter:  karsten  |  Owner:  (none)
 Type:   | Status:  new
  enhancement|
 Priority:  Medium   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core |Version:
  Tor/Tor|   Keywords:  tor-client tor-relay 029-backport
 Severity:  Normal   |  032-backport 033-backport 034-must
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 ​[https://gitweb.torproject.org/karsten/tor.git/log/?h=geoip-2018-08-07 My
 geoip-2018-08-07 branch] contains the updated `geoip` and `geoip6` files
 with IPv4 and IPv6 ranges and is supposed to be merged into maint-0.2.9
 and other branches that are still maintained.

--
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] #26038 [Core Tor/Tor]: Misc Rust/Cargo improvements (incl. use global cargo cache)

[Tor Bug Tracker & Wiki]

#26038: Misc Rust/Cargo improvements (incl. use global cargo cache)
+--
 Reporter:  Hello71 |  Owner:  Hello71
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  rust, 035-removed-20180711  |  Actual Points:
Parent ID:  #24629  | Points:
 Reviewer:  isis|Sponsor:
+--
Changes (by teor):

 * status:  needs_information => needs_review


Comment:

 These fixes will be in my #24629 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] #26497 [Core Tor/Tor]: set CARGO_HOME correctly or stop using it

[Tor Bug Tracker & Wiki]

#26497: set CARGO_HOME correctly or stop using it
-+-
 Reporter:  catalyst |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  rust, tor-ci, 035-removed-20180711,  |  Actual Points:
  035-roadmap-proposed   |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  new => needs_review


Comment:

 These fixes will be in my #24629 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] #27088 [Core Tor/Tor]: Pass MODULES_OPTIONS in DISTCHECK_CONFIGURE_FLAGS

[Tor Bug Tracker & Wiki]

#27088: Pass MODULES_OPTIONS in DISTCHECK_CONFIGURE_FLAGS
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.4.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  not-just-linux, tor-ci, teor-was-|  Actual Points:
  assigned, 034-triage-20180328, |
  034-removed-20180328, 034-backport,|
  035-removed-20180711, fast-fix |
Parent ID:  #24629   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * status:  assigned => needs_review
 * version:   => Tor: 0.3.4.1-alpha


Comment:

 This fix will be in my #24629 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