[tor-bugs] #19906 [- Select a component]: "Maximizing Tor Browser" Notification can exist multiple times

[Tor Bug Tracker & Wiki]

#19906: "Maximizing Tor Browser" Notification can exist multiple times
-+-
 Reporter:  oldmanjohnson|  Owner:
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:
Component:  - Select a   |Version:
  component  |   Keywords:  maximizing, message,
 Severity:  Trivial  |  overlay, multiple
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 The following Message that overlays the top part of the browser when
 maximizing it, can open itself multiple times.
 See i.imgur.com/hQfxjO1.png

 Steps to reproduce:
 1. Open Tor (6.0.3)
 2. Maximize (message shows up)
 3. Revert to other size then maximum / minimum
 4. Repeat 2,3

 Multiple messages now lie on top of each other which have to be closed
 individually.

 Expected behavior:
 Only one of those messages can be open at one time.

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

Re: [tor-bugs] #19387 [Internal Services/Tor Sysadmin Team]: upgrade troodi [trac] to jessie

[Tor Bug Tracker & Wiki]

#19387: upgrade troodi [trac] to jessie
-+-
 Reporter:  weasel   |  Owner:  tpa
 Type:  defect   | Status:
 |  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by weasel):

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


Comment:

 Not yet finished:

 {{{
 WARNING: 1 obs/loc, 3 updates, 447 ok, 1 obs/loc(ignored)
 1 local or obsolete packages: trac-batchmodify
 }}}

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608R,   |  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 #19900 is a 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] #19900 [Applications/Tor Browser]: Up-to-date Tor Browser asks me to update Firefox

[Tor Bug Tracker & Wiki]

#19900: Up-to-date Tor Browser asks me to update Firefox
--+---
 Reporter:  erchewin  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

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


Comment:

 This is fixed on Mozilla's side and a duplicate of #19890. We'll release a
 new Tor Browser stable shortly to address the remaining bits on our side.
 See: comment:13:ticket:19890 for a workaround that avoid installing a new
 Tor Browser or waiting until the next extensions update ping (which should
 get rid of the cause as well).

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by dcf):

 And then of course we'll have to get a certificate and put a domain name
 for the bridge in the proxy rather than an IP address.

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

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

[Tor Bug Tracker & Wiki]

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

Comment (by dcf):

 Replying to [comment:1 serene]:
 > Been updating a few things on my end -- when I visit
 keroserene.net/snowflake with https, snowflake doesn't work due to the
 lack of wss from proxy to server. While it's trivial to set the proxy
 javascript to use wss, we still also need to get the server plugin to
 accept that. How much time would it take to get TLS support on the server
 plugin?

 It's probably not too bad. This is the source file:
 https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/tree/server/server.go

 You can probably copy the `startListenerTLS` and `listenTLS` functions
 from meek-server:
 https://gitweb.torproject.org/pluggable-transports/meek.git/tree/meek-
 server/meek-server.go?id=edc089e5af06eebf6a5b1d84d278082746a22c48#n306

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

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

[Tor Bug Tracker & Wiki]

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

 * cc: serene (added)


Comment:

 Been updating a few things on my end -- when I visit
 keroserene.net/snowflake with https, snowflake doesn't work due to the
 lack of wss from proxy to server. While it's trivial to set the proxy
 javascript to use wss, we still also need to get the server plugin to
 accept that. How much time would it take to get TLS support on the server
 plugin?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19905 [Core Tor/Tor]: make-test-network-all has never detected IPv6 on linux

[Tor Bug Tracker & Wiki]

#19905: make-test-network-all has never detected IPv6 on linux
--+
 Reporter:  teor  |  Owner:  teor
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.0.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.7.3-rc
 Severity:  Normal|   Keywords:  029-proposed
Actual Points:|  Parent ID:
   Points:  0.2   |   Reviewer:
  Sponsor:|
--+
 When I wrote make-test-network-all, I tested IPv6 on OS X and BSD.
 But it's never worked on Linux.

 On BSD and OS X systems, we use:
 `ping6 -q -c 1 -o ::1`

 On Linux systems, we should use:
 `ping6 -q -c 1 -W 1 ::1`

 You'd think we could get away with:
 `ping6 -q -c 1 ::1`
 but BSD / OS X would hang forever on systems where IPv6 packets are
 dropped, and Linux is somewhat ambiguous about what happens in that case.

 Over the long term, implementing checks like this in chutney might be a
 better idea.

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

Re: [tor-bugs] #19904 [Core Tor/Tor]: evutil_secure_rng_add_bytes() not present in openbsd libevent 2

[Tor Bug Tracker & Wiki]

#19904: evutil_secure_rng_add_bytes() not present in openbsd libevent 2
---+---
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201608 openbsd  |  Actual Points:  0
Parent ID: | Points:  0
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * actualpoints:   => 0


Comment:

 This is a bugfix on 0.2.5.4-alpha, but I recommend no backport, since it
 didn't matter still we started requiring libevent 2, and openbsd started
 caring.

 Fixed in e788c577f11ef4

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19904 [Core Tor/Tor]: evutil_secure_rng_add_bytes() not present in openbsd libevent 2

[Tor Bug Tracker & Wiki]

#19904: evutil_secure_rng_add_bytes() not present in openbsd libevent 2
--+---
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  TorCoreTeam201608 openbsd
Actual Points:|  Parent ID:
   Points:  0 |   Reviewer:
  Sponsor:|
--+---
 For decent reasons, OpenBSD removes evutil_secure_rng_add_bytes().  But
 now that Tor requires Libevent 2, Tor should detect this absence and not
 call evutil_secure_rng_add_bytes() if it isn't there.

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

Re: [tor-bugs] #19903 [Core Tor/Tor]: tor_tls_get_by_ssl is declared non-inline, then inline.

[Tor Bug Tracker & Wiki]

#19903: tor_tls_get_by_ssl is declared non-inline, then inline.
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.8.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Minor| Resolution:
 Keywords:  openbsd TorCoreTeam201608|  Actual Points:  0
  028-backport   |
Parent ID:   | Points:  0
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * keywords:  openbsd TorCoreTeam201608 => openbsd TorCoreTeam201608
 028-backport


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

Re: [tor-bugs] #19903 [Core Tor/Tor]: tor_tls_get_by_ssl is declared non-inline, then inline.

[Tor Bug Tracker & Wiki]

#19903: tor_tls_get_by_ssl is declared non-inline, then inline.
---+---
 Reporter:  nickm  |  Owner:  nickm
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:  Tor:
   |  0.2.8.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Minor  | Resolution:
 Keywords:  openbsd TorCoreTeam201608  |  Actual Points:  0
Parent ID: | Points:  0
 Reviewer: |Sponsor:
---+---
Changes (by nickm):

 * status:  accepted => needs_review
 * keywords:   => openbsd TorCoreTeam201608
 * actualpoints:   => 0


Comment:

 Trivial fix in my branch `bug19903_028`. Please 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] #19903 [Core Tor/Tor]: tor_tls_get_by_ssl is declared non-inline, then inline.

[Tor Bug Tracker & Wiki]

#19903: tor_tls_get_by_ssl is declared non-inline, then inline.
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  0
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * owner:   => nickm
 * status:  new => accepted
 * severity:  Normal => Minor


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19903 [Core Tor/Tor]: tor_tls_get_by_ssl is declared non-inline, then inline.

[Tor Bug Tracker & Wiki]

#19903: tor_tls_get_by_ssl is declared non-inline, then inline.
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:  0 |   Reviewer:
  Sponsor:|
--+
 In tortls.h, we declare tor_tls_by_ssl as non-inline.  But in tortls.c, we
 declare it inline.  This bugs the version of GCC that OpenBSD uses, and
 wasn't our intention.

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

Re: [tor-bugs] #19901 [Core Tor/Tor]: ENABLE_GCC_WARNING is broken on GCC < 4.6

[Tor Bug Tracker & Wiki]

#19901: ENABLE_GCC_WARNING is broken on GCC < 4.6
---+
 Reporter:  nickm  |  Owner:
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  TorCoreTeam201608  |  Actual Points:  0
Parent ID: | Points:  0
 Reviewer: |Sponsor:
---+
Changes (by nickm):

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


Comment:

 Fixed in 60997a00e8e7585e076c750ab37095c0bfc3c773 , I hope

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

Re: [tor-bugs] #19902 [Core Tor/Tor]: Dual-install of libevent 1 and libevent 2 on openbsd confuses our autoconf logic

[Tor Bug Tracker & Wiki]

#19902: Dual-install of libevent 1 and libevent 2 on openbsd confuses our 
autoconf
logic
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  openbsd   |  Actual Points:
Parent ID:| Points:  .2
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => needs_review


Comment:

 I think the problem may be that we demand header files that exist only in
 libevent 2, but we accept libraries that only support libevent 1... until
 we finally link.

 Possible fix in branch `bug19902_try1` in my public repository. I claim we
 should merge it whether it fixes the issue on openbsd or not.

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

Re: [tor-bugs] #19901 [Core Tor/Tor]: ENABLE_GCC_WARNING is broken on GCC < 4.6

[Tor Bug Tracker & Wiki]

#19901: ENABLE_GCC_WARNING is broken on GCC < 4.6
---+
 Reporter:  nickm  |  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorCoreTeam201608  |  Actual Points:  0
Parent ID: | Points:  0
 Reviewer: |Sponsor:
---+
Changes (by nickm):

 * keywords:   => TorCoreTeam201608
 * actualpoints:   => 0


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

Re: [tor-bugs] #19902 [Core Tor/Tor]: Dual-install of libevent 1 and libevent 2 on openbsd confuses our autoconf logic

[Tor Bug Tracker & Wiki]

#19902: Dual-install of libevent 1 and libevent 2 on openbsd confuses our 
autoconf
logic
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  openbsd   |  Actual Points:
Parent ID:| Points:  .2
 Reviewer:|Sponsor:
--+
Changes (by nickm):

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


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

[tor-bugs] #19902 [Core Tor/Tor]: Dual-install of libevent 1 and libevent 2 on openbsd confuses our autoconf logic

[Tor Bug Tracker & Wiki]

#19902: Dual-install of libevent 1 and libevent 2 on openbsd confuses our 
autoconf
logic
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  openbsd
Actual Points:|  Parent ID:
   Points:  .2|   Reviewer:
  Sponsor:|
--+


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

[tor-bugs] #19901 [Core Tor/Tor]: ENABLE_GCC_WARNING is broken on GCC < 4.6

[Tor Bug Tracker & Wiki]

#19901: ENABLE_GCC_WARNING is broken on GCC < 4.6
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:  0 |   Reviewer:
  Sponsor:|
--+
 I'm doing a fix. Creating a placeholder.

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

Re: [tor-bugs] #19899 [Core Tor/Tor]: prop224: Add a consensus param to enable/disable next gen onion service

[Tor Bug Tracker & Wiki]

#19899: prop224: Add a consensus param to enable/disable next gen onion service
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  enhancement | Status:  accepted
 Priority:  High|  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  prop224, tor-hs, TorCoreTeam201608  |  Actual Points:
Parent ID:  #12424  | Points:  1
 Reviewer:  |Sponsor:
|  SponsorR-must
+--

Comment (by nickm):

 Also, if we do something like this, it should have a matching tri-state in
 the configuration: A "1" means "allow", "0" means "forbid", and "auto"
 means "look at the consensus".

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

Re: [tor-bugs] #19899 [Core Tor/Tor]: prop224: Add a consensus param to enable/disable next gen onion service

[Tor Bug Tracker & Wiki]

#19899: prop224: Add a consensus param to enable/disable next gen onion service
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  enhancement | Status:  accepted
 Priority:  High|  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  prop224, tor-hs, TorCoreTeam201608  |  Actual Points:
Parent ID:  #12424  | Points:  1
 Reviewer:  |Sponsor:
|  SponsorR-must
+--

Comment (by nickm):

 What would be so bad if relays stored prop224 descriptors before the rest
 of this stuff is deployed?

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

Re: [tor-bugs] #19387 [Internal Services/Tor Sysadmin Team]: upgrade troodi [trac] to jessie

[Tor Bug Tracker & Wiki]

#19387: upgrade troodi [trac] to jessie
-+
 Reporter:  weasel   |  Owner:  tpa
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by qbi):

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


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

Re: [tor-bugs] #19870 [Internal Services/Service - trac]: permission error: Tor logo and stylesheet on trac

[Tor Bug Tracker & Wiki]

#19870: permission error: Tor logo and stylesheet on trac
--+
 Reporter:  mrphs |  Owner:  qbi
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by qbi):

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


Comment:

 It's fixed. Sorry for the inconvenience.

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

Re: [tor-bugs] #13017 [Applications/Tor Browser]: Determine if AudioBuffers/OfflineAudioContext are a fingerprinting vector

[Tor Bug Tracker & Wiki]

#13017: Determine if AudioBuffers/OfflineAudioContext are a fingerprinting 
vector
-+-
 Reporter:  mikeperry|  Owner:
 |  arthuredelstein
 Type:  task | Status:
 |  assigned
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  tbb-fingerprinting-os,   |  Actual Points:
  TorBrowserTeam201608   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by qSKvY):

 I run browserprint.info which has these tests on it and can confirm that
 the tests appear to be stable among regular browsers.
 We looked at sets of multiple fingerprints that were made by the same
 browser.
 We found that "Fingerprint using DynamicsCompressor (sum of buffer
 values):", "Fingerprint using DynamicsCompressor (hash of full buffer):",
 and "AudioContext properties:" where very stable (between 1 and 10
 instances out of ~500 of them changing between fingerprints).
 The other two were less stable but the majority of the time they were
 consistent (56 and 87 instances of them changing between fingerprints out
 of ~500).

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

Re: [tor-bugs] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

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


Comment:

 Announced:
 https://lists.torproject.org/pipermail/tor-dev/2016-August/011283.html
 All done.
 Closing.

 Thanks!

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

Re: [tor-bugs] #19900 [Applications/Tor Browser]: Up-to-date Tor Browser asks me to update Firefox

[Tor Bug Tracker & Wiki]

#19900: Up-to-date Tor Browser asks me to update Firefox
--+--
 Reporter:  erchewin  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sukhbir):

 Related: #19890.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19900 [Applications/Tor Browser]: Up-to-date Tor Browser asks me to update Firefox

[Tor Bug Tracker & Wiki]

#19900: Up-to-date Tor Browser asks me to update Firefox
--+--
 Reporter:  erchewin  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 [[Image(https://i.imgur.com/jPpARzE.png, 700px)]]

 Maybe it happens because I use old Firefox installed from Debian APT.
 Firefox was called Iceweasel in Debian and then it was renamed to Firefox.
 Maybe Tor Browser undestands now that I use old system-wide Firefox and
 asks me to upgrade. If it is so, I consider this behavior wrong, because
 it is not Tor Browser's business what else software I use. Moreover when I
 press button "Get Firefox" it redirects me to page
 https://www.torproject.org/download/download-easy.html which does not
 solve the problem of outdated system-wide Firefox in my Debian box...

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

Re: [tor-bugs] #17238 [Core Tor/Tor]: prop224: Implement HSDir support

[Tor Bug Tracker & Wiki]

#17238: prop224: Implement HSDir support
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  enhancement | Status:
|  needs_review
 Priority:  High|  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs, prop224, TorCoreTeam201608  |  Actual Points:
Parent ID:  #12424  | Points:  parent
 Reviewer:  |Sponsor:
|  SponsorR-must
+--
Changes (by dgoulet):

 * status:  accepted => needs_review


Comment:

 Ok _'''big'''_ branch here. Some of it has been reviewed already in
 different branches but this one bring the whole feature together.
 Unfortunately, we need a single branch because all child tickets depends
 on each other.

 The branch contains basically in order of commit appearance: #18515,
 #19024, #18571, #18572, #19205

 Branch is `ticket17238_029_01`. Merge request here:

 https://gitlab.com/dgoulet/tor/merge_requests/9

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

Re: [tor-bugs] #19647 [Core Tor/Tor]: HS Descriptors should only contain printable ASCII

[Tor Bug Tracker & Wiki]

#19647: HS Descriptors should only contain printable ASCII
---+--
 Reporter:  teor   |  Owner:
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-hs, 029-proposed, prop224  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:  SponsorR-can
---+--
Changes (by dgoulet):

 * sponsor:   => SponsorR-can
 * parent:  #17238 =>


Comment:

 Let's not block on HSDir support (#17238) for this. I see this as an
 improvement to the implementation not a dependency.

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

Re: [tor-bugs] #19899 [Core Tor/Tor]: prop224: Add a consensus param to enable/disable next gen onion service

[Tor Bug Tracker & Wiki]

#19899: prop224: Add a consensus param to enable/disable next gen onion service
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  enhancement | Status:  accepted
 Priority:  High|  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  prop224, tor-hs, TorCoreTeam201608  |  Actual Points:
Parent ID:  #12424  | Points:  1
 Reviewer:  |Sponsor:
|  SponsorR-must
+--
Changes (by dgoulet):

 * status:  new => accepted
 * parent:   => #12424


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19899 [Core Tor/Tor]: prop224: Add a consensus param to enable/disable next gen onion service

[Tor Bug Tracker & Wiki]

#19899: prop224: Add a consensus param to enable/disable next gen onion service
--+
 Reporter:  dgoulet   |  Owner:  dgoulet
 Type:| Status:  new
  enhancement |
 Priority:  High  |  Milestone:  Tor: 0.2.9.x-final
Component:  Core  |Version:
  Tor/Tor |
 Severity:  Normal|   Keywords:  prop224, tor-hs, TorCoreTeam201608
Actual Points:|  Parent ID:
   Points:  1 |   Reviewer:
  Sponsor:|
  SponsorR-must   |
--+
 We need a consensus parameter that controls the deployment of proposal 224
 that is next generation onion service.

 Lots of code will go in tor without being used at first so this parameter
 will tell all the tor out there to start using the new generation onion
 service.

 This is especially important before we merge HSDir support (#17238) in
 order for relay to NOT store 224 descriptors while the rest is under
 development.

 I'm thinking `OnionService224=0` (or we can omit 224 here and assume
 "OnionService" is next gen obviously :).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19898 [- Select a component]: Use defalt search in about:tor

[Tor Bug Tracker & Wiki]

#19898: Use defalt search in about:tor
--+-
 Reporter:  f451022   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 maybe can use the defalt search engine on aobut:tor, like firefox make
 with about:home?

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

Re: [tor-bugs] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by karsten):

 * owner:  karsten => iwakeh
 * status:  needs_review => assigned


Comment:

 Good catches in that branch, pushed them all to master.  And good idea to
 make those other two fixes for 1.1.0.  I just did the release dance for
 1.0.0.  Please find the release here:
 https://dist.torproject.org/collector/1.0.0/ .

 Would you want to announce the release on tor-dev@?  Here's the
 [https://lists.torproject.org/pipermail/tor-dev/2016-August/011250.html
 posting I made for the metrics-lib 1.3.1 release] that I'd probably adapt
 if I were to announce this first CollecTor release.  But it would be cool
 to give some more context than what's in the almost empty changelog.  And
 you're in a much better position to give that context, after having worked
 on this release for months.  If you'd like to send this announcement,
 please just go ahead and send whenever you're ready.  Otherwise I can do
 it tomorrow.  Thanks for all your hard work on this first release!

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

[tor-bugs] #19897 [User Experience/Website]: Dead metrics link

[Tor Bug Tracker & Wiki]

#19897: Dead metrics link
-+-
 Reporter:  Samdney  |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 At https://www.torproject.org/getinvolved/volunteer.html.en#project-
 metrics

 Metrics (code: db, web)
 => Link: db
 => Gitweb site with content "No repositories found"

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608R,   |  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by in spatium):

 Replying to [ticket:19890 arthuredelstein]:
 > On Tor Browser 6.0.3 (up-to-date) I saw the following warning appear
 below the URL bar:
 >
 > "Your Firefox is out of date. Please download a fresh copy." On the
 right is a button that says "Get Firefox". Obviously we want to disable
 this warning.

 Solution --
 Go to about:config/extensions.bootstrappedAddon
 Reset the string Value to empty Value {}
 Restart Tor browser.
 The warning will not appear 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] #16702 [Core Tor/Tor]: Broken INTRODUCE2 cell on an intro circ bothers Tor

[Tor Bug Tracker & Wiki]

#16702: Broken INTRODUCE2 cell on an intro circ bothers Tor
--+
 Reporter:  s7r   |  Owner:
 Type:  defect| Status:  reopened
 Priority:  High  |  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:  Tor: 0.2.7.2-alpha
 Severity:  Normal| Resolution:
 Keywords:  tor-hs, 027-backport  |  Actual Points:
Parent ID:| Points:  2
 Reviewer:|Sponsor:  SponsorR-must
--+
Changes (by dgoulet):

 * milestone:  Tor: 0.2.9.x-final => Tor: 0.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] #19043 [Core Tor/Tor]: Implementation of prop224 ESTABLISH_INTRO cell

[Tor Bug Tracker & Wiki]

#19043: Implementation of prop224 ESTABLISH_INTRO cell
-+-
 Reporter:  alec.heif|  Owner:
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.???
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224, 6.s194, |  Actual Points:
  0210-proposed, TorCoreTeam201608   |
Parent ID:  #17241   | Points:  3
 Reviewer:  asn, dgoulet |Sponsor:
 |  SponsorR-must
-+-

Comment (by dgoulet):

 My two cents. I like the idea very much. Scales much better with future
 version. We can have a single version agnostic function that takes the
 token and re-route it to the right function.

 Yes, tokens have different size depending on the version (well except rdv
 token but that might not be true for version 4 and onward). I would add an
 `enum` of the possible type (in this case only two exists) which will
 makes it nicer if we ever add more types. And the token length as well.
 You might also want to put a `or_circuit_t` in there? :)

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

Re: [tor-bugs] #19896 [Core Tor/Tor]: Write a quick how-to for ht.h

[Tor Bug Tracker & Wiki]

#19896: Write a quick how-to for ht.h
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
|  implemented
 Keywords:  TorCoreTeam201608 tor-doc-lowlevel  |  Actual Points:  .1
Parent ID:  | Points:  .1
 Reviewer:  |Sponsor:
|  SponsorU-can
+--
Changes (by nickm):

 * status:  accepted => closed
 * resolution:   => implemented
 * actualpoints:   => .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] #19896 [Core Tor/Tor]: Write a quick how-to for ht.h

[Tor Bug Tracker & Wiki]

#19896: Write a quick how-to for ht.h
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  accepted
 Priority:  Medium  |  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201608 tor-doc-lowlevel  |  Actual Points:
Parent ID:  | Points:  .1
 Reviewer:  |Sponsor:
|  SponsorU-can
+--

Comment (by nickm):

 Done as d5c47f043665d4513bad10e3220dc9b5f088c543

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19896 [Core Tor/Tor]: Write a quick how-to for ht.h

[Tor Bug Tracker & Wiki]

#19896: Write a quick how-to for ht.h
--+
 Reporter:  nickm |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.9.x-final
Component:  Core  |Version:
  Tor/Tor |
 Severity:  Normal|   Keywords:  TorCoreTeam201608 tor-doc-lowlevel
Actual Points:|  Parent ID:
   Points:  .1|   Reviewer:
  Sponsor:|
  SponsorU-can|
--+
 George wanted some tips about using ht.h.  But he's not around IRC.  I'll
 braindump here instead.

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

Re: [tor-bugs] #19896 [Core Tor/Tor]: Write a quick how-to for ht.h

[Tor Bug Tracker & Wiki]

#19896: Write a quick how-to for ht.h
+--
 Reporter:  nickm   |  Owner:  nickm
 Type:  defect  | Status:  accepted
 Priority:  Medium  |  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorCoreTeam201608 tor-doc-lowlevel  |  Actual Points:
Parent ID:  | Points:  .1
 Reviewer:  |Sponsor:
|  SponsorU-can
+--
Changes (by nickm):

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


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

Re: [tor-bugs] #18571 [Core Tor/Tor]: prop224: Encode/Decode descriptor implementation

[Tor Bug Tracker & Wiki]

#18571: prop224: Encode/Decode descriptor implementation
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  enhancement | Status:  accepted
 Priority:  High|  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs, prop224, TorCoreTeam201608  |  Actual Points:
Parent ID:  #17238  | Points:  6
 Reviewer:  |Sponsor:
|  SponsorR-must
+--
Changes (by dgoulet):

 * owner:  special => dgoulet
 * status:  assigned => accepted


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

Re: [tor-bugs] #19872 [Core Tor/Tor]: Introduce prefixed sign/verify functions

[Tor Bug Tracker & Wiki]

#19872: Introduce prefixed sign/verify functions
-+-
 Reporter:  asn  |  Owner:
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.???
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-proposed, tor-hs,|  Actual Points:  0.3
  TorCoreTeam201608  |
Parent ID:   | Points:  0.3
 Reviewer:   |Sponsor:
 |  SponsorR-can
-+-
Changes (by dgoulet):

 * status:  needs_review => needs_revision


Comment:

 Two small things:

 * Need documentation on the returned value that is 0 on success and -1 on
 error. Either that or we document the return value of `ed25519_sign()`
 which has none documented in `crypto_ed25519.c`.

 * There is lots of `strlen(prefix_str)`, could be nicer to do it once and
 then use it. Also, is there a chance that we would like to use this for a
 non string prefix? Would it be bad to just go with `uint8_t *` and pass
 the prefix len as param as well even though it's a string?

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

Re: [tor-bugs] #19872 [Core Tor/Tor]: Introduce prefixed sign/verify functions

[Tor Bug Tracker & Wiki]

#19872: Introduce prefixed sign/verify functions
-+-
 Reporter:  asn  |  Owner:
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.???
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-proposed, tor-hs,|  Actual Points:  0.3
  TorCoreTeam201608  |
Parent ID:   | Points:  0.3
 Reviewer:  dgoulet  |Sponsor:
 |  SponsorR-can
-+-
Changes (by dgoulet):

 * reviewer:   => dgoulet


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

Re: [tor-bugs] #18693 [Core Tor/Tor]: New SOCKS port restriction to only allow connections to .onion

[Tor Bug Tracker & Wiki]

#18693: New SOCKS port restriction to only allow connections to .onion
---+
 Reporter:  ioerror|  Owner:  dgoulet
 Type:  enhancement| Status:  accepted
 Priority:  Very Low   |  Milestone:  Tor: 0.2.9.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-hs, socks  |  Actual Points:  0.5
Parent ID: | Points:  0.5
 Reviewer: |Sponsor:  SponsorR-can
---+
Changes (by dgoulet):

 * status:  needs_revision => accepted
 * owner:   => dgoulet
 * points:  .5 => 0.5
 * reviewer:  special =>
 * actualpoints:  .5 => 0.5


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

Re: [tor-bugs] #19642 [Core Tor/Tor]: Add a descriptor line for Single Onion Services

[Tor Bug Tracker & Wiki]

#19642: Add a descriptor line for Single Onion Services
-+-
 Reporter:  teor |  Owner:  dgoulet
 Type:  enhancement  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.???
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, rsos, sos, 030-proposed, |  Actual Points:
  prop224, TorCoreTeam201608 |
Parent ID:  #17238   | Points:  0.5
 Reviewer:   |Sponsor:
 |  SponsorR-can
-+-
Changes (by dgoulet):

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


Comment:

 The plan is to merge HSDir support in 029 which is almost ready (#17238).
 However, this line would go in the `encrypted` section of the descriptor
 meaning only the client/service will use it which will come not until 030
 at the earliest so I propose we think more about this option and do no
 press on for 029. Keep in mind that `Tor2web` will not be implemented as
 part of prop224 so this should only apply to RSOS/SOS.

 Anycase, we need a proposal change before code can be fixed.

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

Re: [tor-bugs] #17238 [Core Tor/Tor]: prop224: Implement HSDir support

[Tor Bug Tracker & Wiki]

#17238: prop224: Implement HSDir support
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  enhancement | Status:  accepted
 Priority:  High|  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs, prop224, TorCoreTeam201608  |  Actual Points:
Parent ID:  #12424  | Points:  parent
 Reviewer:  |Sponsor:
|  SponsorR-must
+--
Changes (by dgoulet):

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


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

Re: [tor-bugs] #17627 [Core Tor/Tor]: Add missing controller events so we can link every step of the HS dance

[Tor Bug Tracker & Wiki]

#17627: Add missing controller events so we can link every step of the HS dance
+---
 Reporter:  robgjansen  |  Owner:
 Type:  enhancement | Status:  new
 Priority:  Medium  |  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  needs-proposal  |  Actual Points:
Parent ID:  | Points:  3
 Reviewer:  |Sponsor:  SponsorR-must
+---
Changes (by dgoulet):

 * milestone:  Tor: 0.2.9.x-final => Tor: 0.2.???


Comment:

 Postponing to other version. Rob has now someone to help with this so if a
 patch comes in _before_ 029 stable, great but else it's now "unknown".

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

Re: [tor-bugs] #19205 [Core Tor/Tor]: prop224: HSDir fetch/store implementation

[Tor Bug Tracker & Wiki]

#19205: prop224: HSDir fetch/store implementation
+--
 Reporter:  dgoulet |  Owner:  dgoulet
 Type:  enhancement | Status:  accepted
 Priority:  Medium  |  Milestone:  Tor:
|  0.2.9.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-hs, prop224, TorCoreTeam201608  |  Actual Points:
Parent ID:  #17238  | Points:  2
 Reviewer:  |Sponsor:
|  SponsorR-must
+--
Changes (by dgoulet):

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


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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608R,   |  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Just as an update: this issue got fixed on Mozilla's side meanwhile
 (thanks to bhearsum and all the other Mozilla folks that helped).

 We might want to think about shipping an update though (containing the fix
 on our side and an updated tor 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] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608R,   |  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 I guess we could I guess, I followed mcs and brade in patching firefox.js
 here. I think for the fixup release doing that is fine.

 FWIW: The alpha and hardened series is not affected and Tails neither
 (they have `app.update.enabled` set to `false`).

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

Re: [tor-bugs] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  karsten
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 I tested the release branch and the available tar-ball.

 Here is a
 [https://gitweb.torproject.org/user/iwakeh/collector.git/log/?h=task-19813
 -final-touches branch] with three commits:

 An addition to INSTALL.md, the removal of @Ignore from ConfigurationTest,
 and a minor change for SchedulerTest (uses Main.waitSec now ind order to
 avoid code duplication).

 In addition, I created two ticket that should be part of the next release:
 #19894 and #19895.

 I'd say: release 1.0.0 is ready to go.

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608R,   |  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arthuredelstein):

 Replying to [comment:9 gk]:
 > Good idea, thanks. I've been a bit too fast it seems. The fix
 (https://gitweb.torproject.org/tor-browser.git/commit/?h=tor-
 browser-45.3.0esr-6.0-1=61700466ddefff3005633a6e31f34133eb98197f) was
 aimed to go into my public repo not directly to tor-browser-45.3.0-6.0-1.
 Please review, I am holding off starting a build for 6.0.4 until somebody
 looked at it.

 Rather than patching firefox.js directly, maybe we should apply this
 setting in  `browser/app/profile/000-tor-browser.js` as we have with most
 other prefs? (I notice we have two other changes to firefox.js (from our
 patches for #5472 and #4234) -- maybe these should also be migrated to 000
 -tor-browser.js?)

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

Re: [tor-bugs] #19895 [Metrics/CollecTor]: make CollecTor stop after RunOnce

[Tor Bug Tracker & Wiki]

#19895: make CollecTor stop after RunOnce
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * milestone:   => CollecTor 1.1.0


Comment:

 For release 1.1.0 as it is clearly visible in the log when it is save to
 terminate the jvm.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19895 [Metrics/CollecTor]: make CollecTor stop after RunOnce

[Tor Bug Tracker & Wiki]

#19895: make CollecTor stop after RunOnce
---+
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 The activated modules are run one time, which is correct.
 The configuration check thread just keeps running and thus CollecTor w/o
 doing anything.

 Suggested behavior:
 Exit CollecTor after all activated modules ran one time.

 (related to #19894)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19894 [Metrics/CollecTor]: print message when no module is activated

[Tor Bug Tracker & Wiki]

#19894: print message when no module is activated
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  CollecTor 1.1.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Minor  |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+-
 When no module is activated CollecTor just runs and does nothing.

 Suggested behavior:
 print information and usage and exit if no module is activated.

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608R,   |  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  TorBrowserTeam201608, tbb-6.0-issues => TorBrowserTeam201608R,
 tbb-6.0-issues
 * status:  new => needs_review


Comment:

 Good idea, thanks. I've been a bit too fast it seems. The fix
 (https://gitweb.torproject.org/tor-browser.git/commit/?h=tor-
 browser-45.3.0esr-6.0-1=61700466ddefff3005633a6e31f34133eb98197f) was
 aimed to go into my public repo not directly to tor-browser-45.3.0-6.0-1.
 Please review, I am holding off starting a build for 6.0.4 until somebody
 looked at 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] #19162 [Core Tor/Tor]: Make it even harder to become HSDir

[Tor Bug Tracker & Wiki]

#19162: Make it even harder to become HSDir
-+-
 Reporter:  asn  |  Owner:  arma
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs SponsorR 029-proposed |  Actual Points:
  TorCoreTeam201608  |
Parent ID:   | Points:  4
 Reviewer:   |Sponsor:
 |  SponsorR-can
-+-

Comment (by asn):

 Roger is it still the case that the tk cutoffs in your logs are strictly
 increasing?
 Can you post some more recent "Cutoffs" logs to verify this?

 If that's still the case, the next move here is to take the tk dataset
 that you posted a month ago, and make a python script that calculates the
 cutoffs, and test if they are also strictly increasing. Unfortunately, we
 don't have the corresponding "Cutoffs" logs for those dates, to check the
 correctness of the script.

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608,|  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arthuredelstein):

 Replying to [comment:7 cypherpunks]:
 > `extensions.systemAddon.update.url` should be set to "".

 I think this is a good solution. To check this, I found the location of
 the XPI in Tor Browser:
 {{{
 arthur@localhost ~/t/Browser> find . -name "*outofdate*"
 ./TorBrowser/Data/Browser/profile.default/features/{541bf4ef-2e8d-
 44d5-9aa1-887165d68eec}/outofdate-notificati...@mozilla.org.xpi
 
./TorBrowser/Data/Browser/profile.default/datareporting/archived/2016-08/1470864327100
 .72bc501f-cad6-4be7-b082-9af725197de9.outofdate-notifications-system-
 addon.jsonlz4
 
./TorBrowser/Data/Browser/profile.default/datareporting/archived/2016-08/1470864333700.c7c02599-f462-49f2-8f11-fad83bfc976c
 .outofdate-notifications-system-addon.jsonlz4
 }}}
 After setting the pref to "", I opened Tor Browser and entered the
 following in the browser console:
 {{{
 Cu.import("resource://gre/modules/AddonManager.jsm");
 AddonManagerPrivate.backgroundUpdateCheck();
 }}}
 Then I confirmed that the XPI had been removed:
 {{{
 arthur@localhost ~/t/Browser> find . -name "*outofdate*"
 
./TorBrowser/Data/Browser/profile.default/datareporting/archived/2016-08/1470864327100
 .72bc501f-cad6-4be7-b082-9af725197de9.outofdate-notifications-system-
 addon.jsonlz4
 
./TorBrowser/Data/Browser/profile.default/datareporting/archived/2016-08/1470864333700.c7c02599-f462-49f2-8f11-fad83bfc976c
 .outofdate-notifications-system-addon.jsonlz4
 }}}
 Here is the relevant code that apparently removes the XPI file. When the
 pref is empty, `url` is falsey and `yield
 systemAddonLocation.cleanDirectories();` is called:
 https://dxr.mozilla.org/mozilla-central/rev
 
/0502bd9e025edde29777ba1de4280f9b52af4663/toolkit/mozapps/extensions/internal/XPIProvider.jsm#3069

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

Re: [tor-bugs] #19162 [Core Tor/Tor]: Make it even harder to become HSDir

[Tor Bug Tracker & Wiki]

#19162: Make it even harder to become HSDir
-+-
 Reporter:  asn  |  Owner:  arma
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs SponsorR 029-proposed |  Actual Points:
  TorCoreTeam201608  |
Parent ID:   | Points:  4
 Reviewer:   |Sponsor:
 |  SponsorR-can
-+-
Changes (by asn):

 * keywords:  tor-hs SponsorR 029-proposed TorCoreTeam201606 => tor-hs
 SponsorR 029-proposed TorCoreTeam201608


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

Re: [tor-bugs] #19043 [Core Tor/Tor]: Implementation of prop224 ESTABLISH_INTRO cell

[Tor Bug Tracker & Wiki]

#19043: Implementation of prop224 ESTABLISH_INTRO cell
-+-
 Reporter:  alec.heif|  Owner:
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.???
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-hs, prop224, 6.s194, |  Actual Points:
  0210-proposed, TorCoreTeam201608   |
Parent ID:  #17241   | Points:  3
 Reviewer:  asn, dgoulet |Sponsor:
 |  SponsorR-must
-+-

Comment (by asn):

 Replying to [comment:15 nickm]:
 > Replying to [comment:13 asn]:
 > >   b) Somehow refactor the current system so that we can do both old-
 style and prop224 mappings using the same data structure. For example, we
 could hash the old-style keys with sha256 and store them in a digest256
 map, and do the same for new style keys as well (or just store the keys
 intact since they are 32bytes).
 >
 > This is what I'd suggest.  I'd suggest an underlying data structure
 mapping a tagged structure to a circuit pointer.  If you use the handle
 and the ht code, it should actually be easy.
 >
 > Then you can define all the accessor functions, to actually make the
 code safer.

 Hm, I'm very unfamiliar with the `HT_` and `HANDLE_` code, but I'm
 definitely willing to get my hands dirty if this is the right way to do
 this. I'll start studying the `HT_PROTOTYPE` and `HT_GENERATE2` functions.

 BTW, the idea here is that we want to create a new map that maps from all
 sorts of HS tokens (`hs_token_t`) to circuits. Right? An `hs_token_t` in
 this case can hold both old-style and new-style tokens for both
 introduction and rendezvous.

 For example here is a data structure definition:
 {{{
 /** Represents a token used in the HS protocol. Each such token maps to a
  *  specific introduction or rendezvous circuit. */
 typedef struct hs_token_t {
   /* The HS protocol version that uses this token.
*
* The version value is 2 for the old HS version, and 3 for next
 generation
* hidden services.
*
* The size of the hs_token depends on the HS protocol version and the
 type
* of token:
*  Old HS protocol uses 128bit tokens for introduction and rendezvous.
*  New HS protocol uses 128bit tokens for rendezvous, and 256bit tokens
 for
*  introductions. */
   int version;

   /* Is this a rendezvous cookie? Otherwise, it's an introduction token.
 */
   int is_rend_token;

   /* The token itself. Memory allocated at runtime depending on the HS
 version. */
   uint8_t *hs_token;
 }
 }}}

 Does this look reasonable to 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] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608,|  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 `extensions.systemAddon.update.url` should be set to "".

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608,|  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 Okay, I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=1294395 and
 poked the Mozilla folks on #releng. Hopefully they can tweak the server-
 side rules in order to affect less of our users while we are working on
 getting a new version out.

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

Re: [tor-bugs] #11442 [HTTPS Everywhere/HTTPS Everywhere: Chrome]: Amazon Web Services rule breaks issuu.com

[Tor Bug Tracker & Wiki]

#11442: Amazon Web Services rule breaks issuu.com
-+-
 Reporter:  cypherpunks  |  Owner:  pde
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/HTTPS Everywhere:   |Version:
  Chrome |
 Severity:  Blocker  | Resolution:
 Keywords:  httpse-ruleset-bug   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by Jenny):

 * severity:   => Blocker


Comment:

 Property Pages Phuket is a real estate listing directory covering property
 for sale and rent in Phuket.

 [http://propertypagesphuket.com]

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

Re: [tor-bugs] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  karsten
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 The ConfigurationTest still contains @Ignore annotations
 [https://gitweb.torproject.org/karsten/metrics-
 
db.git/tree/src/test/java/org/torproject/collector/conf/ConfigurationTest.java?h=task-19813=06bcf327bb7741f3b972e932c80c7cfcb090e1fa#n176
 here] and [https://gitweb.torproject.org/karsten/metrics-
 
db.git/tree/src/test/java/org/torproject/collector/conf/ConfigurationTest.java?h=task-19813=06bcf327bb7741f3b972e932c80c7cfcb090e1fa#n197
 here] and the import.  They are not necessary anymore (are they?) and
 shouldn't be released.

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

Re: [tor-bugs] #19872 [Core Tor/Tor]: Introduce prefixed sign/verify functions

[Tor Bug Tracker & Wiki]

#19872: Introduce prefixed sign/verify functions
-+-
 Reporter:  asn  |  Owner:
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.???
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  029-proposed, tor-hs,|  Actual Points:  0.3
  TorCoreTeam201608  |
Parent ID:   | Points:  0.3
 Reviewer:   |Sponsor:
 |  SponsorR-can
-+-
Changes (by asn):

 * status:  new => needs_review
 * actualpoints:   => 0.3


Comment:

 Please check my branch `bug19872` for an implementation of those
 functions.

 
https://gitweb.torproject.org/user/asn/tor.git/commit/?h=bug19872=ce0820755f5c4b6b74bade2299adeb0c89a52335

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

Re: [tor-bugs] #19893 [Metrics/metrics-lib]: Include resources in tarball

[Tor Bug Tracker & Wiki]

#19893: Include resources in tarball
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  defect   | Status:  needs_review
 Priority:  Low  |  Milestone:  metrics-lib 1.4.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by karsten):

 * status:  new => needs_review


Comment:

 Please review the trivial patch in my
 [https://gitweb.torproject.org/user/karsten/metrics-
 lib.git/log/?h=task-19893 my task-19893 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] #19893 [Metrics/metrics-lib]: Include resources in tarball

[Tor Bug Tracker & Wiki]

#19893: Include resources in tarball
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:  metrics-lib 1.4.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+---
 While putting out the first CollecTor release I noticed that the release
 tarball of metrics-lib does not include resource files
 `src/main/resources/*` and `src/test/resources/*`.  We should include them
 in the next release tarball.

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

Re: [tor-bugs] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  karsten
 Type:  task   | Status:  needs_review
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by karsten):

 * status:  assigned => needs_review


Comment:

 Please review the last commit in [https://gitweb.torproject.org/karsten
 /metrics-db.git/log/?h=task-19813 my branch task-19813] carefully, and
 please try out
 [https://people.torproject.org/~karsten/volatile/collector-1.0.0-pre.tar.gz
 this pre-release tarball].  If all looks good, I'll put out the release
 later this afternoon.  Thanks!

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

Re: [tor-bugs] #14209 [Core Tor/Tor]: Implement new option SocksNamedPipe for Windows users

[Tor Bug Tracker & Wiki]

#14209: Implement new option SocksNamedPipe for Windows users
--+--
 Reporter:  anon  |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-client|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by xeonchen):

 * severity:   => Normal


Comment:

 per nickm:

 

 I'd suggest an extra thread and event loop to process Windows handles.
 You'll need to communicate with the main thread; look at workqueue.c
 to get some idea of how we do that now, though you'd probably want a
 different implementation.  Avoid sharing structures whenever possible.
 To keep as much shared implementation as possible, you might do it like
 this:
 * enable threadsafe mode when initializing libevent.
 * Add handle-based versions of read_to_buf / flush_buf. Use them as
 appropriate.
 * Allow a connection_t to optionally have a handle instead of a socket.
 * When constructing the event objects for the handle, do not pass in a
 file descriptor. Instead, pass a file descriptor of -1.
 * From the worker thread, use event_active() to make those event objects
 active when the handles are ready for read/write. (This is why libevent
 needs to be running with thread safety enabled.)
 * Now all you'll need is some way for the main thread to tell the worker
 thread about new handles, closed handles, and which of the handles should
 be reading/writing.

 

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

Re: [tor-bugs] #19570 [Core Tor/Tor]: Shared random round gets out of sync

[Tor Bug Tracker & Wiki]

#19570: Shared random round gets out of sync
--+--
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  reopened
 Priority:  High  |  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tor-sr, 029-proposed  |  Actual Points:
Parent ID:| Points:  0.5
 Reviewer:|Sponsor:  SponsorR-can
--+--
Changes (by asn):

 * keywords:  tor-sr => tor-sr, 029-proposed
 * sponsor:  SponsorR-must => SponsorR-can
 * milestone:  Tor: 0.2.9.x-final => Tor: 0.2.???


Comment:

 This ticket is not a bug anymore. It's a non-essential feature request.
 Changing ticket to more realistic severities.

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

Re: [tor-bugs] #19837 [Applications/Tor Browser]: Audio/video player is blank in 6.5a2

[Tor Bug Tracker & Wiki]

#19837: Audio/video player is blank in 6.5a2
-+-
 Reporter:  dcf  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-regression,  |  Actual Points:
  TorBrowserTeam201608   |
Parent ID:  #8725| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arthuredelstein):

 * cc: arthuredelstein (added)


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

Re: [tor-bugs] #19791 [Metrics/metrics-lib]: Adapt to CollecTor's new date format

[Tor Bug Tracker & Wiki]

#19791: Adapt to CollecTor's new date format
-+---
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:  metrics-lib 1.4.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * milestone:   => metrics-lib 1.4.0


Comment:

 Added to milestone 1.4.0

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

Re: [tor-bugs] #19791 [Metrics/metrics-lib]: Adapt to CollecTor's new date format

[Tor Bug Tracker & Wiki]

#19791: Adapt to CollecTor's new date format
-+--
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Birds-view description of approach for reading from index.json:

 * move currently private node-classes IndexNode, FileNode, DirectoryNode
 to metrics-lib `org.torproject.descriptor.index`.
 * provide metrics-lib with a reading interface and implementation
 * make collector use metrics-lib node-classes

 What needs to be added/altered?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19892 [Internal Services]: viewvc broken on svn.tpo

[Tor Bug Tracker & Wiki]

#19892: viewvc broken on svn.tpo
---+-
 Reporter:  ln5|  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Internal Services  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+-
 https://svn.torproject.org/cgi-bin/viewvc.cgi?view=roots (linked from
 https://svn.torproject.org/) doesn't work (443).

 We could either fix it or remove the link.

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

Re: [tor-bugs] #19170 [Metrics/CollecTor]: make parsing more robust (extra-info)

[Tor Bug Tracker & Wiki]

#19170: make parsing more robust (extra-info)
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by karsten):

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


Comment:

 Merged together with the task-19720 branch.  Closing.  Thanks!

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

Re: [tor-bugs] #19413 [Applications/Tor Browser]: hardened browser does not start on debian with grsec

[Tor Bug Tracker & Wiki]

#19413: hardened browser does not start on debian with grsec
--+--
 Reporter:  tblah |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 I guess this is to be expected given
 {{{
 It [i.e. Address Sanitizer, G.K.] is also currently incompatible with some
 other security measurements (most notably Grsecurity) and with many other
 debugging tools (e. g. Valgrind).
 }}}
 (https://wiki.gentoo.org/wiki/AddressSanitizer).

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

Re: [tor-bugs] #19813 [Metrics/CollecTor]: define release process and do release of milestone 1.0.0

[Tor Bug Tracker & Wiki]

#19813: define release process and do release of milestone 1.0.0
---+-
 Reporter:  iwakeh |  Owner:  karsten
 Type:  task   | Status:  assigned
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by karsten):

 * status:  needs_review => assigned


Comment:

 Merged that README, thanks!  I'll now prepare the release.  Stay tuned. :)

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

Re: [tor-bugs] #19720 [Metrics/CollecTor]: CollecTor should be re-configurable without restart

[Tor Bug Tracker & Wiki]

#19720: CollecTor should be re-configurable without restart
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  closed
 Priority:  High   |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by karsten):

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


Comment:

 Great, it works!  Cherry-picked and pushed to master, together with the
 other commits in my task-19720 branch.  Closing.  Thanks!

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Critical | Resolution:
 Keywords:  TorBrowserTeam201608,|  Actual Points:
  tbb-6.0-issues |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  TorBrowserTeam201608 => TorBrowserTeam201608, tbb-6.0-issues


Comment:

 Replying to [comment:1 arthuredelstein]:
 > Looks like it came from this bug.
 > https://bugzilla.mozilla.org/show_bug.cgi?id=1280378
 >
 > I'm not sure yet how it gets into Firefox (or Tor Browser for that
 matter).

 It seems the infrastructure was already there starting with Firefox 44:

 https://bugzilla.mozilla.org/show_bug.cgi?id=1192924 and
 https://bugzilla.mozilla.org/show_bug.cgi?id=1213348.

 Now, they probably just were ready with the "your Firefox is out of
 date"-system add-on. I guess we should just disable that update ping with
 our `data:text/plain,` trick. And think about how to get rid of already
 installed system extensions.

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

Re: [tor-bugs] #19706 [Applications/Tor Browser]: GetUserDataDirectoryHome in nsXREDirProvider.cpp breaks Orfox

[Tor Bug Tracker & Wiki]

#19706: GetUserDataDirectoryHome in nsXREDirProvider.cpp breaks Orfox
---+---
 Reporter:  amoghbl1   |  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_review
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-mobile, TorBrowserTeam201608R  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
Changes (by gk):

 * cc: arthuredelstein (added)


Comment:

 Looks good to me. Arhur, could you have a look at it as well?

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

Re: [tor-bugs] #19818 [Applications/Tor Browser]: The update_responses script should use a config.yml option for the releases directory path

[Tor Bug Tracker & Wiki]

#19818: The update_responses script should use a config.yml option for the 
releases
directory path
---+
 Reporter:  boklm  |  Owner:  boklm
 Type:  task   | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  TorBrowserTeam201608R, tbb-gitian  |  Actual Points:
Parent ID:  #19817 | Points:
 Reviewer: |Sponsor:
---+
Changes (by gk):

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


Comment:

 Fixed on master, maint-6.0 and hardened-builds (commit
 260c051a69a7323084793c23c6ed53cd1344dd72,
 1bb5bba64b60009c3deb8cc5119dd41d7615f3d4 and
 fcf89874d5b9919633d312e89d8aea529f5664d2).

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

Re: [tor-bugs] #19835 [Applications/Tor Browser]: Put "Tor Browser" and version on the upper right of the changelog page too

[Tor Bug Tracker & Wiki]

#19835: Put "Tor Browser" and version on the upper right of the changelog page 
too
-+-
 Reporter:  arma |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-usability,TorBrowserTeam201608R  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 As said in #19336, applied to tor-browser-45.3.0esr-6.5-1 (commit
 219b21731bec577b8797a8914612f0ae9e55d1ad). We can think about backporting
 this for the stable if there are no issues in the next alpha.

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

Re: [tor-bugs] #19336 [Applications/Tor Browser]: Make text stand out in about:tbupdate

[Tor Bug Tracker & Wiki]

#19336: Make text stand out in about:tbupdate
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-usability,TorBrowserTeam201608R  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Looks good to me. I applied the patch to tor-browser-45.3.0esr-6.5-1
 (commit 219b21731bec577b8797a8914612f0ae9e55d1ad). We can backport that to
 the stable branch if all works out as intended.

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

Re: [tor-bugs] #19891 [Applications/Tor Browser]: "Update Firefox" bug in TBB

[Tor Bug Tracker & Wiki]

#19891: "Update Firefox" bug in TBB
--+---
 Reporter:  b_meson   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

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


Comment:

 Duplicate of #19890.

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

Re: [tor-bugs] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  TorBrowserTeam201608  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * cc: b_meson (added)


Comment:

 #19891 is a 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] #19890 [Applications/Tor Browser]: Tor Browser warning: "Your Firefox is out of date."

[Tor Bug Tracker & Wiki]

#19890: Tor Browser warning: "Your Firefox is out of date."
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  TorBrowserTeam201608  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * priority:  Medium => Very High
 * severity:  Normal => Critical


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