Re: [tor-bugs] #22798 [Core Tor/Tor]: Windows relay is several times slower than Linux relay

[Tor Bug Tracker & Wiki]

#22798: Windows relay is several times slower than Linux relay
---+---
 Reporter:  Vort   |  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Core Tor/Tor   |Version:  Tor: 0.2.9.11
 Severity:  Normal | Resolution:
 Keywords:  tor-relay performance windows  |  Actual Points:
Parent ID: | Points:  5
 Reviewer: |Sponsor:
---+---

Comment (by cypherpunks):

 Enabled https://en.wikipedia.org/wiki/Compound_TCP changes anything for
 you?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22798 [Core Tor/Tor]: Windows relay is several times slower than Linux relay

[Tor Bug Tracker & Wiki]

#22798: Windows relay is several times slower than Linux relay
---+---
 Reporter:  Vort   |  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Core Tor/Tor   |Version:  Tor: 0.2.9.11
 Severity:  Normal | Resolution:
 Keywords:  tor-relay performance windows  |  Actual Points:
Parent ID: | Points:  5
 Reviewer: |Sponsor:
---+---

Comment (by Vort):

 > Enabled https://en.wikipedia.org/wiki/Compound_TCP changes anything for
 you?

 No.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20929 [Applications/Tor Browser]: Bump GCC version in our alpha builds

[Tor Bug Tracker & Wiki]

#20929: Bump GCC version in our alpha builds
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-gitian, TorBrowserTeam201707,|  Actual Points:
  GeorgKoppen201707  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-gitian, TorBrowserTeam201701 => tbb-gitian,
 TorBrowserTeam201707, GeorgKoppen201707


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18325 [Applications/Tor Browser]: We should not depend on rebuilding Firefox to get a new Tor Browser version out

[Tor Bug Tracker & Wiki]

#18325: We should not depend on rebuilding Firefox to get a new Tor Browser 
version
out
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 I just hit this again while trying to just bump the tor version in 7.5a2.
 :(

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20848 [Applications/Tor Browser]: Integrate selfrando into 32bit Linux alpha bundles

[Tor Bug Tracker & Wiki]

#20848: Integrate selfrando into 32bit Linux alpha bundles
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-security, TorBrowserTeam201707,  |  Actual Points:
  GeorgKoppen201707  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-security => tbb-security, TorBrowserTeam201707,
 GeorgKoppen201707


Comment:

 It seems we can think about getting this going for the next alpha
 according to the selfrando people, yay!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21551 [Metrics/Metrics website]: Merge Metrics sub sites into main Tor Metrics website

[Tor Bug Tracker & Wiki]

#21551: Merge Metrics sub sites into main Tor Metrics website
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  High |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  new => needs_review


Comment:

 Please review [https://gitweb.torproject.org/karsten/metrics-
 web.git/log/?h=task-21551 branch task-21551 in my metrics-web repository]
 with commits from staging4 rebased to master and
 [https://gitweb.torproject.org/karsten/metrics-db.git/log/?h=task-21551
 branch task-21551 in my collector repository] and
 [https://gitweb.torproject.org/user/karsten/onionoo.git/log/?h=task-21551
 branch task-21551 in my onionoo repository] with index.html pages reduced
 to placeholder pages.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22826 [Core Tor/Tor]: Write a spec for unsanitised bridge descriptor formats

[Tor Bug Tracker & Wiki]

#22826: Write a spec for unsanitised bridge descriptor formats
-+-
 Reporter:  isis |  Owner:  isis
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-docs, tor-bridges, |  Actual Points:
  tor-bridgeauth, tor-directory-protocol |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-

Comment (by karsten):

 isis: Sounds great to me. I also included some thoughts on such a dir-spec
 patch in [https://trac.torproject.org/projects/tor/ticket/22207#comment:15
 this comment on #22207]. Would you want to write the patch, and I do a
 first review before it goes to nickm or whoever else reviews/merges
 torspec patches?

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

Re: [tor-bugs] #22823 [Webpages/Blog]: Edit blog leading image size and alignment

[Tor Bug Tracker & Wiki]

#22823: Edit blog leading image size and alignment
---+
 Reporter:  steph  |  Owner:  hiro
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by hiro):

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


Comment:

 Leading image is now centred.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22827 [Core Tor/Tor]: Formalise CollecTor spec for sanitised bridge descriptors and put in torspec

[Tor Bug Tracker & Wiki]

#22827: Formalise CollecTor spec for sanitised bridge descriptors and put in
torspec
-+-
 Reporter:  isis |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-docs, tor-bridges  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by karsten):

 Agreed on the idea of making that specification more formal.

 The part that I'm not yet sure about is whether that document should live
 in the torspec repository. In theory, it would be useful to have more
 formal specifications for all descriptor types available in CollecTor, but
 I'm not sure if all of them would fit into torspec. Maybe it's better to
 keep the more formal sanitized bridge descriptors specification in a
 metrics repository, because that's where the sanitizing step takes 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] #22207 [Core Tor/Tor]: Add bridge authority fingerprint to sanitized bridge network statuses

[Tor Bug Tracker & Wiki]

#22207: Add bridge authority fingerprint to sanitized bridge network statuses
--+
 Reporter:  karsten   |  Owner:  metrics-
  |  team
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.1.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
  |  implemented
 Keywords:  intro, SponsorM, review-group-20  |  Actual Points:  .5
Parent ID:| Points:  .5
 Reviewer:  isis  |Sponsor:
--+
Changes (by karsten):

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


Comment:

 Thanks, nickm, for merging (and correcting) the patch!

 And thanks, isis, for the CollecTor patch. We're currently moving the
 [https://collector.torproject.org/ CollecTor page] to a
 [https://metrics.torproject.org/collector.html page on Tor Metrics]
 (#21551). I'll apply your patch there once #21551 is merged, which I hope
 will be today or tomorrow.

 Other than that, I think we can continue the documentation parts on #22826
 and #22827 and close this ticket.

 In fact, I'll just go ahead and do that last part. If I overlooked
 something, please somebody re-open. Thanks, all!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22832 [Applications/Tor Browser]: libwebrtc and snowflake are not being built reproducibly (unless you build in the same month)

[Tor Bug Tracker & Wiki]

#22832: libwebrtc and snowflake are not being built reproducibly (unless you 
build
in the same month)
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major |   Keywords:  tbb-gitian
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I already ran into this problem when building 7.0a4 but did not have time
 to investigate it back then: I did only a partial rebuild (not touching
 snowflake as this was not necessary) but boklm did a full build. The
 result was a different `snowflake-client`.

 Now this happened with the build for 7.5a2 again. The diff is:
 {{{
 --- /dev/fd/63  2017-07-06 09:57:34.341983842 +0200
 +++ /dev/fd/62  2017-07-06 09:57:34.341983842 +0200
 @@ -750821,7 +750821,7 @@
  00b74e40: 6e6e 656c 3d25 642c 2025 6c75 2900 7468  nnel=%d, %lu).th
  00b74e50: 6973 203d 3d20 675f 746f 705f 6d61 6e61  is == g_top_mana
  00b74e60: 6765 7200 4368 6563 6b20 6661 696c 6564  ger.Check failed
 -00b74e70: 3a20 6675 6e63 2e20 004a 756e 2030 3420  : func. .Jun 04
 +00b74e70: 3a20 6675 6e63 2e20 004a 756c 2030 3220  : func. .Jul 02
  00b74e80: 3230 3137 2030 353a 3030 3a30 3000 4368  2017 05:00:00.Ch
  00b74e90: 6563 6b20 6661 696c 6564 3a20 6269 6e64  eck failed: bind
  00b74ea0: 5f73 7461 7465 5f2e 2000 2c3c 2a00 4368  _state_. .,<*.Ch
 }}}
 That seems to be a bit weird given the actual build date but boklm had the
 idea it could be the first Sunday of the month/week getting embedded.

 And, indeed, as boklm pointed out `/build/write_build_date_header.py`
 seems to do such a thing.

 I can trace the problem back to `build_time.o` in the libwebrtc .a 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] #22832 [Applications/Tor Browser]: libwebrtc and snowflake are not being built reproducibly (unless you build in the same month)

[Tor Bug Tracker & Wiki]

#22832: libwebrtc and snowflake are not being built reproducibly (unless you 
build
in the same month)
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 boklm pointed out that there is an `override_build_date` argument in
 `base/BUILD.gn` that might be definable in `GN_ARGS`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #16782 [Core Tor/Tor]: systemd unit file is not compatible with the AppArmorProfile= directive

[Tor Bug Tracker & Wiki]

#16782: systemd unit file is not compatible with the AppArmorProfile= directive
-+-
 Reporter:  intrigeri|  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  systemd, apparmor, debian,   |  Actual Points:
  packaging  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by intrigeri):

 Replying to [comment:13 nickm]:
 > Is there any way we can devolve responsibility here to the distributors?
 I don't think we have anybody on the core tor programming team who is
 expert in systemd or apparmor.

 My historical background/perspective: before the tor package in Debian
 shipped any systemd unit file, I've put quite some energy into making the
 upstream unit file good enough for my taste. And then weasel (probably
 with good reasons) forked that unit file into a new one, that's now part
 of the Debian packaging and lives its happy life independently from the
 unit file shipped upstream. As I'm working with Debian systems, this
 implies that I now have no interest anymore in the upstream unit file: I
 would not benefit from any improvements made there unless someone manually
 synchronizes these changes to the Debian version from time to time. So to
 be clear: don't count on me to work on the upstream unit file again,
 sorry!

 If any other distro maintainer ships the upstream unit file _and_ cares
 about AppArmor, then they would be well suited to take care of this
 ticket. If this person doesn't exist, then I suggest we simply give up and
 reject 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

[tor-bugs] #22833 [Metrics/CollecTor]: Either include or retain "fingerprint" line in bridge network statuses with @type bridge-network-status 1.2

[Tor Bug Tracker & Wiki]

#22833: Either include or retain "fingerprint" line in bridge network statuses 
with
@type bridge-network-status 1.2
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 #22207 adds a new "fingerprint" line which we should keep in the
 sanitizing process, or add it for original statuses published prior to
 this patch. I'll attach a branch in a minute.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22833 [Metrics/CollecTor]: Either include or retain "fingerprint" line in bridge network statuses with @type bridge-network-status 1.2

[Tor Bug Tracker & Wiki]

#22833: Either include or retain "fingerprint" line in bridge network statuses 
with
@type bridge-network-status 1.2
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by karsten):

 * status:  new => needs_review


Comment:

 Please review [https://gitweb.torproject.org/karsten/metrics-
 db.git/log/?h=task-22833 my branch task-22833].

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22798 [Core Tor/Tor]: Windows relay is several times slower than Linux relay

[Tor Bug Tracker & Wiki]

#22798: Windows relay is several times slower than Linux relay
---+---
 Reporter:  Vort   |  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Core Tor/Tor   |Version:  Tor: 0.2.9.11
 Severity:  Normal | Resolution:
 Keywords:  tor-relay performance windows  |  Actual Points:
Parent ID: | Points:  5
 Reviewer: |Sponsor:
---+---

Comment (by Vort):

 I have made a test using WANem and 3 virtual machines: Windows 7, Windows
 XP and WANem.
 Connection settings was set to 10 Mbit/s and 150 ms delay.
 With this configuration, Win7->WinXP iperf gives out 3.3 Mbit/s (400
 KiB/s).
 This is worse than theoretical limit of 1.19 MiB/s.
 But far more better than 50 KiB/s, which I was obtaining on real
 configuration.

 If I figure out how to set up completely virtual Tor network, I will be
 able to make additional measurements.
 But, most likely, I will get the same 50 KiB/s with 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] #22428 [Metrics/CollecTor]: add webstats module to collector

[Tor Bug Tracker & Wiki]

#22428: add webstats module to collector
---+---
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by iwakeh):

 Replying to [comment:9 karsten]:
 > First bit of feedback (more may follow): wouldn't it be problematic to
 leave out the hostname of the collecting server in the output path? There
 are several hosts serving the main Tor website, and each of them will
 create a log file for that domain name for a given day.

 Good point!  The hostname is used as directory name on
 webstats.torproject.org, but doesn't seem to be part of current
 shell/python processing, which takes place in a directory containing the
 files to be cleaned (afaict).

 >
 > Note that I don't have access to the current webstats host, but I would
 imagine that not all files are stored in a directory without
 subdirectories. The existing code might reveal something about that, but I
 haven't looked.

 As mentioned above, but it is very easy to simply look for files in
 subfolder, too.

 So all in all, the main question left is how the access logs and the log
 meta data are provided.  So far, meta data seems to be in the log-filename
 and the path (i.e. the hostname).
 Could the logs be 'delivered' as compressed files having meta data in
 their filename, e.g.,
 {{{--access.log-.xz}}}
 This is just an  example any other combination will be fine, important is
 what and how meta-data is communicated.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21551 [Metrics/Metrics website]: Merge Metrics sub sites into main Tor Metrics website

[Tor Bug Tracker & Wiki]

#21551: Merge Metrics sub sites into main Tor Metrics website
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  merge_ready
 Priority:  High |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 Looks fine 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] #17857 [Core Tor/Tor]: Create a consensus param to disable (netflow) padding if RSOS is enabled

[Tor Bug Tracker & Wiki]

#17857: Create a consensus param to disable (netflow) padding if RSOS is enabled
-+-
 Reporter:  teor |  Owner:
 |  mikeperry
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, single-onion, review-|  Actual Points:
  group-20   |
Parent ID:   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

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


Comment:

 Wait. I have a question here before we merge this.

 Why is `channel_do_open_actions()` looking at the consensus param by
 itself but yet we have a dedicated function that updates static value with
 the param values `channelpadding_new_consensus_params()` and then we have
 `channelpadding_decide_to_pad_channel()` that basically do the checks that
 are done in `channel.c`.

 Could `channel_do_open_actions()` just use that decide function which
 would remove duplicated code and make channel ask the "padding subsystem"
 directly instead of taking decision on its own?

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

Re: [tor-bugs] #21759 [Metrics/CollecTor]: Add persistence for torperf/onionperf

[Tor Bug Tracker & Wiki]

#21759: Add persistence for torperf/onionperf
---+--
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by iwakeh):

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


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21880 [Applications/TorBirdy]: Protected E-mail Headers (Enigmail)

[Tor Bug Tracker & Wiki]

#21880: Protected E-mail Headers (Enigmail)
---+-
 Reporter:  cypherpunks|  Owner:  sukhbir
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/TorBirdy  |Version:
 Severity:  Minor  | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by cypherpunks):

 Replying to [comment:4 cypherpunks]:
 > Wrong.
 >
 > If both sides are using enigmail, they will see "Encrypted Message" but
 addon automatically
 > changed to original title. Very useful and secure.
 >
 > Add this to TorBirdy, sukhbir.

 If the recipient uses enigmail he/she's going to see the original title
 (ok, after a second or so), no further addon is needed (even without
 him/her having set the option, if the she/he replies to the sender without
 having the option set the original title gets lost)

 It won't work with sides that just support inline-PGP (like protonmail,
 nothing changes, because the title is put into pgp/mime-part and the
 option has no effect on inline-pgp), i guess it wouldn't work with
 Mailvelope either, etc. put overall most people don't trust js-
 cryptogryphy probably won't use a service that requires their private-key
 to be on thair server anyway.

 Maybe just add an option (pref. menu) to turn it on/off.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22428 [Metrics/CollecTor]: add webstats module to collector

[Tor Bug Tracker & Wiki]

#22428: add webstats module to collector
---+---
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by karsten):

 Hmmm, the metadata question is really a good one. Ideally, we'd include
 metadata in the first lines, but I didn't find anything about comments or
 metadata or ignored lines in the Apache documentation that we could use
 here.

 Putting metadata in paths and file names is something we're just giving up
 in the case of bridge network statuses. Ideally, file contents would be
 self-contained, if that's possible in this case.

 Another option could be to put sanitized web logs into tarballs of their
 own and include a small metadata file. This might have other downsides,
 though.

 Maybe there are other ways?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22428 [Metrics/CollecTor]: add webstats module to collector

[Tor Bug Tracker & Wiki]

#22428: add webstats module to collector
---+---
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by iwakeh):

 Replying to [comment:11 karsten]:
 > Hmmm, the metadata question is really a good one. Ideally, we'd include
 metadata in the first lines, but I didn't find anything about comments or
 metadata or ignored lines in the Apache documentation that we could use
 here.
 >
 > Putting metadata in paths and file names is something we're just giving
 up in the case of bridge network statuses. Ideally, file contents would be
 self-contained, if that's possible in this case.
 >
 > Another option could be to put sanitized web logs into tarballs of their
 own and include a small metadata file. This might have other downsides,
 though.
 >
 > Maybe there are other ways?


 The output side is something we can build and your suggestion here is one
 solution.
 The open question is how the 'real' access logs and the log meta data are
 provided to CollecTor?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20488 [Core Tor/Tor]: Nickname registration message is confusing

[Tor Bug Tracker & Wiki]

#20488: Nickname registration message is confusing
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  easy, tor-client log-message  |  Actual Points:  0.1
Parent ID:  #12898| Points:  0.2
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 IIUC "a going concern" is an idiom, but I guess it's not well-known
 enough.

 Fixup commit pushed for both issues, including the third "server" :)

 Squashed as `bug20488_029_squashed`, and merged to 0.3.2.  Not
 backporting.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22762 [Core Tor/Tor]: Revise coding standards expectation for tests to be run before review

[Tor Bug Tracker & Wiki]

#22762: Revise coding standards expectation for tests to be run before review
---+
 Reporter:  chelseakomlo   |  Owner:  chelseakomlo
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor   |Version:  Tor: unspecified
 Severity:  Normal | Resolution:
 Keywords:  documentation  |  Actual Points:
Parent ID: | Points:
 Reviewer:  catalyst   |Sponsor:
---+
Changes (by nickm):

 * status:  merge_ready => assigned


Comment:

 Merged the main commit to master; putting this back in `assigned`.

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

Re: [tor-bugs] #19648 [Core Tor/Tor]: Error in descriptor download log message

[Tor Bug Tracker & Wiki]

#19648: Error in descriptor download log message
--+
 Reporter:  teor  |  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Low   |  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:  fixed
 Keywords:  easy, intro, review-group-20  |  Actual Points:  0
Parent ID:| Points:  0.2
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


Comment:

 Merged to master; thank you!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21551 [Metrics/Metrics website]: Merge Metrics sub sites into main Tor Metrics website

[Tor Bug Tracker & Wiki]

#21551: Merge Metrics sub sites into main Tor Metrics website
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  merge_ready
 Priority:  High |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Thanks for checking! Merged all three branches into their respective
 masters. Keeping this ticket open until all suggested new tickets are
 opened.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22263 [Metrics/CollecTor]: Raise @type torperf version produced by OnionPerf from 1.0 to 1.1

[Tor Bug Tracker & Wiki]

#22263: Raise @type torperf version produced by OnionPerf from 1.0 to 1.1
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by karsten):

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


Comment:

 I just merged and deployed the remaining website changes. Closing.

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

Re: [tor-bugs] #20671 [Core Tor/Tor]: Refactor stream cipher API

[Tor Bug Tracker & Wiki]

#20671: Refactor stream cipher API
-+-
 Reporter:  chelseakomlo |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  refactoring, tor-crypto, api,|  Actual Points:
  technical-debt |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  refactoring, tor-crypto => refactoring, tor-crypto, api,
 technical-debt


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20655 [Core Tor/Chutney]: Run the chutney "mixed" network tests in multiple ways

[Tor Bug Tracker & Wiki]

#20655: Run the chutney "mixed" network tests in multiple ways
-+-
 Reporter:  nickm|  Owner:  teor
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Chutney |Version:
 Severity:  Normal   | Resolution:
 Keywords:  chutney, testing, test-networks, |  Actual Points:
  integration-testing|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => chutney, testing, test-networks, integration-testing


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

Re: [tor-bugs] #20653 [Core Tor/Tor]: Test targets should gracefully handle missing dependencies

[Tor Bug Tracker & Wiki]

#20653: Test targets should gracefully handle missing dependencies
-+-
 Reporter:  chelseakomlo |  Owner:
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  test, convenience, easy, api,|  Actual Points:
  dependencies   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  test => test, convenience, easy, api, dependencies


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20647 [Core Tor/Tor]: Run chutney tests in Jenkins

[Tor Bug Tracker & Wiki]

#20647: Run chutney tests in Jenkins
-+-
 Reporter:  chelseakomlo |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  test, chutney, consistency,  |  Actual Points:
  jenkins, integration-testing, continuous-  |
  integration|
Parent ID:   | Points:
 Reviewer:  weasel   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  test =>
 test, chutney, consistency, jenkins, integration-testing, continuous-
 integration


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22428 [Metrics/CollecTor]: add webstats module to collector

[Tor Bug Tracker & Wiki]

#22428: add webstats module to collector
---+---
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by iwakeh):

 Regarding the output of meta-data:

 Shouldn't applications processing Apache access logs ignore 'funny' lines?
 If yes, we could include meta-data lines, i.e.:
 {{{
 measuring meronense.torproject.org
 measured metrics.torproject.org
 date 20160829
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20617 [Core Tor/Tor]: Write a unit test abstraction for tests that need to be repeated multiple times to prove failure

[Tor Bug Tracker & Wiki]

#20617: Write a unit test abstraction for tests that need to be repeated 
multiple
times to prove failure
--+--
 Reporter:  teor  |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  test, unit-test, backend  |  Actual Points:
Parent ID:| Points:  2
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * keywords:  test => test, unit-test, backend


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20611 [Core Tor/Tor]: Relays should log a message when they return a 503 error to a client

[Tor Bug Tracker & Wiki]

#20611: Relays should log a message when they return a 503 error to a client
--+--
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.9
 Severity:  Normal| Resolution:
 Keywords:  easy, tor-relay, logging  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * keywords:   => easy, tor-relay, logging


Comment:

 Also, this message should be rate-limited using the log_fn_ratelim() API.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20606 [Core Tor/Tor]: Make the test network exponential backoff multiplier configurable

[Tor Bug Tracker & Wiki]

#20606: Make the test network exponential backoff multiplier configurable
-+-
 Reporter:  teor |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  test-network, configuration, torrc,  |  Actual Points:
  chutney|
Parent ID:  #20534   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  triaged-out-20170116 => test-network, configuration, torrc,
 chutney


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20605 [Core Tor/Tor]: Reduce the exponential backoff variance

[Tor Bug Tracker & Wiki]

#20605: Reduce the exponential backoff variance
-+-
 Reporter:  teor |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  backoff, tor-client download-|  Actual Points:
  schedule   |
Parent ID:  #20534   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  triaged-out-20170116 => backoff, tor-client download-schedule


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20601 [Core Tor/Tor]: Clients should reject outdated consensuses as soon as they parse them

[Tor Bug Tracker & Wiki]

#20601: Clients should reject outdated consensuses as soon as they parse them
-+-
 Reporter:  teor |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  easy, tor-client timestamp   |  Actual Points:
  consensus download |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  easy, triaged-out-20170116 => easy, tor-client timestamp
 consensus download


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20594 [Core Tor/Tor]: hs: Make HSDir produce HS statistics for prop224

[Tor Bug Tracker & Wiki]

#20594: hs: Make HSDir produce HS statistics for prop224
-+-
 Reporter:  dgoulet  |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Very High|  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224, tor-spec,   |  Actual Points:
  prop224-extra, statistics, privcount-maybe |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorR-must
-+-
Changes (by nickm):

 * keywords:  tor-hs, prop224, tor-spec, prop224-extra => tor-hs, prop224,
 tor-spec, prop224-extra, statistics, privcount-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] #20606 [Core Tor/Tor]: Make the test network exponential backoff multiplier configurable

[Tor Bug Tracker & Wiki]

#20606: Make the test network exponential backoff multiplier configurable
-+-
 Reporter:  teor |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  test-network, configuration, torrc,  |  Actual Points:
  chutney, backoff, download-schedule|
Parent ID:  #20534   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  test-network, configuration, torrc, chutney =>
 test-network, configuration, torrc, chutney, backoff, download-
 schedule


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20872 [Core Tor/Tor]: option to build non-standard code paths on x86

[Tor Bug Tracker & Wiki]

#20872: option to build non-standard code paths on x86
-+-
 Reporter:  weasel   |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.10
 Severity:  Normal   | Resolution:
 Keywords:  triaged-out-20170116, testing,   |  Actual Points:
  portability, unit-tests, intro |
Parent ID:   | Points:  parent
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  triaged-out-20170116 => triaged-out-20170116, testing,
 portability, unit-tests, intro


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20849 [Core Tor/Tor]: periodic pattern in network connections ofa newly setup relay

[Tor Bug Tracker & Wiki]

#20849: periodic pattern in network connections ofa  newly setup relay
--+
 Reporter:  toralf|  Owner:
 Type:  task  | Status:  needs_information
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.2.9.5-alpha
 Severity:  Minor | Resolution:
 Keywords:  tor-relay needs-analysis  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * keywords:   => tor-relay needs-analysis


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20835 [Core Tor/Tor]: Refactor choose_good_entry_server so it is (almost) never used

[Tor Bug Tracker & Wiki]

#20835: Refactor choose_good_entry_server so it is (almost) never used
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  task | Status:
 |  accepted
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-guard, refactor, technical-debt  |  Actual Points:
Parent ID:  #20822   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-guard, triaged-out-20170116 => tor-guard, refactor,
 technical-debt


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20827 [Core Tor/Tor]: Record guards' ed25519 identities

[Tor Bug Tracker & Wiki]

#20827: Record guards' ed25519 identities
-+-
 Reporter:  nickm|  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-guard, ed25519, technical-debt   |  Actual Points:
  crypto |
Parent ID:  #20822   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-guard, triaged-out-20170116 => tor-guard, ed25519,
 technical-debt crypto


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20825 [Core Tor/Tor]: User-named guard selections

[Tor Bug Tracker & Wiki]

#20825: User-named guard selections
--+--
 Reporter:  nickm |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-guard |  Actual Points:
Parent ID:  #20822| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * type:  defect => enhancement


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20742 [Core Tor/Tor]: prop224: Implement stealth client authorization

[Tor Bug Tracker & Wiki]

#20742: prop224: Implement stealth client authorization
-+-
 Reporter:  asn  |  Owner:  asn
 Type:  enhancement  | Status:
 |  assigned
 Priority:  Very High|  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  prop224, needs-proposal, |  Actual Points:
  prop224-extra, tor-hs, client-authorization|
  sealth-authorization, term-project |
Parent ID:  #20700   | Points:  3
 Reviewer:   |Sponsor:
 |  SponsorR-can
-+-
Changes (by nickm):

 * keywords:  prop224, needs-proposal, prop224-extra, tor-hs =>
 prop224, needs-proposal, prop224-extra, tor-hs, client-authorization
 sealth-authorization, term-project


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20719 [Core Tor/Tor]: prop271 -- make parameters configurable

[Tor Bug Tracker & Wiki]

#20719: prop271 -- make parameters configurable
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  intro tor-client guard torrc |  Actual Points:
  configuration  |
Parent ID:  #20822   | Points:  .5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  triaged-out-20170116 => intro tor-client guard torrc
 configuration


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20699 [Core Tor/Tor]: prop224: Add control port events and commands

[Tor Bug Tracker & Wiki]

#20699: prop224: Add control port events and commands
-+-
 Reporter:  dgoulet  |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Very High|  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224, needs-proposal, |  Actual Points:
  prop224-extra, tor-control |
Parent ID:  #12424   | Points:  6
 Reviewer:   |Sponsor:
 |  SponsorR-must
-+-
Changes (by nickm):

 * keywords:  tor-hs, prop224, needs-proposal, prop224-extra => tor-hs,
 prop224, needs-proposal, prop224-extra, tor-control


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20676 [Core Tor/Tor]: Disposable Exit Nodes

[Tor Bug Tracker & Wiki]

#20676: Disposable Exit Nodes
-+-
 Reporter:  madystar |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  research-program, needs-design tor-  |  Actual Points:
  relay  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => research-program, needs-design tor-relay


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20672 [Core Tor/Tor]: Refactor hashing API

[Tor Bug Tracker & Wiki]

#20672: Refactor hashing API
-+-
 Reporter:  chelseakomlo |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  refactoring, tor-crypto, technical-  |  Actual Points:
  debt api   |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  refactoring, tor-crypto => refactoring, tor-crypto, technical-
 debt api


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22834 [Metrics/CollecTor]: CollecTor sync: what should happen to UnparseableDescriptors?

[Tor Bug Tracker & Wiki]

#22834: CollecTor sync: what should happen to UnparseableDescriptors?
---+--
 Reporter:  iwakeh |  Owner:  metrics-team
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 Let's find out, if a code change is needed or things are fine as they are.

 Current situation when one CollecTor fetches data from another CollecTor:
 Metrics Lib cannot parse the fetched content, provides an object of
 `UnparseableDescriptor`, and CollecTor simply ignores this object as
 unknown (only logs on trace level).

 During normal collecting an unparseable descriptor is stored anyway.

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

Re: [tor-bugs] #22834 [Metrics/CollecTor]: CollecTor sync: what should happen to UnparseableDescriptors?

[Tor Bug Tracker & Wiki]

#22834: CollecTor sync: what should happen to UnparseableDescriptors?
---+---
 Reporter:  iwakeh |  Owner:  metrics-team
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by iwakeh):

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

[tor-bugs] #22835 [Metrics/Onionoo]: Provide schemas for Onionoo protocol and CollecTor files

[Tor Bug Tracker & Wiki]

#22835: Provide schemas for Onionoo protocol and CollecTor files
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Low  |  Milestone:
Component:  Metrics/Onionoo  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 From [https://trac.torproject.org/projects/tor/ticket/21551#comment:3
 comment 3 in #21551]: "In the future we could consider providing a schema
 file on both Onionoo and Collector which metrics-web fetches and uses to
 generate a human-readable specification page."

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20925 [Core Tor/Tor]: Tor should handle DNSSec RR types (DS, DNSKEY, DLV, etc.) as well as MX

[Tor Bug Tracker & Wiki]

#20925: Tor should handle DNSSec RR types (DS, DNSKEY, DLV, etc.) as well as MX
--+--
 Reporter:  paulj |  Owner:
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:  #7829 | Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

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


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

Re: [tor-bugs] #20919 [Core Tor/Tor]: Extract prop271 state-parsing code into a generic thing

[Tor Bug Tracker & Wiki]

#20919: Extract prop271 state-parsing code into a generic thing
+--
 Reporter:  nickm   |  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  torrc configuration technical-debt  |  Actual Points:
Parent ID:  #20822  | Points:  3
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * keywords:   => torrc configuration technical-debt


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20918 [Core Tor/Tor]: Switch onion.c to use TRUNNEL_OPAQUE

[Tor Bug Tracker & Wiki]

#20918: Switch onion.c to use TRUNNEL_OPAQUE
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  technical-debt refactor opaque   |  Actual Points:  .2
  data-hiding trunnel|
Parent ID:  #15054   | Points:  .1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => technical-debt refactor opaque data-hiding trunnel


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20910 [Core Tor/Fallback Scripts]: Make the fallback list automatically adapt to minor changes

[Tor Bug Tracker & Wiki]

#20910: Make the fallback list automatically adapt to minor changes
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * owner:   => teor
 * component:  Core Tor/Tor => Core Tor/Fallback 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

[tor-bugs] #22836 [Metrics/Metrics website]: Parse CollecTor's index.json and provide our own directory listing

[Tor Bug Tracker & Wiki]

#22836: Parse CollecTor's index.json and provide our own directory listing
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 From #21551: "Should we let users browser CollecTor files on the Tor
 Metrics website rather than in Apache-generated directory listings on the
 CollecTor page? My suggestion: I'd say yes, but that can be done in a
 subsequent patch. Also a fun project." -- "Yes, new 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] #20909 [Core Tor/Tor]: Tor 0.2.9.5-alpha still delivers outdated consensuses

[Tor Bug Tracker & Wiki]

#20909: Tor 0.2.9.5-alpha still delivers outdated consensuses
-+-
 Reporter:  teor |  Owner:
 Type:  defect   | Status:
 |  needs_information
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.5-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay needs-analysis maybe-it-   |  Actual Points:
  went-away-when-we-werent-looking   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => tor-relay needs-analysis maybe-it-went-away-when-we-
 werent-looking


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20897 [Core Tor/Fallback Scripts]: Make it easier to check the entire fallback whitelist for errors

[Tor Bug Tracker & Wiki]

#20897: Make it easier to check the entire fallback whitelist for errors
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID: | Points:  0.5
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * owner:   => teor
 * component:  Core Tor/Tor => Core Tor/Fallback 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] #22836 [Metrics/Metrics website]: Parse CollecTor's index.json and provide our own directory listing

[Tor Bug Tracker & Wiki]

#22836: Parse CollecTor's index.json and provide our own directory listing
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 I'd like to grab this one, unless somebody else really wants to do 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] #20887 [Core Tor/Tor]: DIRCACHE_MIN_MEM_MB does not stringify on FreeBSD, we should use %d instead

[Tor Bug Tracker & Wiki]

#20887: DIRCACHE_MIN_MEM_MB does not stringify on FreeBSD, we should use %d 
instead
+--
 Reporter:  teor|  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:  Tor:
|  0.2.8.1-alpha
 Severity:  Normal  | Resolution:
 Keywords:  easy, refactor, logging, tor-relay  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * keywords:  easy, intro, refactor => easy, refactor, logging, tor-relay


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20876 [Core Tor/Fallback Scripts]: Avoid contacting fallback operators who are unlikely to be accepted

[Tor Bug Tracker & Wiki]

#20876: Avoid contacting fallback operators who are unlikely to be accepted
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * owner:   => teor
 * component:  Core Tor/Tor => Core Tor/Fallback 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] #20883 [Core Tor/Fallback Scripts]: Ignore relays without contact info when emailing potential fallback operators

[Tor Bug Tracker & Wiki]

#20883: Ignore relays without contact info when emailing potential fallback
operators
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  defect | Status:  new
 Priority:  Very Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Minor  | Resolution:
 Keywords:  fallback, lorax|  Actual Points:
Parent ID: | Points:  0.2
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * owner:   => teor
 * component:  Core Tor/Tor => Core Tor/Fallback 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] #20874 [Core Tor/Tor]: ReachableAddresses adds an extra reject *:* on every SAVECONF

[Tor Bug Tracker & Wiki]

#20874: ReachableAddresses adds an extra reject *:* on every SAVECONF
-+-
 Reporter:  teor |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, torrc, saveconf, |  Actual Points:
  configuration, annoyance   |
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-client => tor-client, torrc, saveconf, configuration,
 annoyance


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22837 [Metrics/Metrics website]: Describe all protocol changes on the Onionoo page

[Tor Bug Tracker & Wiki]

#22837: Describe all protocol changes on the Onionoo page
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 From #21551: "How do we support the case of different Onionoo hosts
 running different Onionoo protocol versions? We said we'd include
 something like "added in version X" and "removed in version Y" in the
 specification. Sounds totally doable, but maybe in the near future as a
 subsequent patch." -- "Agreed. Let's keep it simple."

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21551 [Metrics/Metrics website]: Merge Metrics sub sites into main Tor Metrics website

[Tor Bug Tracker & Wiki]

#21551: Merge Metrics sub sites into main Tor Metrics website
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  closed
 Priority:  High |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:  implemented
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 Created #22835, #22836, and #22837 for the suggestions above. Closing now.
 Thanks again!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20995 [Core Tor/Tor]: Clean up tickets with incorrect milestones

[Tor Bug Tracker & Wiki]

#20995: Clean up tickets with incorrect milestones
--+--
 Reporter:  cypherpunks   |  Owner:
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  wontfix
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

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


Comment:

 I don't think we're going to do a systematic revision of all the closed
 tickets, though we're trying to do better in the future. Unless somebody
 comes up with an automated way to do so.  To find out when a ticket was
 closed, the changelog and the git history are a better bet.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20986 [Core Tor/Tor]: Gracefully handle build configurations on systems without AsciiDoc

[Tor Bug Tracker & Wiki]

#20986: Gracefully handle build configurations on systems without AsciiDoc
-+-
 Reporter:  cypherpunks  |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  build, asciidoc, resilience, |  Actual Points:
  annoyance, autotools   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => build, asciidoc, resilience, annoyance, autotools
 * points:   => 1


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22834 [Metrics/CollecTor]: CollecTor sync: what should happen to UnparseableDescriptors?

[Tor Bug Tracker & Wiki]

#22834: CollecTor sync: what should happen to UnparseableDescriptors?
---+---
 Reporter:  iwakeh |  Owner:  metrics-team
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by karsten):

 That matches my understanding, too. Do you think we should do something
 differently?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20982 [Core Tor/Tor]: Remove trailing dot from version numbers

[Tor Bug Tracker & Wiki]

#20982: Remove trailing dot from version numbers
--+--
 Reporter:  cypherpunks   |  Owner:
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Trivial   | Resolution:  wontfix
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * status:  reopened => closed
 * 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] #20953 [Core Tor/Tor]: Isolate references to versioning

[Tor Bug Tracker & Wiki]

#20953: Isolate references to versioning
-+-
 Reporter:  chelseakomlo |  Owner:
 |  chelseakomlo
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  refactoring technical-debt protover  |  Actual Points:
  api|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  refactoring => refactoring technical-debt protover api


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20946 [Core Tor/Fallback Scripts]: Make it easier to find contacts for a fallback list

[Tor Bug Tracker & Wiki]

#20946: Make it easier to find contacts for a fallback list
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * owner:   => teor
 * component:  Core Tor/Tor => Core Tor/Fallback 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] #20939 [Core Tor/Fallback Scripts]: Add average for each flag and uptime to the fallback summary

[Tor Bug Tracker & Wiki]

#20939: Add average for each flag and uptime to the fallback summary
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * owner:   => teor
 * component:  Core Tor/Tor => Core Tor/Fallback 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] #20934 [Core Tor/Fallback Scripts]: Use standard python multiset implementation in fallback script

[Tor Bug Tracker & Wiki]

#20934: Use standard python multiset implementation in fallback script
---+--
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: unspecified
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID: | Points:  0.1
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * owner:   => teor
 * component:  Core Tor/Tor => Core Tor/Fallback 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] #20931 [Core Tor/Tor]: [prop271] Generate GUARD controller events

[Tor Bug Tracker & Wiki]

#20931: [prop271] Generate GUARD controller events
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  regression, technical-debt tor-  |  Actual Points:
  controller guards  |
Parent ID:  #20822   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  regression, triaged-out-20170116 => regression, technical-debt
 tor-controller guards


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20930 [Core Tor/Tor]: Use new systemd hardening options

[Tor Bug Tracker & Wiki]

#20930: Use new systemd hardening options
+--
 Reporter:  serafean|  Owner:
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  systemd, packaging  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * keywords:   => systemd, packaging


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22832 [Applications/Tor Browser]: libwebrtc and snowflake are not being built reproducibly (unless you build in the same month)

[Tor Bug Tracker & Wiki]

#22832: libwebrtc and snowflake are not being built reproducibly (unless you 
build
in the same month)
--+--
 Reporter:  gk|  Owner:  dcf
 Type:  defect| Status:  assigned
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * status:  new => assigned
 * owner:  tbb-team => dcf


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21084 [Core Tor/Tor]: sometimes we call circuit has_opened() more than 2 times on client side

[Tor Bug Tracker & Wiki]

#21084: sometimes we call circuit has_opened() more than 2 times on client side
-+-
 Reporter:  s7r  |  Owner:  dgoulet
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs needs-insight needs-analysis  |  Actual Points:
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-hs => tor-hs needs-insight needs-analysis
 * cc: dgoulet (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] #21081 [Core Tor/Tor]: tor --service install -options does not work

[Tor Bug Tracker & Wiki]

#21081: tor --service install -options does not work
---+---
 Reporter:  PekaFat|  Owner:
   |  cypherpunks
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.2.8.11
 Severity:  Normal | Resolution:
 Keywords:  windows ntservice win32 tor-relay  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * keywords:  windows ntservice => windows ntservice win32 tor-relay


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21073 [Core Tor/Tor]: "PredictedPortsRelevanceTime 0" causes stagnant/uncommunicative onion services, stale descriptors

[Tor Bug Tracker & Wiki]

#21073: "PredictedPortsRelevanceTime 0" causes stagnant/uncommunicative onion
services, stale descriptors
-+-
 Reporter:  alecmuffett  |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.7-rc
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs dont-do-that-then |  Actual Points:
  predictedports liveness-detection  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-hs => tor-hs dont-do-that-then predictedports liveness-
 detection


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21044 [Core Tor/Tor]: ORPort self reachability test happens also when it shouldn't

[Tor Bug Tracker & Wiki]

#21044: ORPort self reachability test happens also when it shouldn't
--+
 Reporter:  s7r   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor:
  |  unspecified
Component:  Core Tor/Tor  |Version:  Tor:
  |  0.3.0.1-alpha
 Severity:  Normal| Resolution:
 Keywords:  self-test tor-relay reachability  |  Actual Points:
Parent ID:| Points:  3
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * keywords:  triaged-out-20170308 => self-test tor-relay reachability


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21043 [Core Tor/Tor]: Make ClientUseIPv4 and ClientUseIPv6 equivalent to ReachableAddresses

[Tor Bug Tracker & Wiki]

#21043: Make ClientUseIPv4 and ClientUseIPv6 equivalent to ReachableAddresses
-+-
 Reporter:  teor |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, tor-client reachableaddresses  |  Actual Points:
  torrc configuration|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  ipv6 => ipv6, tor-client reachableaddresses torrc
   configuration


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21023 [Core Tor/Tor]: Replace custom checks with Autoconf macros

[Tor Bug Tracker & Wiki]

#21023: Replace custom checks with Autoconf macros
+--
 Reporter:  cypherpunks |  Owner:
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  autotools build technical-debt  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * keywords:   => autotools build technical-debt


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21020 [Core Tor/Tor]: Refactor dirserv_generate_networkstatus_vote_obj

[Tor Bug Tracker & Wiki]

#21020: Refactor dirserv_generate_networkstatus_vote_obj
-+-
 Reporter:  chelseakomlo |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  refactoring testing, large-function  |  Actual Points:
  technical-debt tor-dirauth |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  refactoring testing => refactoring testing, large-function
 technical-debt tor-dirauth


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21006 [Core Tor/Tor]: Reduce NumDirectoryGuards to 1

[Tor Bug Tracker & Wiki]

#21006: Reduce NumDirectoryGuards to 1
-+-
 Reporter:  nickm|  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  guards, triaged-out-20170116 |  Actual Points:
  client-enumeration tor-client needs-design |
Parent ID:  #20822   | Points:  3
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  guards, triaged-out-20170116 =>
 guards, triaged-out-20170116 client-enumeration tor-client needs-
 design


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21015 [Core Tor/Tor]: Tor hidden service stops working and I must change the domain

[Tor Bug Tracker & Wiki]

#21015: Tor hidden service stops working and I must change the domain
--+--
 Reporter:  jesobreira|  Owner:
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:  tor-hs|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * status:  needs_information => closed
 * resolution:   => user disappeared


Comment:

 Not enough info here to diagnose; no response to query. :(

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21003 [Core Tor/Tor]: extend_info_describe should list IPv6 address (if present)

[Tor Bug Tracker & Wiki]

#21003: extend_info_describe should list IPv6 address (if present)
-+--
 Reporter:  teor |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  easy intro ipv6 logging  |  Actual Points:
Parent ID:   | Points:  0.5
 Reviewer:   |Sponsor:
-+--
Changes (by nickm):

 * keywords:  easy intro ipv6 => easy intro ipv6 logging


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22834 [Metrics/CollecTor]: CollecTor sync: what should happen to UnparseableDescriptors?

[Tor Bug Tracker & Wiki]

#22834: CollecTor sync: what should happen to UnparseableDescriptors?
---+---
 Reporter:  iwakeh |  Owner:  metrics-team
 Type:  enhancement| Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by iwakeh):

 The unpars.desc. could be counted or collected in a different place.  Just
 want to make sure we thought about nor changing anything with the 'new'
 descriptor type (unpars.desc).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21115 [Core Tor/Tor]: Building Tor With Static SNI

[Tor Bug Tracker & Wiki]

#21115: Building Tor With Static SNI
---+---
 Reporter:  mintu.juit@…   |  Owner:
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  easy, intro, torrc, configuration  |  Actual Points:
Parent ID: | Points:  1
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * keywords:  easy, triaged-out-20170308 => easy, intro, torrc,
   configuration


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21148 [Core Tor/Tor]: Restore documentation for the approved-routers file (was: Document the approved-routers file)

[Tor Bug Tracker & Wiki]

#21148: Restore documentation for the approved-routers file
---+---
 Reporter:  ln5|  Owner:
 Type:  enhancement| Status:  new
 Priority:  Very Low   |  Milestone:  Tor:
   |  0.3.2.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  doc tor-dirauth revert regression  |  Actual Points:
Parent ID:  #13059 | Points:  .1
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * keywords:  doc => doc tor-dirauth revert regression
 * points:   => .1
 * milestone:  Tor: unspecified => Tor: 0.3.2.x-final


Comment:

 All that needs to happen here is for the stanza about the approved-routers
 file that was removed in 607724c696a6e1bb10c8a955dac38f0ea947ce34 to go
 back in, and then for the nickname parts of that to be noted as obsolete.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21158 [Core Tor/Tor]: Tor as plain HTTP proxy (without SOCKS)

[Tor Bug Tracker & Wiki]

#21158: Tor as plain HTTP proxy (without SOCKS)
-+-
 Reporter:  Maxt |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  term-project-ideas tor-client HTTP-  |  Actual Points:
  CONNECT|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:   => term-project-ideas tor-client HTTP-CONNECT


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21149 [Core Tor/Tor]: Document what Tor means by "using reasonable defaults"

[Tor Bug Tracker & Wiki]

#21149: Document what Tor means by "using reasonable defaults"
+--
 Reporter:  arma|  Owner:
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-doc tor-client  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by nickm):

 * keywords:   => tor-doc tor-client


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21179 [Core Tor/Tor]: Add a fuzzing harness for the tor OR protocol

[Tor Bug Tracker & Wiki]

#21179: Add a fuzzing harness for the tor OR protocol
-+-
 Reporter:  teor |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  fuzz testing hard term-project-  |  Actual Points:
  ideas  |
Parent ID:   | Points:  5
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  fuzz => fuzz testing hard term-project-ideas


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21237 [Core Tor/Tor]: Support domain isolation for onion connections too?

[Tor Bug Tracker & Wiki]

#21237: Support domain isolation for onion connections too?
---+---
 Reporter:  arma   |  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-client isolation needs-design  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * keywords:   => tor-client isolation needs-design


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21181 [Core Tor/Tor]: Add a fuzzing harness for the tor control protocol

[Tor Bug Tracker & Wiki]

#21181: Add a fuzzing harness for the tor control protocol
-+-
 Reporter:  teor |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  fuzz testing term-project-ideas  |  Actual Points:
Parent ID:   | Points:  3
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  fuzz => fuzz testing term-project-ideas


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21859 [Core Tor/Tor]: prop224: Rendezvous circuit e2e crypto

[Tor Bug Tracker & Wiki]

#21859: prop224: Rendezvous circuit e2e crypto
--+
 Reporter:  dgoulet   |  Owner:  asn
 Type:  enhancement   | Status:
  |  needs_review
 Priority:  Very High |  Milestone:  Tor:
  |  0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-hs, prop224, review-group-19  |  Actual Points:
Parent ID:  #21888| Points:  9
 Reviewer:  nickm |Sponsor:  SponsorR-
  |  must
--+
Changes (by dgoulet):

 * status:  needs_revision => needs_review


Comment:

 Everything has been addressed/commented. Let's go back in needs_review.

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

Re: [tor-bugs] #21253 [Core Tor/Tor]: Add link handshakes to benchmark program

[Tor Bug Tracker & Wiki]

#21253: Add link handshakes to benchmark program
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  task | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  triaged-out-20170124 performance |  Actual Points:  1
  testing link-handshake |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  SponsorU-must
-+-
Changes (by nickm):

 * keywords:  triaged-out-20170124 => triaged-out-20170124 performance
 testing link-handshake


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21281 [Core Tor/Tor]: Allow process poll rate to be customized

[Tor Bug Tracker & Wiki]

#21281: Allow process poll rate to be customized
-+-
 Reporter:  atagar   |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Very Low |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Trivial  | Resolution:
 Keywords:  stem-wants, chutney-wants, easy  |  Actual Points:
  intro torrc configuration  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  stem-wants, chutney-wants => stem-wants, chutney-wants, easy
 intro torrc configuration


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21285 [Core Tor/Tor]: Add tor compilation to disable all non-anonymous services

[Tor Bug Tracker & Wiki]

#21285: Add tor compilation to disable all non-anonymous services
-+-
 Reporter:  teor |  Owner:
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, single-onion maybe-bad-idea  |  Actual Points:
  build modularity   |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  tor-hs, single-onion => tor-hs, single-onion maybe-bad-idea
 build modularity


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