Re: [tor-bugs] #19001 [Obfuscation/Snowflake]: Tor Browser with Snowflake

[Tor Bug Tracker & Wiki]

#19001: Tor Browser with Snowflake
---+-
 Reporter:  dcf|  Owner:
 Type:  project| Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by dcf):

 I'm making some good progress on the mac build. For the first time, I got
 a libwebrtc-darwin-amd64-magic.a built. (I had to do some bad things to do
 it.) The build of go-webrtc failed ultimately because of a few missing
 Objective-C++ symbols--the build system assumes that only Xcode can
 compile Objective-C++ and left out a few source files. So now I'm digging
 into that but my feeling is we're getting pretty close. (Whether the
 compiled library will actually ''work'' is potentially another matter.)

 I'm doing a build now to see that I got all my manual steps into the
 gitian descriptors.

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

Re: [tor-bugs] #19001 [Obfuscation/Snowflake]: Tor Browser with Snowflake

[Tor Bug Tracker & Wiki]

#19001: Tor Browser with Snowflake
---+-
 Reporter:  dcf|  Owner:
 Type:  project| Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by dcf):

 Replying to [comment:11 serene]:
 > I successfully built TBB (just for linux) with latest snowflake
 [https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/commit/?id=ac9d49b8727b953c12a76e3645fe71a9ec3aab75
 ac9d49b872]
 > Can we bump the version to this latest one? (I can't push to your
 branch)

 I created #19848 to give you and arlo access.

 > Also, question about including multiplexing in the torrc defaults.
 >
 > For quicker recovery when browsing and the current remote goes offline,
 I've manually added the flag {{{-max 3}}} to the ClientTransportPlugin
 snowflake line in /Browser/TorBrowser/Data/Tor/torrc. Can you confirm if
 multiplexing works well on your end / if this might be a sensible default?
 >
 > If so, would it make sense to update the torrc in the pre-build so that
 the build itself would generate this default?

 Edit the files Bundle-Data/PTConfigs/{linux,mac,windows}/torrc-defaults-
 appendix in order to change command-line defaults.

 I'm in the middle of the mac build so I haven't tried
 [https://gitweb.torproject.org/pluggable-
 transports/snowflake.git/commit/?id=ac9d49b8727b953c12a76e3645fe71a9ec3aab75
 ac9d49b872].

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19848 [Internal Services/Service - git]: Grant arlo and serene access to /user/dcf/tor-browser-bundle.git

[Tor Bug Tracker & Wiki]

#19848: Grant arlo and serene access to /user/dcf/tor-browser-bundle.git
-+
 Reporter:  dcf  |  Owner:  tor-gitadm
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 I'd like these LDAP names to be able to push to /user/dcf/tor-browser-
 bundle.git, please.
  * arlo
  * serene

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

Re: [tor-bugs] #17245 [User Experience/Website]: Getting stats on the website

[Tor Bug Tracker & Wiki]

#17245: Getting stats on the website
-+---
 Reporter:  mrphs|  Owner:  Sebastian
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  UX, analytics, stats |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by arthuredelstein):

 * cc: arthuredelstein (added)


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

Re: [tor-bugs] #10675 [Archived/general]: Let's graph an estimate of the number of Tor Browser users

[Tor Bug Tracker & Wiki]

#10675: Let's graph an estimate of the number of Tor Browser users
--+-
 Reporter:  lunar |  Owner:
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Archived/general  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by arthuredelstein):

 * cc: arthuredelstein (added)


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

Re: [tor-bugs] #19804 [Applications/Tor Browser]: HTML5 fingerprinting by battery status

[Tor Bug Tracker & Wiki]

#19804: HTML5 fingerprinting by battery status
--+--
 Reporter:  cypherpunks   |  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 gacar):

 Yes, Battery Status API is
 
[https://gitweb.torproject.org/torbutton.git/tree/src/chrome/content/torbutton.js?id=e403cd883db74649eed86aed0edaf3d101d07fbb#n2295
 disabled] by default in Tor Browser.

 To be specific, the API is disabled as long as "''Change details that
 distinguish you from other Tor Browser users''" option is checked in
 "''Privacy and Security Settings''" panel.

 See also, #5293.

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

Re: [tor-bugs] #19844 [- Select a component]: Prevent browser history leaks from CSS mix-blend-mode API in Tor Browser

[Tor Bug Tracker & Wiki]

#19844: Prevent browser history leaks from CSS mix-blend-mode API in Tor Browser
--+-
 Reporter:  isis  |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-linkability   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 lcamtuf's demo does not work for me with Tor Browser 6.0.3.

 Even I visit the test sites (reddit, amazon, etc.) on the same tab, the
 demo cannot find any visited site and suspects that I'm in incognito.

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

Re: [tor-bugs] #19847 [- Select a component]: make tor@default.service a non-static unit

[Tor Bug Tracker & Wiki]

#19847: make tor@default.service a non-static unit
--+--
 Reporter:  cypherpunks   |  Owner:
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Replying to [comment:3 weasel]:
 > If static means it has an [install] section, then we don't want that.
 >
 > We want tor.service to pull it in.  This means that tor.service restart
 will restart all the instances.

 If you add an [Install] section, the restart effect stays the same.
 Or explained the other way around: /lib/systemd/system/tor@.service has an
 [Install] section and they also get restarted when tor.service is
 restarted (because of the PartOf= line).

 What is the current rational for not having a [Install] section in
 tor@default?

 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] #19847 [- Select a component]: make tor@default.service a non-static unit

[Tor Bug Tracker & Wiki]

#19847: make tor@default.service a non-static unit
--+--
 Reporter:  cypherpunks   |  Owner:
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by weasel):

 If static means it has an [install] section, then we don't want that.

 We want tor.service to pull it in.  This means that tor.service restart
 will restart all the instances.

 Also, tor.service will not include the default tor service if it doesn't
 have a config 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] #19819 [Core Tor/Tor]: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6

[Tor Bug Tracker & Wiki]

#19819: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6
--+
 Reporter:  hacktic   |  Owner:
 Type:  defect| Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by hacktic):

 Fix committed ->
 
https://gitweb.torproject.org/debian/tor.git/commit/?id=86d5dc6e083e21acfe42e3cc349b0fa6e49fa08b

 Thanks weasel

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

Re: [tor-bugs] #19847 [- Select a component]: make tor@default.service a non-static unit

[Tor Bug Tracker & Wiki]

#19847: make tor@default.service a non-static unit
--+--
 Reporter:  cypherpunks   |  Owner:
 Type:  enhancement   | Status:  reopened
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

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


Comment:

 Ok, let me elaborate:
 Currently it is not possible to disable tor@default. service
 via
 {{{
 systemctl disable tor@default
 }}}
 since it is a static unit.

 Making it a non-static unit would allow users to disable the default
 instance while continuing to use other multi-instances.

 More on static vs. non-static units:
 https://bbs.archlinux.org/viewtopic.php?id=147964

 context:
 https://lists.torproject.org/pipermail/tor-relays/2016-August/009851.html

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

Re: [tor-bugs] #19847 [- Select a component]: make tor@default.service a non-static unit

[Tor Bug Tracker & Wiki]

#19847: make tor@default.service a non-static unit
--+-
 Reporter:  cypherpunks   |  Owner:
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by weasel):

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


Comment:

 Unclear what is requested here.

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

Re: [tor-bugs] #19819 [Core Tor/Tor]: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6

[Tor Bug Tracker & Wiki]

#19819: 100% CPU usage and restarts after upgrade from 0.2.8.5-rc to 0.2.8.6
--+
 Reporter:  hacktic   |  Owner:
 Type:  defect| Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.2.8.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.2.8.6
 Severity:  Major | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by hacktic):

 * status:  new => needs_review


Comment:

 Update 3: when upgrading to 0.2.8.6-2 and even just running a relay for 2
 days it will hit this limit.

 please increase  /lib/systemd/system/tor default.service TimeoutStartSec=
 from 120 to 300 to fix this issue

 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

[tor-bugs] #19847 [- Select a component]: make tor@default.service a non-static unit

[Tor Bug Tracker & Wiki]

#19847: make tor@default.service a non-static unit
--+-
 Reporter:  cypherpunks   |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 Making it a non-static unit allows users to disable it via the usual
 systemctl command
 {{{
 systemctl disable tor@default.service
 }}}
 Are there any drawbacks to allowing that?

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

Re: [tor-bugs] #19809 [Applications/Tor Messenger]: Update verification failed but update still applies on Linux and OS X

[Tor Bug Tracker & Wiki]

#19809: Update verification failed but update still applies on Linux and OS X
+
 Reporter:  sukhbir |  Owner:
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Messenger  |Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  |  Actual Points:
Parent ID:  #14388  | Points:
 Reviewer:  |Sponsor:
+
Changes (by sukhbir):

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


Comment:

 OK I managed to figure it out. I was missing setting the update channel in
 the mozconfig (!). Setting:

 {{{
 ac_add_options --enable-update-channel=release
 }}}

 Fixed the issue. I realized this after noticing that the update channel
 was default. I had this option in the mozconfig files for Linux and OS X
 but somehow missed Windows.

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

Re: [tor-bugs] #19845 [Internal Services/Tor Sysadmin Team]: Please create an LDAP account for Huy

[Tor Bug Tracker & Wiki]

#19845: Please create an LDAP account for Huy
-+-
 Reporter:  arlolra  |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sukhbir):

 +1 from me, if it matters :)

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

[tor-bugs] #19846 [Internal Services/Tor Sysadmin Team]: Create coniks.torproject.org, or similar, to host CONIKS server

[Tor Bug Tracker & Wiki]

#19846: Create coniks.torproject.org, or similar, to host CONIKS server
-+
 Reporter:  arlolra  |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:  #19845
   Points:   |   Reviewer:
  Sponsor:   |
-+
 We need somewhere to host the CONIKS server on Tor infrastructure.

 It's a RAM heavy application, so more is better.  Written in golang, so
 please install that.

 Access is required for the `tormessenger` group, and `huyvq`.

 Thanks!


 For further information about the project, please see,
 https://github.com/coniks-sys/coniks-go
 https://trac.torproject.org/projects/tor/ticket/17961
 and the status updates on the tor-dev ml.

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

Re: [tor-bugs] #19845 [Internal Services/Tor Sysadmin Team]: Please create an LDAP account for Huy

[Tor Bug Tracker & Wiki]

#19845: Please create an LDAP account for Huy
-+-
 Reporter:  arlolra  |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Description changed by arlolra:

Old description:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Huy is a GSoC participant this go around, working on CONIKS for Tor
> Messenger.
> We'd like to setup the developed CONIKS server on Tor infrastructure.
>
> For further information about the project, please see,
> https://github.com/coniks-sys/coniks-go
> https://trac.torproject.org/projects/tor/ticket/17961
> and the status updates on the tor-dev ml.
>

> First name: Quoc Huy
> Last name: Vu
> Desired uid: huyvq
> Forwarding address: huyvq.c...@gmail.com
>
> $ gpg --fingerprint 533191CEEC406DFF360D19DEC6202750C2FA740E
> pub   4096R/C2FA740E 2016-07-30 [expires: 2020-01-01]
>   Key fingerprint = 5331 91CE EC40 6DFF 360D  19DE C620 2750 C2FA
> 740E
> uid   [  full  ] Vu Quoc Huy 
> sub   4096R/B88E95ED 2016-07-30 [expires: 2020-01-01]
>
> -BEGIN PGP SIGNATURE-
>
> iQIcBAEBCgAGBQJXpNV5AAoJEF46k7TU3c2L4moP/RT4KZ7E91uU/I9ZVIwBR+4p
> SLuMAX2Ys5a3reodBkzLUkb8pW1MLXCNPQPWRk/4nchIEptEC+6WceMM+AGnKJpi
> sOyXJbmotzE1OG9m6T9BcoTodU+5MKtv2qIVnC+V0/l/QTUJMpT8NUuL+k6ya2i6
> zykLyoR/dMOf83z94LpaKLVj+8Y7/8tuTjqcxGgQzm3qv9dSdw4eF5ywMoWPA6Vq
> mriOtnMM74M2VmtTJtF+sVUHn6YlY9Ve7x119VDyYd9TbikVCDlIkjAflh8r28Fl
> 3tOYijVD4g1w/pmkSZC2wuMqhCQFoo+hdqFmSbM2cZsbM3t54jgoHg8R9BfZq9JC
> 7LglaYs0S9PiLgqjY2MRVjV9MyQNzKga0oEfYTx4uchcAdGOK9w/zpSA8y6EwNNB
> TCnGd9WALGysfdM7024Y5fsWx3bkBgWGF67WrF4q14vviHO9S0HxRUMarZ8ZMdIW
> br7rZ5C+UgxmQCz70hdJJrPw6FW1ByULmfrOLCX/2Y4wT56nzYbaMKzNppBj3mbz
> klYANFu581SA/r81TjAvjrS8wJAPGfl6hrHRcC18igocgKOrRjDnFIjBUy6tVhQT
> DnZ+ms0p4WNvkK8rOmgVxP4jX7Ka8LLZdXccujX4pC7zVwwZwqpunixZhhV6sPJn
> OhKQLRE865RhSefs48h1
> =eb0R
> -END PGP SIGNATURE-

New description:

 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 Huy is a GSoC participant this go around, working on CONIKS for Tor
 Messenger.
 We'd like to setup the developed CONIKS server on Tor infrastructure.

 For further information about the project, please see,
 https://github.com/coniks-sys/coniks-go
 https://trac.torproject.org/projects/tor/ticket/17961
 and the status updates on the tor-dev ml.


 First name: Quoc Huy
 Last name: Vu
 Desired uid: huyvq
 Forwarding address: huyvq.c...@gmail.com

 $ gpg --fingerprint 533191CEEC406DFF360D19DEC6202750C2FA740E
 pub   4096R/C2FA740E 2016-07-30 [expires: 2020-01-01]
   Key fingerprint = 5331 91CE EC40 6DFF 360D  19DE C620 2750 C2FA 740E
 uid   [  full  ] Vu Quoc Huy 
 sub   4096R/B88E95ED 2016-07-30 [expires: 2020-01-01]

 -BEGIN PGP SIGNATURE-

 iQIcBAEBCgAGBQJXpNV5AAoJEF46k7TU3c2L4moP/RT4KZ7E91uU/I9ZVIwBR+4p
 SLuMAX2Ys5a3reodBkzLUkb8pW1MLXCNPQPWRk/4nchIEptEC+6WceMM+AGnKJpi
 sOyXJbmotzE1OG9m6T9BcoTodU+5MKtv2qIVnC+V0/l/QTUJMpT8NUuL+k6ya2i6
 zykLyoR/dMOf83z94LpaKLVj+8Y7/8tuTjqcxGgQzm3qv9dSdw4eF5ywMoWPA6Vq
 mriOtnMM74M2VmtTJtF+sVUHn6YlY9Ve7x119VDyYd9TbikVCDlIkjAflh8r28Fl
 3tOYijVD4g1w/pmkSZC2wuMqhCQFoo+hdqFmSbM2cZsbM3t54jgoHg8R9BfZq9JC
 7LglaYs0S9PiLgqjY2MRVjV9MyQNzKga0oEfYTx4uchcAdGOK9w/zpSA8y6EwNNB
 TCnGd9WALGysfdM7024Y5fsWx3bkBgWGF67WrF4q14vviHO9S0HxRUMarZ8ZMdIW
 br7rZ5C+UgxmQCz70hdJJrPw6FW1ByULmfrOLCX/2Y4wT56nzYbaMKzNppBj3mbz
 klYANFu581SA/r81TjAvjrS8wJAPGfl6hrHRcC18igocgKOrRjDnFIjBUy6tVhQT
 DnZ+ms0p4WNvkK8rOmgVxP4jX7Ka8LLZdXccujX4pC7zVwwZwqpunixZhhV6sPJn
 OhKQLRE865RhSefs48h1
 =eb0R
 -END PGP SIGNATURE-
 }}}

--

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

[tor-bugs] #19845 [Internal Services/Tor Sysadmin Team]: Please create an LDAP account for Huy

[Tor Bug Tracker & Wiki]

#19845: Please create an LDAP account for Huy
-+-
 Reporter:  arlolra  |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512

 Huy is a GSoC participant this go around, working on CONIKS for Tor
 Messenger.
 We'd like to setup the developed CONIKS server on Tor infrastructure.

 For further information about the project, please see,
 https://github.com/coniks-sys/coniks-go
 https://trac.torproject.org/projects/tor/ticket/17961
 and the status updates on the tor-dev ml.


 First name: Quoc Huy
 Last name: Vu
 Desired uid: huyvq
 Forwarding address: huyvq.c...@gmail.com

 $ gpg --fingerprint 533191CEEC406DFF360D19DEC6202750C2FA740E
 pub   4096R/C2FA740E 2016-07-30 [expires: 2020-01-01]
   Key fingerprint = 5331 91CE EC40 6DFF 360D  19DE C620 2750 C2FA 740E
 uid   [  full  ] Vu Quoc Huy 
 sub   4096R/B88E95ED 2016-07-30 [expires: 2020-01-01]

 -BEGIN PGP SIGNATURE-

 iQIcBAEBCgAGBQJXpNV5AAoJEF46k7TU3c2L4moP/RT4KZ7E91uU/I9ZVIwBR+4p
 SLuMAX2Ys5a3reodBkzLUkb8pW1MLXCNPQPWRk/4nchIEptEC+6WceMM+AGnKJpi
 sOyXJbmotzE1OG9m6T9BcoTodU+5MKtv2qIVnC+V0/l/QTUJMpT8NUuL+k6ya2i6
 zykLyoR/dMOf83z94LpaKLVj+8Y7/8tuTjqcxGgQzm3qv9dSdw4eF5ywMoWPA6Vq
 mriOtnMM74M2VmtTJtF+sVUHn6YlY9Ve7x119VDyYd9TbikVCDlIkjAflh8r28Fl
 3tOYijVD4g1w/pmkSZC2wuMqhCQFoo+hdqFmSbM2cZsbM3t54jgoHg8R9BfZq9JC
 7LglaYs0S9PiLgqjY2MRVjV9MyQNzKga0oEfYTx4uchcAdGOK9w/zpSA8y6EwNNB
 TCnGd9WALGysfdM7024Y5fsWx3bkBgWGF67WrF4q14vviHO9S0HxRUMarZ8ZMdIW
 br7rZ5C+UgxmQCz70hdJJrPw6FW1ByULmfrOLCX/2Y4wT56nzYbaMKzNppBj3mbz
 klYANFu581SA/r81TjAvjrS8wJAPGfl6hrHRcC18igocgKOrRjDnFIjBUy6tVhQT
 DnZ+ms0p4WNvkK8rOmgVxP4jX7Ka8LLZdXccujX4pC7zVwwZwqpunixZhhV6sPJn
 OhKQLRE865RhSefs48h1
 =eb0R
 -END PGP SIGNATURE-

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

[tor-bugs] #19844 [- Select a component]: Prevent browser history leaks from CSS mix-blend-mode API in Tor Browser

[Tor Bug Tracker & Wiki]

#19844: Prevent browser history leaks from CSS mix-blend-mode API in Tor Browser
--+-
 Reporter:  isis  |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:  tbb-linkability
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 Similar to the old trick of querying the colour of a link on a page to see
 whether the user has visited that link before, there is
 [https://lcamtuf.blogspot.sk/2016/08/css-mix-blend-mode-is-bad-for-
 keeping.html a new form of this attack] which is made more efficient by
 querying the :visited attribute on a set of numerous links via defining a
 boolean algebra with the non-linear CSS blending operators in the
 [https://developer.mozilla.org/en-US/docs/Web/CSS/mix-blend-mode mix-
 blend-mode API].

 lcamtuf has [http://lcamtuf.coredump.cx/whack/ a demo of the attack] which
 works in my Tor Browser 6.0.3. We should determine a way to mitigate this
 attack.

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

Re: [tor-bugs] #16665 [Applications/Tor Browser]: Circuit visualizer needs a cue about guards

[Tor Bug Tracker & Wiki]

#16665: Circuit visualizer needs a cue about guards
-+-
 Reporter:  lunar|  Owner:  tbb-
 Type:  enhancement  |  team
 Priority:  Medium   | Status:
Component:  Applications/Tor Browser |  needs_revision
 Severity:  Normal   |  Milestone:
 Keywords:  tbb-usability, tbb-circuit-display,  |Version:
  TorBrowserTeam201603   | Resolution:
Parent ID:   |  Actual Points:
 Reviewer:   | Points:
 |Sponsor:
-+-

Comment (by dcf):

 Here are some blog comments by users confused by guards.

   https://blog.torproject.org/blog/tor-browser-55a5-hardened-
 released#comment-144848
   Is it normal or ok for Tor browser to maintain the same entry node all
 the time. I have noticed that my entry node has been persistently the same
 node (same ip address) no matter the time of day or if I request a new Tor
 server node. I find this troubling

   https://blog.torproject.org/blog/tor-browser-551-released#comment-155538
   Why do I connect using only the first node 88.198.9.16 !!! DEU!
   This can not be changed either by restarting or change of identity.
   Can I still trust?
   Ver .: Tor-Browser 5.5.1

   https://blog.torproject.org/blog/breaking-through-censorship-barriers-
 even-when-tor-blocked#comment-197050
   Since I installed the latest TOR update i get always connected to the
 same entry server in sweden whose ip is 155.4.59.251. Why is it so?

 I try to answer these questions by linking to
 https://www.torproject.org/docs/faq#EntryGuards, but IMO the FAQ does not
 explain the situation 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] #19823 [Core Tor/Stem]: pwd not available on Windows

[Tor Bug Tracker & Wiki]

#19823: pwd not available on Windows
---+
 Reporter:  trodun |  Owner:  atagar
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by atagar):

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


Comment:

 
[https://gitweb.torproject.org/stem.git/commit/?id=646bd2b9856e9b7a43e863ca5880ddd9ba846df3
 Fix pushed], thanks for the catch!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dcf):

 More information: https://blog.torproject.org/blog/tor-browser-
 65a2-released#comment-197036
   Image display also seems to be affected; I've only tried .jpg & .png so
 far.
   Image is on white/blank background, not centered & in the Inspector UI's
 CSS pane [Rules:element {shrinkToFit} does not seem to be available or is
 a bit wonky, in addition to other styles], no magnifying glass icon
 (however zoom does work).

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

Re: [tor-bugs] #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:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #19817| Points:
 Reviewer:|Sponsor:
--+---
Changes (by sukhbir):

 * cc: sukhbir (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] #19276 [Applications/Tor Browser]: Scrolling is slow and CPU intensive

[Tor Bug Tracker & Wiki]

#19276: Scrolling is slow and CPU intensive
-+-
 Reporter:  cypherpunks  |  Owner:  tbb-
 Type:  defect   |  team
 Priority:  Medium   | Status:
Component:  Applications/Tor Browser |  assigned
 Severity:  Normal   |  Milestone:
 Keywords:  tbb-6.0-issues, tbb-usability, tbb-  |Version:
  performance, GeorgKoppen201606,| Resolution:
  TorBrowserTeam201606   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 https://lists.torproject.org/pipermail/tor-talk/2016-August/041923.html

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

Re: [tor-bugs] #16016 [Core Tor/Tor]: extrainfo_insert(): Bug: No entry found in extrainfo map.

[Tor Bug Tracker & Wiki]

#16016: extrainfo_insert(): Bug: No entry found in extrainfo map.
-+--
 Reporter:  arma |  Owner:
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  PostFreeze027, 027-backport  |  Actual Points:
Parent ID:   | Points:  medium
 Reviewer:   |Sponsor:
-+--

Comment (by arma):

 {{{
 Aug 05 10:25:00.410 [info] router_load_extrainfo_from_string(): 13661
 elements to add
 Aug 05 10:25:00.410 [info] extrainfo_insert(): Bug: No entry found in
 extrainfo map. (on Tor 0.2.9.1-alpha c9b8d4c086931d80)
 Aug 05 10:25:00.474 [info] router_load_extrainfo_from_string(): 250
 elements to add
 }}}

 bug remains in 0.2.9.1-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] #19830 [Metrics/CollecTor]: Check if recent directory exists before checking available space

[Tor Bug Tracker & Wiki]

#19830: Check if recent directory exists before checking available space
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | 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 iwakeh):

 * priority:  Low => Medium


Comment:

 Increasing priority, so this floats near the top of the stack of reviews.

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

Re: [tor-bugs] #19776 [Metrics/CollecTor]: Make minor improvements to scheduler

[Tor Bug Tracker & Wiki]

#19776: Make minor improvements to scheduler
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  enhancement| Status:  needs_review
 Priority:  High   |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * priority:  Medium => High


Comment:

 Increasing priority, so this floats near the top of the stack of reviews.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  needs_review
 Priority:  High   |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * priority:  Medium => High


Comment:

 Increasing priority, so this floats near the top of the stack of reviews.

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

Re: [tor-bugs] #19843 [Metrics/Atlas]: Sorry. You are not using Tor.Your IP address appears to be: 108.61.122.139(new:108.61.122.70)

[Tor Bug Tracker & Wiki]

#19843: Sorry. You are not using Tor.Your IP address appears to be:
108.61.122.139(new:108.61.122.70)
+---
 Reporter:  108.61.122.139  |  Owner:  irl
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Metrics/Atlas   |Version:
 Severity:  Normal  | Resolution:  not a bug
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
Changes (by irl):

 * status:  new => closed
 * resolution:   => not a bug


Comment:

 This is certainly not a bug with Atlas, as you have screenshots of
 check.torproject.org. I can also tell you that the IP addresses that you
 have seen are not Tor exit relays, nor are they Tor relays at all, so this
 is also not a bug with check.torproject.org.

 This is most likely a problem with your local configuration.

 The Tor Trac is for tracking issues with the Tor software. Please find
 details of user support at:

 https://www.torproject.org/about/contact.html.en#support

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

Re: [tor-bugs] #19843 [Metrics/Atlas]: Sorry. You are not using Tor.Your IP address appears to be: 108.61.122.139(new:108.61.122.70) (was: Sorry. You are not using Tor.Your IP address appears to be: 1

[Tor Bug Tracker & Wiki]

#19843: Sorry. You are not using Tor.Your IP address appears to be:
108.61.122.139(new:108.61.122.70)
+-
 Reporter:  108.61.122.139  |  Owner:  irl
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Atlas   |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-

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

Re: [tor-bugs] #19843 [Metrics/Atlas]: Sorry. You are not using Tor.Your IP address appears to be: 108.61.122.139

[Tor Bug Tracker & Wiki]

#19843: Sorry. You are not using Tor.Your IP address appears to be: 
108.61.122.139
+-
 Reporter:  108.61.122.139  |  Owner:  irl
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Atlas   |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-

Comment (by 108.61.122.139):

 new
 
[[Image(https://trac.torproject.org/projects/tor/attachment/ticket/19843/tor108.61.122.70.png)]]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19843 [Metrics/Atlas]: Sorry. You are not using Tor.Your IP address appears to be: 108.61.122.139

[Tor Bug Tracker & Wiki]

#19843: Sorry. You are not using Tor.Your IP address appears to be: 
108.61.122.139
+-
 Reporter:  108.61.122.139  |  Owner:  irl
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Metrics/Atlas   |Version:
 Severity:  Normal  |   Keywords:
Actual Points:  |  Parent ID:
   Points:  |   Reviewer:
  Sponsor:  |
+-
 Sorry. You are not using Tor.
 Your IP address appears to be: 108.61.122.139
 https://check.torproject.org/?lang=en_US

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

Re: [tor-bugs] #19830 [Metrics/CollecTor]: Check if recent directory exists before checking available space

[Tor Bug Tracker & Wiki]

#19830: Check if recent directory exists before checking available space
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_review
 Priority:  Low|  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

 * status:  accepted => needs_review


Comment:

 Please review
 [https://gitweb.torproject.org/user/iwakeh/collector.git/commit/?h=task-19830
 my branch].

 Solution:
 Now check the root of given path. That should always exist and be
 accessible. Any IOException here is a major problem and escalated via
 RuntimeException.

 Added test for the problem and added some necessary test permissions.

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

Re: [tor-bugs] #19839 [Obfuscation/BridgeDB]: BridgeDB website: German translation could be improved (and completed)

[Tor Bug Tracker & Wiki]

#19839: BridgeDB website: German translation could be improved (and completed)
--+--
 Reporter:  sebalis   |  Owner:  isis
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Obfuscation/BridgeDB  |Version:
 Severity:  Normal| Resolution:
 Keywords:  bridgedb-reportbug|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sebalis):

 Replying to [comment:2 isis]:
 > Hi! That's odd that the headlines were in English. Do you mean the text
 in  (etc.) tags, or also the text in the titlebar/menubar of
 Firefox? As you mentioned, using Tor Browser, I also get all German or all
 English, depending on my language settings.

 I mean the text in  tags on https://bridges.torproject.org/,
 https://bridges.torproject.org/options and
 https://bridges.torproject.org/howto – I’ve seen one h3 tag with German
 content, no h2 or h1.

 It does seem to depend on my language preferences in Firefox. Using a
 fresh profile (and as I said, my Firefox itself is en-US and the OS is
 English too) and its default language preferences, which are to 1. en-US,
 2. en, I get all English content. Changing to 1. en, 2. de as mentioned
 before gives me what I’m describing here: h4 content is English, body text
 German.

 > As for improving the German, we use
 [https://www.transifex.com/projects/p/torproject/resource/2-bridgedb-
 bridgedb-pot/ Transifex], and I'm happy to figure out how to get you an
 account there. I'm also happy to take suggestions here and put them into
 Transifex for you. (Und ja auch kann ich irgenwie deutsch sprechen…
 zumeist. Die aktuelle Übersetzung ist vielleicht ein bisschen schade, aber
 auch ist sie nicht meine Muttersprache. :)

 Massive respect for the effort! The text is very good already, looking
 closer I think I would have very little to suggest. I’d regard Bug #19841
 as more important, adding a switcher and solving the mixed content puzzle.
 But if you get me an account on Transifex I will devote some time to the
 German content as well. (At the moment surfing to the Transifex link gives
 me a 403 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] #19839 [Obfuscation/BridgeDB]: BridgeDB website: German translation could be improved (and completed)

[Tor Bug Tracker & Wiki]

#19839: BridgeDB website: German translation could be improved (and completed)
--+--
 Reporter:  sebalis   |  Owner:  isis
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Obfuscation/BridgeDB  |Version:
 Severity:  Normal| Resolution:
 Keywords:  bridgedb-reportbug|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by isis):

 * component:  User Experience/Website => Obfuscation/BridgeDB


Comment:

 Replying to [ticket:19839 sebalis]:
 > Browsing to https://bridges.torproject.org/ from Germany using an
 English Firefox, I am served a page that shows headlines in English, but
 the rest (as far as I checked) is in German. The German text is not bad
 but should be improved in some places as it seems too close to the English
 original with some incorrect translation choices. As a native speaker and
 also long-standing translator/interpreter for Digitalcourage and the CCC
 I’d be happy to help.

 Hi! That's odd that the headlines were in English. Do you mean the text in
  (etc.) tags, or also the text in the titlebar/menubar of
 Firefox? As you mentioned, using Tor Browser, I also get all German or all
 English, depending on my language settings.

 As for improving the German, we use
 [https://www.transifex.com/projects/p/torproject/resource/2-bridgedb-
 bridgedb-pot/ Transifex], and I'm happy to figure out how to get you an
 account there. I'm also happy to take suggestions here and put them into
 Transifex for you. (Und ja auch kann ich irgenwie deutsch sprechen…
 zumeist. Die aktuelle Übersetzung ist vielleicht ein bisschen schade, aber
 auch ist sie nicht meine Muttersprache. :)

 > (And since this ticket will apparently be “owned” by Isis, I’d like to
 add that I’m hugely looking forward to being her interpreter for her
 upcoming talk at Digitalcourage’s “Public Domain” event. ☺)

 Voll knorke!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 LenientParser ticket #19842

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19842 [Metrics/metrics-lib]: offer a `LenientParser` option with metrics-lib

[Tor Bug Tracker & Wiki]

#19842: offer a `LenientParser` option with metrics-lib
-+-
 Reporter:  iwakeh   |  Owner:  karsten
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Provide another parser option, quote from #19170#comment:7

   make use of the `descriptor.parser` and `descriptor.reader` properties
 and supply a different non-ascci-accepting parser, let's call it
 `LenientParser`, as well as a LenientReader.

 * Necessary change in CollecTor would be to set the `descriptor.parser`
 and `descriptor.reader` properties to the LenientParser class.
 * Necessary change in metrics-lib would be the addition of the
 LenientParser, which consist mostly in providing additional ParserHelper
 methods that accept non-ascii and calling these in the appropriate places;
 most of the code will be the same as in the current, stricter
 implementation.  Also a LenientReader would have to be supplied.

 That way we could switch between implementations.
 Users of metrics-lib would also have another option.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 The patch doesn't correct the extra-info descriptor part
 
[https://gitweb.torproject.org/collector.git/tree/src/main/java/org/torproject/collector/relaydescs/RelayDescriptorParser.java#n272
 here and below] (afaict)?

 `logger` should be accessed in a static way; currently all access to
 `logger` are done like `this.logger`.  Maybe, just include this minor
 change in the patch?

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

Re: [tor-bugs] #19833 [Applications]: torsocks-2.2.0-rc1 segfaults emacs(notmuch) and git

[Tor Bug Tracker & Wiki]

#19833: torsocks-2.2.0-rc1 segfaults emacs(notmuch) and git
--+-
 Reporter:  ng0   |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications  |Version:
 Severity:  Normal| Resolution:
 Keywords:  torsocks  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by ng0):

 Update: the my.pb.pb function (which torifies curl) fails too.

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

Re: [tor-bugs] #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:  needs_review
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by karsten):

 * status:  accepted => needs_review


Comment:

 Replying to [comment:14 iwakeh]:
 > Replying to [comment:13 karsten]:
 > > Alright, I sent a [https://lists.torproject.org/pipermail/tor-
 dev/2016-August/011271.html heads-up to tor-dev@].
 >
 > Good, nice warning mail.

 Thanks. :)

 > > Should I make this change, or would you want to do that?
 >
 > Please do.

 Sure, please find [https://gitweb.torproject.org/karsten/metrics-
 db.git/log/?h=task-19170 my branch task-19170].

 > > Let's postpone the LenientParser discussion, as I'd also want to make
 unrelated changes to the parser, including making it lazy for performance
 reasons.  And we'd want to include signature verification at some point.
 But that's all for later.
 >
 > That's fine.

 Can you create a ticket for this, so we don't forget?

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

Re: [tor-bugs] #18513 [Applications/Tor Browser]: New Identity bypass

[Tor Bug Tracker & Wiki]

#18513: New Identity bypass
+--
 Reporter:  tahuttun|  Owner:  tbb-team
 Type:  defect  | Status:  new
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Major   | Resolution:
 Keywords:  tbb-newnym, ff45-esr-will-have  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by cypherpunks):

 is this closed?

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

Re: [tor-bugs] #19840 [Metrics/CollecTor]: Change path defaults to match those of main CollecTor instance

[Tor Bug Tracker & Wiki]

#19840: Change path defaults to match those of main CollecTor instance
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

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


Comment:

 Task added to #18734.

 All done here.
 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] #18734 [Metrics/CollecTor]: Installation Guide for Operators

[Tor Bug Tracker & Wiki]

#18734: Installation Guide for Operators
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  task   | Status:  accepted
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 Also add explanation for path settings in collector.properties (cf.
 #19840)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 Replying to [comment:13 karsten]:
 > Alright, I sent a [https://lists.torproject.org/pipermail/tor-
 dev/2016-August/011271.html heads-up to tor-dev@].

 Good, nice warning mail.

 >
 > Should I make this change, or would you want to do that?

 Please do.

 >
 > Let's postpone the LenientParser discussion, as I'd also want to make
 unrelated changes to the parser, including making it lazy for performance
 reasons.  And we'd want to include signature verification at some point.
 But that's all for later.

 That's fine.

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

Re: [tor-bugs] #19840 [Metrics/CollecTor]: Change path defaults to match those of main CollecTor instance

[Tor Bug Tracker & Wiki]

#19840: Change path defaults to match those of main CollecTor instance
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | 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:   => iwakeh
 * status:  needs_review => assigned


Comment:

 Great, thanks for looking!  Pushed to master and leaving open for the
 operator guide update.

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

Re: [tor-bugs] #19805 [Internal Services/Tor Sysadmin Team]: provide more onion services

[Tor Bug Tracker & Wiki]

#19805: provide more onion services
-+-
 Reporter:  ilf  |  Owner:  tpa
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by ilf):

 Thanks for following up on this.

 Instead of me scraping for your servers, there must be a list of
 Torproject servers somewhere? DNS? Or this?
 https://db.torproject.org/machines.cgi

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: 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:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ctip   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by karsten):

 Alright, I sent a [https://lists.torproject.org/pipermail/tor-
 dev/2016-August/011271.html heads-up to tor-dev@].

 Should I make this change, or would you want to do that?

 Let's postpone the LenientParser discussion, as I'd also want to make
 unrelated changes to the parser, including making it lazy for performance
 reasons.  And we'd want to include signature verification at some point.
 But that's all for later.

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

Re: [tor-bugs] #19776 [Metrics/CollecTor]: Make minor improvements to scheduler

[Tor Bug Tracker & Wiki]

#19776: Make minor improvements to scheduler
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  enhancement| 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):

 part 1: solved in #19840.
 part 2: see #19720.

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

Re: [tor-bugs] #19840 [Metrics/CollecTor]: Change path defaults to match those of main CollecTor instance

[Tor Bug Tracker & Wiki]

#19840: Change path defaults to match those of main CollecTor instance
---+-
 Reporter:  karsten|  Owner:
 Type:  defect | 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):

 Looks ok.  I reference the directory fix in #19776.

 I think we need an explanation for the various paths configured.  will add
 this to the upcoming operator guide.

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

Re: [tor-bugs] #19841 [User Experience/Website]: BridgeDB website: surprising choices and no language switcher

[Tor Bug Tracker & Wiki]

#19841: BridgeDB website: surprising choices and no language switcher
-+--
 Reporter:  sebalis  |  Owner:  isis
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bridgedb-reportbug   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by sebalis):

 Given that using the Tor Browser I see content that is either fully
 English or fully German, it really seems very surprising that I should see
 mixed content when using my regular Firefox profile. The language
 preferences I have set in that profile are English (en) first, German (de)
 second.

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

Re: [tor-bugs] #19839 [User Experience/Website]: BridgeDB website: German translation could be improved (and completed)

[Tor Bug Tracker & Wiki]

#19839: BridgeDB website: German translation could be improved (and completed)
-+--
 Reporter:  sebalis  |  Owner:  isis
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bridgedb-reportbug   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by sebalis):

 During some further investigation for reporting bug #19841 I found that
 the headlines have been translated to German too, but these translations
 were not served to me. Using the Tor Browser I either get a fully English
 or fully German page depending on my language choices. Anyway, I can
 submit suggestions for some (very small) language changes using any
 channel you prefer. However I will not be online a lot until 19 Aug.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19841 [User Experience/Website]: BridgeDB website: surprising choices and no language switcher

[Tor Bug Tracker & Wiki]

#19841: BridgeDB website: surprising choices and no language switcher
-+
 Reporter:  sebalis  |  Owner:  isis
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   |   Keywords:  bridgedb-reportbug
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 Browsing to https://bridges.torproject.org/ from Germany using an English
 Firefox, I am served a page that shows headlines in English, but the rest
 (as far as I checked) is in German. This language choice is surprising to
 me as I think the browser’s language as transmitted in the HTTP headers
 should be the main factor. Strangely, using the Tor Browser and declining
 the question whether I want to request English content for improved
 anonymity, I get a page that is fully German despite my exit node being in
 the UK, so geolocating can not be the sole criterion for this language
 choice either. This might become a problem because the website does not
 seem to offer a means for switching the language.

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

Re: [tor-bugs] #19840 [Metrics/CollecTor]: Change path defaults to match those of main CollecTor instance

[Tor Bug Tracker & Wiki]

#19840: Change path defaults to match those of main CollecTor instance
---+-
 Reporter:  karsten|  Owner:
 Type:  defect | 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:  new => needs_review


Comment:

 Please review the last two commits in
 [https://gitweb.torproject.org/karsten/metrics-db.git/log/?h=task-19840 my
 branch task-19840].  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

[tor-bugs] #19840 [Metrics/CollecTor]: Change path defaults to match those of main CollecTor instance

[Tor Bug Tracker & Wiki]

#19840: Change path defaults to match those of main CollecTor instance
---+-
 Reporter:  karsten|  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+-
 We discussed this elsewhere, but I can't find where.  Too many active
 tickets...

 We should change the defaults for the following paths to match the values
 of the main CollecTor instance:

 {{{
 IndexPath = out/index -> .
 ArchivePath = out/archive -> archive
 RecentPath = out/recent -> recent
 StatsPath = out/stats -> stats
 }}}

 Note that the `out/` directory is already used for storing files
 containing single descriptors that will be tar'ed later.

 I also found a bug in the exit list downloader that I'm fixing here.

 I'll push 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] #19836 [Metrics/CollecTor]: Prepare relay descriptor downloader for consensuses published at :30 of the hour

[Tor Bug Tracker & Wiki]

#19836: Prepare relay descriptor downloader for consensuses published at :30 of 
the
hour
---+-
 Reporter:  karsten|  Owner:
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by karsten):

 Replying to [comment:1 iwakeh]:
 > Replying to [ticket:19836 karsten]:
 > > Consensuses have always been published once per hour, so with valid-
 after time :00 in the past.  This might change in the future, as has been
 discussed in the context of consensus diffs, but which might also happen
 independent of those.
 > >
 > > However, CollecTor is not ready for such a change, because
 `currentValidAfter` in `RelayDescriptorDownloader` is always initialized
 with :00 of the hour.  This would prevent us from accepting a consensus
 published at :30.  Of course, when we make such a change we should also
 accept other valid-after times that :00 and :30.
 >
 > Is :30 just an example or will there always be a set of valid values
 like for example {30,00,25}?

 Quoting from dir-spec.txt:

 {{{
Authorities divide time into Intervals.  Authority administrators
 SHOULD
try to all pick the same interval length, and SHOULD pick intervals
 that
are commonly used divisions of time (e.g., 5 minutes, 15 minutes, 30
minutes, 60 minutes, 90 minutes).  Voting intervals SHOULD be chosen to
divide evenly into a 24-hour day.
 }}}

 > > Testing a fix might require setting up a testing network using Chutney
 and archiving network data produced by that.  That is, we could also
 create a testing environment and write unit tests for this, which we
 should do anyway.  But that shouldn't block us here, unless the fix is
 more complex than I currently anticipate.
 >
 > I think, the testing should be doable by (j)unit tests.
 > The (system) test environment using Chutney or similar might be useful
 in general, but should not be necessary here.

 Okay.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19839 [User Experience/Website]: BridgeDB website: German translation could be improved (and completed)

[Tor Bug Tracker & Wiki]

#19839: BridgeDB website: German translation could be improved (and completed)
-+
 Reporter:  sebalis  |  Owner:  isis
 Type:  defect   | Status:  new
 Priority:  Low  |  Milestone:
Component:  User Experience/Website  |Version:
 Severity:  Normal   |   Keywords:  bridgedb-reportbug
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+
 Browsing to https://bridges.torproject.org/ from Germany using an English
 Firefox, I am served a page that shows headlines in English, but the rest
 (as far as I checked) is in German. The German text is not bad but should
 be improved in some places as it seems too close to the English original
 with some incorrect translation choices. As a native speaker and also
 long-standing translator/interpreter for Digitalcourage and the CCC I’d be
 happy to help. (And since this ticket will apparently be “owned” by Isis,
 I’d like to add that I’m hugely looking forward to being her interpreter
 for her upcoming talk at Digitalcourage’s “Public Domain” event. ☺)

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

Re: [tor-bugs] #19836 [Metrics/CollecTor]: Prepare relay descriptor downloader for consensuses published at :30 of the hour

[Tor Bug Tracker & Wiki]

#19836: Prepare relay descriptor downloader for consensuses published at :30 of 
the
hour
---+-
 Reporter:  karsten|  Owner:
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 Replying to [ticket:19836 karsten]:
 > Consensuses have always been published once per hour, so with valid-
 after time :00 in the past.  This might change in the future, as has been
 discussed in the context of consensus diffs, but which might also happen
 independent of those.
 >
 > However, CollecTor is not ready for such a change, because
 `currentValidAfter` in `RelayDescriptorDownloader` is always initialized
 with :00 of the hour.  This would prevent us from accepting a consensus
 published at :30.  Of course, when we make such a change we should also
 accept other valid-after times that :00 and :30.

 Is :30 just an example or will there always be a set of valid values like
 for example {30,00,25}?

 >
 > Testing a fix might require setting up a testing network using Chutney
 and archiving network data produced by that.  That is, we could also
 create a testing environment and write unit tests for this, which we
 should do anyway.  But that shouldn't block us here, unless the fix is
 more complex than I currently anticipate.

 I think, the testing should be doable by (j)unit tests.
 The (system) test environment using Chutney or similar might be useful in
 general, but should not be necessary here.

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

Re: [tor-bugs] #13419 [Applications/Tor Browser]: Fix cross-compiling ICU with mingw-w64 for Windows builds

[Tor Bug Tracker & Wiki]

#13419: Fix cross-compiling ICU with mingw-w64 for Windows builds
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:  fixed
 Keywords:  tbb-gitian, GeorgKoppen201604,   |  Actual Points:
  TorBrowserTeam201604R, ff45-esr, tbb-6.0a5 | Points:
Parent ID:   |Sponsor:
 Reviewer:   |
-+-

Comment (by msdobrescu):

 Hi, I came across this by searching to fix a SpiderMonkey build under
 Windows with MinGW64 using mozilla build tools.
 It still doesn't build as it creates libs like 'libX.dll.a'. I've managed
 to find where to name them 'libX.a', but still 'libX56.a' is needed, where
 56 is the major version of ICU.
 IMHO, it is not yet fixed in this case.

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

Re: [tor-bugs] #19829 [Metrics/CollecTor]: Update directory authority addresses to recent tor.git

[Tor Bug Tracker & Wiki]

#19829: Update directory authority addresses to recent tor.git
---+-
 Reporter:  karsten|  Owner:
 Type:  enhancement| Status:  closed
 Priority:  High   |  Milestone:  CollecTor 1.0.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by karsten):

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


Comment:

 There, I just pushed a fix to master.  If you find a mistake in the
 update, please reopen!  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] #19776 [Metrics/CollecTor]: Make minor improvements to scheduler

[Tor Bug Tracker & Wiki]

#19776: Make minor improvements to scheduler
---+-
 Reporter:  karsten|  Owner:  iwakeh
 Type:  enhancement| 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 iwakeh):

 * status:  assigned => needs_review


Comment:

 Please review
 [https://gitweb.torproject.org/user/iwakeh/collector.git/commit/?h=task-19791
 -seconds-to-zero=160e1b437f017eef67036e82bbd01ae5b0b8e84d my branch].
 It contains the patch for 3, the HH.mm:00 part.
 The milliseconds are not easily set to zero, b/c the scheduler seems to
 take time to schedule a task.
 When the period is already running the start happens immediately, i.e.
 10:10:03 with period 2 and offset 0 the task will be started at 10:10:03.
 I didn't find a better solution here, will this suffice?


 Regarding part 4:
 It fits into the current design, but I rather have new properties instead
 of a command line switch. That way all settings are in one file, which
 helps with (remote) debugging.  Will that do?

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