[tor-bugs] #29128 [Core Tor/Tor]: Place complete obfs4 bridge line in accessible location

[Tor Bug Tracker & Wiki]

#29128: Place complete obfs4 bridge line in accessible location
--+
 Reporter:  phoul |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Currently operators wanting to distribute or use personal obfs4 bridges
 must follow 5 steps:

 1. Determine their bridge's IP address
 2. Check logs for their bridge's fingerprint
 3. Check logs for which port obfs4 is running on
 4. Retrieve their obfs4 cert from
 /var/lib/tor/pt_state/obfs4_bridgeline.txt
 5. String the above together in the following format:

 {{{
 Bridge obfs4 :  cert=$FROMSTEP4 iat-mode=0
 }}}

 This can be a confusing process, and is only fully explained upon opening
 `/var/lib/tor/pt_state/obfs4_bridgeline.txt`; however it leaves filling in
 the fields (with the exception of the cert) to the user.

 Having the complete bridge line placed somewhere accessible would make
 this process much less painful for operators.

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

Re: [tor-bugs] #29120 [Applications/Tor Browser]: Default value of media.cache_size (0) causes some media to load extremely slowly or become unplayable

[Tor Bug Tracker & Wiki]

#29120: Default value of media.cache_size (0) causes some media to load 
extremely
slowly or become unplayable
--+--
 Reporter:  QZw2aBQoPyuEVXYVlBps  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by QZw2aBQoPyuEVXYVlBps):

 * priority:  Medium => High


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

Re: [tor-bugs] #29120 [Applications/Tor Browser]: Default value of media.cache_size (0) causes some media to load extremely slowly or become unplayable

[Tor Bug Tracker & Wiki]

#29120: Default value of media.cache_size (0) causes some media to load 
extremely
slowly or become unplayable
--+--
 Reporter:  QZw2aBQoPyuEVXYVlBps  |  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 QZw2aBQoPyuEVXYVlBps):

 I've narrowed down the criteria for when this bug happens. It will trigger
 for any video played using the built in media player ({{{}}}) that's filesize is either greater than
 {{{media.memory_cache_max_size}}} (default 8192kb) or unknown (no
 {{{Content-Length}}}).

 I've also established that setting {{{media.cache_size}}} to 0 does
 ''not'' eliminate writing the cache to disk, it simply limits the cache
 file on disk to a few hundred kilobytes and constantly cycles it. Due to
 the nature of how physical storage mediums work, this is likely to be
 functionally equivalent to writing the entire cache to disk without all
 the nonsense inbetween.

 You can observe this yourself with the following command: {{{inotifywait
 -me modify,create,delete,move -r /tmp/ | grep mozilla}}}
 If you open the link in the first post in Tor Browser, you should start
 seeing mozilla temporary files being written to, this is the disk-backed
 MediaCache.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29127 [Internal Services/Tor Sysadmin Team]: Please create email alias and LDAP for new dev

[Tor Bug Tracker & Wiki]

#29127: Please create email alias and LDAP for new dev
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA512



 Please create email alias/forwarding and LDAP for our new dev:

 Name: Cecylia
 Desired uid/email alias: cohosh
 Forwarding email address: coh...@riseup.net
 PGP key: 5A61 8CE8 4088 3942 BAF1  334F 009D E379 FD9B 7B90

 Thank you!

 -BEGIN PGP SIGNATURE-
 Comment: GPGTools - https://gpgtools.org

 iQIzBAEBCgAdFiEENecqn2ZVRfkstmYkugyUAPgPkc4FAlxCo8UACgkQugyUAPgP
 kc5drxAAlIzOpsQEHUnPVjsW5HejOtwH9MvEGTP528DmTXwsH60z/nVmkCu/sTbZ
 t9YovkNb73KDV4e0Nr3v0wRfeetA36jrGOK/o5WGD7+gMJkPkndtc1hSwVc9zQ6w
 3Z4RBfkorcOSPwmyVoQVzdh2aIlqXpi3SzUNlvV9HV2RvBwsfH1POYg4k/14OW2x
 4HMzgnq9aMSSTsl4qbl2Vl53sNYyPPzO1A9cX+GD0cdhBIxnUqYTKUC/fVNIEuP+
 lSueBolqKv8pNp/ZNbW05xpgbYf5cAauH46vxuXiglTM2pXfjMYx/1RnBpNmix/+
 zC/GIPN3L51zdjX7ajJEmuRb1Nb8PPcDgouBuP18hB6lZ9dQTu/9v2bxJ6TH0d2a
 s1h7VdZ4T9mgRyI9FjIsQPma9tfdQUjWuZup9ZiOWfpCFs1fJeJRl86V8rchK7nQ
 H0/G+LfeX9mrQQrQUVX7B961eND9byHKJ411kiqme6obH9y59gHhe3l1HE9mLhn1
 sZu4YnlgEdCcROYo/9vWa+EFariiqbundabRgs5WOmVulTmUAtJLgoG8ZvauTX7N
 wY3AgoLaksm/4t8vpnaJ4N5JJ1pjNz9GyOO+I1qAnc+hAHMbuxXsMvkRdLfZZeUa
 0Jq70JgjD7NwdETzOQGZ+icoCyD9x/emXEehlHEklKp6InMdZdQ=
 =SHe1
 -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

Re: [tor-bugs] #28960 [Applications/Tor Browser]: Tor Browser 8 does not support legacy OS like Win2000, WinXP

[Tor Bug Tracker & Wiki]

#28960: Tor Browser 8 does not support legacy OS like Win2000, WinXP
--+--
 Reporter:  nigger_from_africa|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  wontfix
 Keywords:  CIA   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by pospeselr):

 * status:  reopened => closed
 * resolution:   => wontfix
 * sponsor:  Sponsor3 =>


Comment:

 If you could stop messing with our bug tracker that'd be great.

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

Re: [tor-bugs] #28960 [Applications/Tor Browser]: Tor Browser 8 does not support legacy OS like Win2000, WinXP

[Tor Bug Tracker & Wiki]

#28960: Tor Browser 8 does not support legacy OS like Win2000, WinXP
--+--
 Reporter:  nigger_from_africa|  Owner:  tbb-team
 Type:  defect| Status:  reopened
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  CIA   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  Sponsor3
--+--
Changes (by nigger_from_africa):

 * status:  closed => reopened
 * resolution:  wontfix =>
 * sponsor:   => Sponsor3


Comment:

 >We won't do either of those.
 Why not?
 You have to do it, it's your duty. Otherwise, it means you are owned by
 CIA.

 Or maybe Tor is not for journalists and whistleblowers in 3rd world, but
 it is a toy for rich white pedophiles from 1st world countries?

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

Re: [tor-bugs] #27471 [Core Tor/Tor]: HS intermittently fails: Non-fatal assertion failed in send_introduce1

[Tor Bug Tracker & Wiki]

#27471: HS intermittently fails: Non-fatal assertion failed in send_introduce1
+--
 Reporter:  tgragnato   |  Owner:  dgoulet
 Type:  defect  | Status:
|  merge_ready
 Priority:  Very High   |  Milestone:  Tor:
|  0.3.4.x-final
Component:  Core Tor/Tor|Version:  Tor:
|  0.3.2.1-alpha
 Severity:  Minor   | Resolution:
 Keywords:  tor-hs, 035-backport, 034-backport  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  asn |Sponsor:
+--

Comment (by asan):

 Replying to [comment:31 nickm]:
 > Merged to 0.3.5
 The ticket is still in //merge_ready// state. Is this patch already
 applied in recently released 0.3.5.7 or 0.4.0.1-alpha? If yes, and you
 don't have plans to backport it, we should mark it as resolved.

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

Re: [tor-bugs] #29097 [Applications/Tor Browser]: https-everywhere make.sh explicitly depends on missing python 3.6

[Tor Bug Tracker & Wiki]

#29097: https-everywhere make.sh explicitly depends on missing python 3.6
--+--
 Reporter:  pospeselr |  Owner:  boklm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201901R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by pospeselr):

 Replying to [comment:3 boklm]:
 > What is the error that you get?
 >
 > Is it because the `python3` package in buster was previously installing
 python 3.6, but now they changed it to 3.7?

 Yep that's exactly the issue.

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

Re: [tor-bugs] #29078 [Core Tor/Nyx]: nyx values do differ from stem native example

[Tor Bug Tracker & Wiki]

#29078: nyx values do differ from stem native example
--+--
 Reporter:  toralf|  Owner:  atagar
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:  Tor: 0.3.5.7
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by atagar):

 Hi toralf. Nope, none of my systems have such high connection load.

 I'd rather not put further time into speculation. If you have a problem I
 can reproduce locally I'm happy to take a peek but otherwise I'll need to
 go with 'patches welcome'.

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

Re: [tor-bugs] #29078 [Core Tor/Nyx]: nyx values do differ from stem native example

[Tor Bug Tracker & Wiki]

#29078: nyx values do differ from stem native example
--+--
 Reporter:  toralf|  Owner:  atagar
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:  Tor: 0.3.5.7
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by toralf):

 Hhm, might be the bug is lcoal specific, but...
 Did you tried to reproduced the bug at your system with a number of
 connection >  ?

 IIRC there was a bug in parsing 5-digit numbers of connection lists in an
 example script 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] #29078 [Core Tor/Nyx]: nyx values do differ from stem native example

[Tor Bug Tracker & Wiki]

#29078: nyx values do differ from stem native example
--+--
 Reporter:  toralf|  Owner:  atagar
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:  Tor: 0.3.5.7
 Severity:  Normal| Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by atagar):

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


Comment:

 Gotcha, thanks toralf.

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

Re: [tor-bugs] #29078 [Core Tor/Nyx]: nyx values do differ from stem native example

[Tor Bug Tracker & Wiki]

#29078: nyx values do differ from stem native example
--+---
 Reporter:  toralf|  Owner:  atagar
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:  Tor: 0.3.5.7
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by toralf):

 Seems that counting works for every resolver long as I do pause nyx and
 choose any resolver and do continue.

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

Re: [tor-bugs] #28615 [Metrics/Library]: Additional @type annotation

[Tor Bug Tracker & Wiki]

#28615: Additional @type annotation
-+--
 Reporter:  atagar   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by atagar):

 * cc: teor, juga (added)


Comment:

 > What do you suggest as @type annotation for bandwidth files?

 Perfect question, and something I intentionally neglected to mention
 because I don't know for certain. The spec uses the terms 'bandwidth file'
 or 'bandwidth list', and in Stem I opted to call the class a
 BandwidthMetric. Adding juga and teor to this ticket to see if they have
 an opinion on which they want...

 {{{
 @type bandwidth 1.2
 @type bandwidth-file 1.2
 @type bandwidth-list 1.2
 @type bandwidth-metric 1.2
 }}}

 **juga, teor: any preference on which of the above you like best?**

 For what it's worth a couple other things worth noting...

 * juga mentioned adding these to CollecTor, so the addition of a @type
 annotation of it will probably be of particular interest to you soon as
 well.
 * Bandwidth files already have multiple versions. According to #29056
 these documents have versions 1.0, 1.1, and 1.2 (not to be confused with
 software versions, which are moot for this ticket and include torflow,
 sbws 0.1.0, sbws 1.0.0, and sbws 1.0.3).

 > @type detached-signature 1.0 seems plausible to me. Let's add it.

 Great!

 > Oh, and I wonder if @type network-status-entry-3 1.0 would be more
 consistent with the consensus and vote equivalents, what do you think?

 Sure, fine with me. I don't mind what the name is and '@type network-
 status-entry-3' sounds fine.

 > The unflavored or the microdesc-flavored entry?

 Good question, and one that previously caused quite a bit of confusion. My
 understanding is that the answer is **unflavored**...

 https://gitweb.torproject.org/stem.git/commit/?id=136537c
 https://trac.torproject.org/projects/tor/ticket/24110

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

Re: [tor-bugs] #25702 [Applications/Tor Browser]: Activity 1.1 Update Tor Browser icon to follow design guidelines.

[Tor Bug Tracker & Wiki]

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

 * keywords:  ux-team, tbb-mobile, TorBrowserTeam201901 => ux-team, tbb-
 mobile, TorBrowserTeam201901R
 * status:  needs_revision => needs_review


Comment:

 Ok, reverted change to official's brand.ftl, removed tor-watermark.svg's
 metadata, fixed some of the border weirdness in the alpha and nightly
 svg's and regenerated icons (and updated icons in #28546)

 torbutton:
 
​https://gitweb.torproject.org/user/richard/torbutton.git/commit/?h=bug_25702_v2=6a69d724bee840e2281d907a3dd48b794b724337

 tor-browser (squashed and rebased):
 ​https://gitweb.torproject.org/user/richard/tor-
 browser.git/commit/?h=bug_25702_v3

 tor-browser-build (rebased): https://gitweb.torproject.org/user/richard
 /tor-browser-
 build.git/commit/?h=bug_25702=9965e0710f5f5a78a5a8b0961c5cc10a8454d00b

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

Re: [tor-bugs] #28615 [Metrics/Library]: Additional @type annotation

[Tor Bug Tracker & Wiki]

#28615: Additional @type annotation
-+--
 Reporter:  atagar   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 One thing that comes to mind is NASA's ontology of units. They have a
 number of units defined that wouldn't make any sense on their own, but
 they are found in intermediate steps of solving equations. If we begin
 moving to big data stream/batch processing with databases and object
 stores then we are likely to find ourselves with individual entries that
 are stored on disk as objects or in databases independently of the network
 status document they came from.

 I believe for bandwidth files they should be "bandwidth-list" to use the
 same terminology as the spec. The spec filename is "bandwidth file" but
 the actual content of it calls them "lists".

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

Re: [tor-bugs] #29050 [Community/Tor Support]: Connecting to tor over a socks 5 connection no longer works in 3.5.7

[Tor Bug Tracker & Wiki]

#29050: Connecting to tor over a socks 5 connection no longer works in 3.5.7
---+---
 Reporter:  arj|  Owner:  dgoulet
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Community/Tor Support  |Version:  Tor: 0.3.5.7
 Severity:  Normal | Resolution:
 Keywords:  regression?|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by arj):

 This is default tor config on a debian machine.

 torsocks seems to work both with -u & -p and without, here is log without:

 547843375 DEBUG torsocks[16768]: Logging subsystem initialized. Level 5,
 file (null), time 1 (in init_logging() at torsocks.c:304)
 1547843375 DEBUG torsocks[16768]: Config file not provided by
 TORSOCKS_CONF_FILE. Using default /etc/tor/torsocks.conf (in
 config_file_read() at config-file.c:543)
 1547843375 DEBUG torsocks[16768]: Config file setting tor address to
 127.0.0.1 (in conf_file_set_tor_address() at config-file.c:298)
 1547843375 DEBUG torsocks[16768]: Config file setting tor port to 9050 (in
 conf_file_set_tor_port() at config-file.c:254)
 1547843375 DEBUG torsocks[16768]: [config] Onion address range set to
 127.42.42.0/24 (in set_onion_info() at config-file.c:108)
 1547843375 DEBUG torsocks[16768]: Config file /etc/tor/torsocks.conf
 opened and parsed. (in config_file_read() at config-file.c:572)
 1547843375 DEBUG torsocks[16768]: [fclose] Close caught for fd 3 (in
 tsocks_fclose() at fclose.c:45)
 1547843375 DEBUG torsocks[16768]: Config file setting tor port to 9050 (in
 conf_file_set_tor_port() at config-file.c:254)
 1547843375 DEBUG torsocks[16768]: [onion] Pool init with subnet
 127.42.42.0 and mask 24 (in onion_pool_init() at onion.c:104)
 1547843375 DEBUG torsocks[16768]: [onion] Pool initialized with base 0,
 max_pos 255 and size 8 (in onion_pool_init() at onion.c:132)
 1547843375 DEBUG torsocks[16768]: [fclose] Close caught for fd 3 (in
 tsocks_fclose() at fclose.c:45)
 --2019-01-18 21:29:35--  https://www.google.com./
 1547843375 DEBUG torsocks[16768]: [fclose] Close caught for fd 3 (in
 tsocks_fclose() at fclose.c:45)
 1547843375 DEBUG torsocks[16768]: [close] Close caught for fd 3 (in
 tsocks_close() at close.c:33)
 1547843375 DEBUG torsocks[16768]: [fclose] Close caught for fd 3 (in
 tsocks_fclose() at fclose.c:45)
 Resolving www.google.com. (www.google.com.)... 1547843375 DEBUG
 torsocks[16768]: [getaddrinfo] Requesting www.google.com. hostname (in
 tsocks_getaddrinfo() at getaddrinfo.c:44)
 1547843375 DEBUG torsocks[16768]: Resolving www.google.com. on the Tor
 network (in tsocks_tor_resolve() at torsocks.c:545)
 1547843375 DEBUG torsocks[16768]: Setting up a connection to the Tor
 network on fd 3 (in setup_tor_connection() at torsocks.c:368)
 1547843375 DEBUG torsocks[16768]: Socks5 sending method ver: 5, nmethods
 0x01, methods 0x00 (in socks5_send_method() at socks5.c:229)
 1547843375 DEBUG torsocks[16768]: Socks5 received method ver: 5, method
 0x00 (in socks5_recv_method() at socks5.c:262)
 1547843375 DEBUG torsocks[16768]: [socks5] Resolve for www.google.com.
 sent successfully (in socks5_send_resolve_request() at socks5.c:633)
 1547843375 DEBUG torsocks[16768]: [socks5] Resolve reply received
 successfully (in socks5_recv_resolve_reply() at socks5.c:710)
 1547843375 DEBUG torsocks[16768]: [getaddrinfo] Node www.google.com.
 resolved to 172.217.21.132 (in tsocks_getaddrinfo() at getaddrinfo.c:107)
 172.217.21.132
 Connecting to www.google.com. (www.google.com.)|172.217.21.132|:443...
 1547843375 DEBUG torsocks[16768]: [socket] Creating socket with domain 2,
 type 1 and protocol 0 (in tsocks_socket() at socket.c:33)
 1547843375 DEBUG torsocks[16768]: Connect caught on fd 3 (in
 tsocks_connect() at connect.c:118)
 1547843375 DEBUG torsocks[16768]: [connect] Socket family AF_INET and type
 1 (in tsocks_validate_socket() at connect.c:77)
 1547843375 DEBUG torsocks[16768]: [onion] Finding onion entry for IP
 172.217.21.132 (in onion_entry_find_by_addr() at onion.c:268)
 1547843375 DEBUG torsocks[16768]: Connecting to the Tor network on fd 3
 (in tsocks_connect_to_tor() at torsocks.c:473)
 1547843375 DEBUG torsocks[16768]: Setting up a connection to the Tor
 network on fd 3 (in setup_tor_connection() at torsocks.c:368)
 1547843375 DEBUG torsocks[16768]: Socks5 sending method ver: 5, nmethods
 0x01, methods 0x00 (in socks5_send_method() at socks5.c:229)
 1547843375 DEBUG torsocks[16768]: Socks5 received method ver: 5, method
 0x00 (in socks5_recv_method() at socks5.c:262)
 1547843375 DEBUG torsocks[16768]: Socks5 sending connect request to fd 3
 (in socks5_send_connect_request() at socks5.c:459)
 1547843375 DEBUG torsocks[16768]: Socks5 received connect 

Re: [tor-bugs] #28615 [Metrics/Library]: Additional @type annotation

[Tor Bug Tracker & Wiki]

#28615: Additional @type annotation
-+--
 Reporter:  atagar   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Library  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Replying to [comment:4 atagar]:
 > Hi Karsten, I also need a @type for bandwidth files. Stem is learning to
 parse these since they'll soon be available via DirPorts...
 >
 > https://trac.torproject.org/projects/tor/ticket/29056
 > https://gitweb.torproject.org/torspec.git/tree/bandwidth-file-spec.txt

 What do you suggest as `@type` annotation for bandwidth files?

 > Mind if we move this forward?

 So, regarding the four suggested @type annotations from above (in slightly
 different order):

  - `@type detached-signature 1.0` seems plausible to me. Let's add it.
  - `@type router-status-entry-3 1.0` might be okay, too, even though it's
 not a descriptor of its own, but because it's defined in control-spec as
 response to a command there. We might want to document whether descriptor
 (parts) can be obtained via dir-spec, control-spec, or both. Oh, and I
 wonder if `@type network-status-entry-3 1.0` would be more consistent with
 the consensus and vote equivalents, what do you think?
  - `@type router-status-entry-micro-3 1.0` might be okay for the same
 reasons as above, though possibly renamed to `@type network-status-
 microdesc-entry-3 1.0`. One question though: which one do you get when
 running that control port command above? The unflavored or the microdesc-
 flavored entry?
  - `@type router-status-entry-2 1.0`, see above, except I'm unclear where
 you get this from in control-spec. And again, the slightly more consistent
 name could be `@type network-status-entry-2 1.0`.

 All these are questions and suggestions for discussion 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] #29124 [Applications/Tor Browser]: Browser opening without Tor

[Tor Bug Tracker & Wiki]

#29124: Browser opening without Tor
--+---
 Reporter:  alpra |  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 cypherpunks3):

 * owner:  (none) => tbb-team
 * resolution:   => duplicate
 * status:  new => closed
 * component:  Core Tor => Applications/Tor Browser


Comment:

 Duplicate of #29123

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

Re: [tor-bugs] #29123 [Applications/Tor Browser]: Firefox opening without Tor connection

[Tor Bug Tracker & Wiki]

#29123: Firefox opening without Tor connection
--+--
 Reporter:  alpra |  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 cypherpunks3):

 > Firefox window opens on a blank page and stays that way (there is no
 onion icon at all).

 Reinstall it. or
 https://trac.torproject.org/projects/tor/ticket/28749#comment: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] #29125 [Obfuscation/Snowflake]: Make websocket server tolerant of HTTP/2

[Tor Bug Tracker & Wiki]

#29125: Make websocket server tolerant of HTTP/2
---+
 Reporter:  dcf|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by dcf):

 * component:  - Select a component => Obfuscation/Snowflake


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29126 [Community/Tor Support]: Connection error with Debian Tor 0.3.5.7-1 and Tor Socks5 proxy

[Tor Bug Tracker & Wiki]

#29126: Connection error with Debian Tor 0.3.5.7-1 and Tor Socks5 proxy
--+---
 Reporter:  lanius|  Owner:  phoul
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  Community/Tor Support
  Version:  Tor: 0.3.5.7  |   Severity:  Normal
 Keywords:  regression?   |  Actual Points:
Parent ID:  #29050| Points:
 Reviewer:|Sponsor:
--+---
 I'm using a Tor proxy in my private LAN 192.168.1.0/24 on port 9050. That
 works fine with e.g. Telegram messenger in home zone to hide domestic DSL
 IP number. (Data stream is already encrypted)

 Since update there are no longer connections possible. /var/log/tor/*
 shows what went wrong. There are lots of same entries:

 > Jan 18 18:55:15.000 [warn] socks5: parsing failed - invalid user/pass
 authentication message.
 > Jan 18 18:55:15.000 [warn] Fetching socks handshake failed. Closing.

 If I set random login credentials (user/pass) in Telegram then Tor proxy
 works. A password isn't required but without an arbitrary username Tor
 connection failed again.

 I never used `Socks5ProxyUsername` and `Socks5ProxyUsername.` Both are not
 set.

 The Socks5 proxy setting in /etc/tor/torrc are:

 !SocksPort 127.0.0.1:9050
 !SocksPort 192.168.1.16:9050

 My workaround is to set an arbitrary username and no password.

 Hope that helps.

 

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

Re: [tor-bugs] #21304 [Obfuscation/Snowflake]: Sanitize snowflake.log

[Tor Bug Tracker & Wiki]

#21304: Sanitize snowflake.log
---+
 Reporter:  arlolra|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords:  starter|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Description changed by dcf:

Old description:

> For starters, the timestamps are in the local timezone.  We can make that
> UTC
>
> See also #19026

New description:

 For starters, the timestamps are in the local timezone.  We can make that
 UTC

 See also #19026

 Known problems:
  * When the websocket server panics (as in #29125), it writes the client
 IP address to the log:
{{{
 2019/01/18 18:56:29 http2: panic serving X.X.X.X:: interface
 conversion: *http2.responseWriter is not http.Hijacker: missing method
 Hijack
}}}

--

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29125 [- Select a component]: Make websocket server tolerant of HTTP/2

[Tor Bug Tracker & Wiki]

#29125: Make websocket server tolerant of HTTP/2
--+
 Reporter:  dcf   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 The Snowflake websocket server, inherited from flash proxy,
 [https://gitweb.torproject.org/pluggable-
 transports/websocket.git/tree/websocket/websocket.go?h=0.3#n326 assumes]
 that the incoming http.ResponseWriter implements the
 [https://golang.org/pkg/net/http/#Hijacker http.Hijacker] interface, which
 HTTP/2 connections do not.

 It causes a panic in the log when you connect to the server with e.g.
 curl:
 {{{
 2019/01/18 18:56:29 http2: panic serving X.X.X.X:: interface
 conversion: *http2.responseWriter is not http.Hijacker: missing method
 Hijack
 }}}

 I'm not sure if WebSocket connections from browsers use HTTP/2 yet or not,
 but in any case we should handle it gracefully.

 My first inclination is to see if porting to
 [https://godoc.org/github.com/gorilla/websocket gorilla/websocket] fixes
 this and #28726.

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

Re: [tor-bugs] #29123 [Applications/Tor Browser]: Firefox opening without Tor connection

[Tor Bug Tracker & Wiki]

#29123: Firefox opening without Tor connection
--+--
 Reporter:  alpra |  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:
--+--
Changes (by nickm):

 * owner:  (none) => tbb-team
 * component:  - Select a component => Applications/Tor Browser


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

[tor-bugs] #29124 [Core Tor]: Browser opening without Tor

[Tor Bug Tracker & Wiki]

#29124: Browser opening without Tor
+--
 Reporter:  alpra   |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  Core Tor
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 After updating, Tor browser worked fine the first time. After that, on
 restarting, the firefox browser opens to a blank page - it is not preceded
 by the Tor connection window, and there is no onion icon on the address
 bar at all. Not able to go any further from the blank page. Please help

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29123 [- Select a component]: Firefox opening without Tor connection

[Tor Bug Tracker & Wiki]

#29123: Firefox opening without Tor connection
+--
 Reporter:  alpra   |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  - Select a component
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 Hi. I am a newbie. Installed Tor Browser (64-bit) on Windows system -
 worked fine for several months, but after recent updates, worked fine when
 first updated; however, whenever restarted later, the Tor connection
 window does not come up; just the Firefox window opens on a blank page and
 stays that way (there is no onion icon at all). Needless to say, I am
 unable to do anything further with the browser. I have tried disabling
 antivirus/firewall without success. Please help.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29122 [Core Tor/Tor]: Intermittent test failure in circuitpadding/circuitpadding_wronghop

[Tor Bug Tracker & Wiki]

#29122: Intermittent test failure in circuitpadding/circuitpadding_wronghop
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Try running `circuitpadding_wronghop` in a loop, like this:
 {{{
 while ./src/test/test circuitpadding/circuitpadding_wronghop ; do true;
 done
 }}}

 After a minute or two it will fail with an error like this:
 {{{
   FAIL src/test/test_circuitpadding.c:1346: assert(n_client_cells OP_EQ
 2): 3 vs 2
 }}}
 or sometimes like this
 {{{
 circuitpadding/circuitpadding_wronghop: [forking]
   FAIL src/test/test_circuitpadding.c:1336: assert(n_client_cells OP_EQ
 1): 2 vs 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] #29122 [Core Tor/Tor]: Intermittent test failure in circuitpadding/circuitpadding_wronghop

[Tor Bug Tracker & Wiki]

#29122: Intermittent test failure in circuitpadding/circuitpadding_wronghop
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * cc: asn, mikeperry (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] #29029 [Core Tor/Tor]: Make "tried to establish rendezvous on non-OR circuit" into a protocol warning

[Tor Bug Tracker & Wiki]

#29029: Make "tried to establish rendezvous on non-OR circuit" into a protocol
warning
-+-
 Reporter:  teor |  Owner:  teor
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.5.7-rc
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tor-hs, fast-fix,|  Actual Points:  0.2
  040-accepted-20190115, 040-backport,   |
  035-backport, 034-backport, 033-backport,  |
  029-backport, postfreeze-ok|
Parent ID:  #15618   | Points:  0.1
 Reviewer:  asn  |Sponsor:
-+-
Changes (by nickm):

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


Comment:

 Merged to 0.2.9 and forward!

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

Re: [tor-bugs] #29114 [Core Tor/Tor]: Extended ORPort and TransportControlPort spec (#196) is "Finished" but not "Closed"

[Tor Bug Tracker & Wiki]

#29114: Extended ORPort and TransportControlPort spec (#196) is "Finished" but 
not
"Closed"
-+--
 Reporter:  ahf  |  Owner:  (none)
 Type:  project  | Status:  new
 Priority:  Low  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor |Version:  Tor: unspecified
 Severity:  Normal   | Resolution:
 Keywords:  tor-pt,tor-spec  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:  Sponsor19
-+--

Comment (by nickm):

 Yes, if we're actually using it (and I believe we are, right?)

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

Re: [tor-bugs] #29069 [Core Tor/Tor]: shellcheck: autogen.sh issues

[Tor Bug Tracker & Wiki]

#29069: shellcheck: autogen.sh issues
+
 Reporter:  rl1987  |  Owner:  rl1987
 Type:  defect  | Status:  merge_ready
 Priority:  Medium  |  Milestone:  Tor: 0.4.1.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  technical-debt  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+
Changes (by nickm):

 * status:  needs_review => merge_ready
 * milestone:   => Tor: 0.4.1.x-final


Comment:

 lgtm, let's take it in 0.4.1.x

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

Re: [tor-bugs] #29121 [Core Tor/Tor]: tor man page doesn't mention isolating between socksports

[Tor Bug Tracker & Wiki]

#29121: tor man page doesn't mention isolating between socksports
--+--
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by nickm):

 * milestone:   => Tor: unspecified


Comment:

 (It might not be obvious enough, but it ''is'' there.  I'd love a patch to
 make it make more sense.)

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

Re: [tor-bugs] #29121 [Core Tor/Tor]: tor man page doesn't mention isolating between socksports

[Tor Bug Tracker & Wiki]

#29121: tor man page doesn't mention isolating between socksports
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by nickm):

 Here's the documentation:

 {{{
 **SessionGroup=**__INT__;;
 If no other isolation rules would prevent it, allow streams
 on this port to share circuits with streams from every other
 port with the same session group.  (By default, streams received
 on different SocksPorts, TransPorts, etc are always isolated from
 one
 another. This option overrides that behavior.)
 }}}

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

Re: [tor-bugs] #26698 [Core Tor/Tor]: Authorities should put a hash of the bandwidth file in their votes

[Tor Bug Tracker & Wiki]

#26698: Authorities should put a hash of the bandwidth file in their votes
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:
   |  needs_review
 Priority:  Low|  Milestone:  Tor:
   |  0.4.0.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tor-crypto tor-dirauth tor-bwauth  |  Actual Points:
Parent ID:  #27047 | Points:
 Reviewer:  nickm  |Sponsor:
---+---
Changes (by juga):

 * status:  needs_revision => needs_review


Comment:

 Nickm and teor reviews are not overlapping (except for the `255` typo).
 I made lot of fixups because i moved the hash calculation from the new
 function to `dirserv_read_measured_bandwidths` and i realized about more
 issues on the way.
 I explain each fixup in the PR.
 If you prefer to review a squashed version, see also the comment in the
 PR.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29121 [Core Tor/Tor]: tor man page doesn't mention isolating between socksports

[Tor Bug Tracker & Wiki]

#29121: tor man page doesn't mention isolating between socksports
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 If I set SocksPort 9050 and also SocksPort 9060, then if I understand
 correctly, Tor automatically isolates stream requests that come in on the
 different socksports.

 But the man page doesn't mention this level of isolation. Maybe because
 there is no flag for influencing it?

 It sure seems helpful to have a full sentence in the socksport intro
 stanza explaining what gets isolated by default, and what can be isolated
 by changing options. Or maybe there is a better place to put that than the
 socksport section?

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

Re: [tor-bugs] #29107 [Metrics/CollecTor]: Please add op-ab to CollecTor

[Tor Bug Tracker & Wiki]

#29107: Please add op-ab to CollecTor
---+--
 Reporter:  irl|  Owner:  karsten
 Type:  task   | Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by karsten):

 * status:  assigned => accepted


Comment:

 Sounds good. I just added op-ab to CollecTor's properties file, but it'll
 take a few more hours until the next run. I'll check over the next days
 whether it gets archived successfully.

 Next step will be to add op-ab to the Tor Metrics website. I believe
 that's going to happen automagically. But if not, I'll take a look.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29120 [Applications/Tor Browser]: Default value of media.cache_size (0) causes some media to load extremely slowly or become unplayable

[Tor Bug Tracker & Wiki]

#29120: Default value of media.cache_size (0) causes some media to load 
extremely
slowly or become unplayable
+--
 Reporter:  |  Owner:  tbb-team
  QZw2aBQoPyuEVXYVlBps  |
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  Applications/Tor Browser
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 It seems this value was defaulted to 0 after this ticket:
 https://trac.torproject.org/projects/tor/ticket/10237

 The issue this causes can be seen on this page:
 https://livestreamfails.com/post/28515

 If you open this link in a default configured Tor Browser (I'm using
 v8.0.4), and open the network inspector (CTRL+SHIFT+E), you will see the
 media file is constantly being re-requested, downloading the file a few
 hundred kilobytes at a time using range requests.

 This causes the video to load extremely slowly. If the HTTP server does
 not support range requests, the video will seemingly become unplayable in
 the native player.

 This kind of behavior could also be seen as abusive or mistaken as DoS
 related traffic by website operators, since it is not typically how
 browsers download media.

 Setting media.cache_size to the default Firefox value of 512000 fixes
 this, it may also work with a lower cache size, but I've only tried the
 default Firefox value. I suppose it also may bring back the original issue
 of the media cache being stored on disk, that ticket is from 5 years ago
 though, so I'm sure if that situation has changed.

 This bug only seems to affect certain media files, I'm not exactly sure
 what the other factors are in triggering the behavoir.

 This bug also exists in the latest stable version of Firefox if you set
 the media.cache_size to 0, I suppose it's rarely encountered though since
 the default is much higher.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29119 [Applications/Tor Browser]: Searching after start-up when about:tor is loaded returns "400 Bad Request" sometimes

[Tor Bug Tracker & Wiki]

#29119: Searching after start-up when about:tor is loaded returns "400 Bad 
Request"
sometimes
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-regression,
 Severity:  Normal   |  tbb-8.0-issues
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Some users noted that when doing a search right after start-up it happens
 sometimes that e.g. Startpage (and I think DuckDuckGo as well) return a
 "400 Bad Request".

 I've been hitting this issue as well and I can reproduce it if I try hard
 enough (I need less than 10 attempts).

 I think that behavior started with Tor Browser 8, thus setting the
 respective flags.

 Comparing Tor Browser logs do not show anything unusual, though, weird.

 That's on Linux. Not sure whether other platforms are affected.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29118 [Applications/Tor Browser]: Provide ASLR for mingw-w64/clang by default

[Tor Bug Tracker & Wiki]

#29118: Provide ASLR for mingw-w64/clang by default
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-rbm,
 Severity:  Normal   |  GeorgKoppen201901,
 |  TorBrowserTeam201901
Actual Points:   |  Parent ID:  #28238
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 ASLR is disabled when compiling with mingw-w64/clang. But we want to have
 it enabled by default for all of our projects (not just Firefox). See:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1520308 for the corresponding
 Mozilla bug.

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

Re: [tor-bugs] #29035 [Applications/Tor Browser]: Post-YE campaign clean up

[Tor Bug Tracker & Wiki]

#29035: Post-YE campaign clean up
-+-
 Reporter:  pili |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Minor| Resolution:
 Keywords:  TorBrowserTeam201901R,   |  Actual Points:
  GeorgKoppen201901  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * cc: stevenson (removed)
 * cc: sstevenson (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] #29035 [Applications/Tor Browser]: Post-YE campaign clean up

[Tor Bug Tracker & Wiki]

#29035: Post-YE campaign clean up
-+-
 Reporter:  pili |  Owner:  tbb-
 |  team
 Type:  task | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Minor| Resolution:
 Keywords:  TorBrowserTeam201901R,   |  Actual Points:
  GeorgKoppen201901  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * cc: sstevenson (removed)
 * cc: stevenson, igt0 (added)
 * keywords:  TorBrowserTeam201901, GeorgKoppen201901 =>
 TorBrowserTeam201901R, GeorgKoppen201901
 * status:  new => needs_review


Comment:

 `bug_29035_v3` has the patches for review. There are essentially three
 parts: 1) removing the donation banner related changes (commit
 9b4c56f050a266bbcd04d6985ee46f9da612e0e7), 2) removing the newsletter
 sign-up banner changes (8d3c6f996c943399a1505646eee14ce81868c0c8), and 3)
 adding the code changes for the new sign-up message/link on desktop and
 mobile (commit e73ff049acb16d410083c9cad64da678aab30294).

 I made it so that the whole sign-up related text and icon are on a single
 line on tablets, laptops, and desktops while on phones it has the three
 lines as outlined in comment:10. I am fine adjusting that as needed or
 making it more complex, like on a phone in landscape mode show the single
 line, too. I am not a web developer, so I don't have that strong opinions
 here.

 A mobile bundle for testing can be found at:

 https://people.torproject.org/~gk/testbuilds/tor-browser-tbb-nightly-
 android-armv7-multi-qa_29035.apk
 https://people.torproject.org/~gk/testbuilds/tor-browser-tbb-nightly-
 android-armv7-multi-qa_29035.apk.asc

 steph: #28145 is the ticket for the remaining links on `about:tor` should
 be doable for the next release provided we are sure how this should look
 like.

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

Re: [tor-bugs] #28982 [Core Tor/Tor]: Refactor GETINFO dir/ so that new tor/ URLs automatically become GETINFOs

[Tor Bug Tracker & Wiki]

#28982: Refactor GETINFO dir/ so that new tor/ URLs automatically become 
GETINFOs
-+-
 Reporter:  teor |  Owner:  rl1987
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-control, technical-debt  |  Actual Points:
Parent ID:  #7646| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by rl1987):

 * type:  defect => enhancement


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

Re: [tor-bugs] #28982 [Core Tor/Tor]: Refactor GETINFO dir/ so that new tor/ URLs automatically become GETINFOs

[Tor Bug Tracker & Wiki]

#28982: Refactor GETINFO dir/ so that new tor/ URLs automatically become 
GETINFOs
-+-
 Reporter:  teor |  Owner:  rl1987
 Type:  defect   | Status:  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-control, technical-debt  |  Actual Points:
Parent ID:  #7646| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by rl1987):

 * owner:  (none) => rl1987
 * 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] #28145 [Applications/Tor Browser]: TBA: Add support/Tor Browser Manual links and mission statement (was: TBA: Add support/Tor Browser Manual links)

[Tor Bug Tracker & Wiki]

#28145: TBA: Add support/Tor Browser Manual links and mission statement
-+-
 Reporter:  pili |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, TBA-a3,  |  Actual Points:
  TorBrowserTeam201901   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8
-+-

Comment (by gk):

 This topic came up in #29035. We should add the mission statement, too, I
 guess, to give a similar experience on all platforms.

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

Re: [tor-bugs] #28229 [Core Tor/Tor]: Possible race condition opening SOCKS Port in test_rebind.py

[Tor Bug Tracker & Wiki]

#28229: Possible race condition opening SOCKS Port in test_rebind.py
-+
 Reporter:  teor |  Owner:  rl1987
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor: 0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.5.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  tor-ci, 035-can  |  Actual Points:
Parent ID:   | Points:
 Reviewer:  teor |Sponsor:
-+

Comment (by rl1987):

 https://travis-ci.org/rl1987/tor/jobs/481321719

 Hmmm

 {{{
 2019-01-18 11:58:35.059 Tor logged: "Jan 18 11:58:35.059 [info]
 set_max_file_descriptors: Raising max file descriptors from 10208 to
 9223372036854775807.", waiting for "Opened Socks listener"
 2019-01-18 11:58:35.059 Tor logged: "Jan 18 11:58:35.059 [info]
 set_max_file_descriptors: Dropped connection limit to 10208 based on
 OPEN_MAX (10240); Apparently, 9223372036854775807 was too high and rlimit
 lied to us.", waiting for "Opened Socks listener"
 2019-01-18 11:58:35.059 Tor logged: "Jan 18 11:58:35.059 [warn] You
 specified a public address '0.0.0.0:58579' for SocksPort. Other people on
 the Internet might find your computer and use it as an open proxy. Please
 don't allow this unless you have a good reason.", waiting for "Opened
 Socks listener"
 2019-01-18 11:58:35.060 Tor logged: "Jan 18 11:58:35.059 [debug]
 retry_all_listeners: 1 replacements - starting rebinding loop.", waiting
 for "Opened Socks listener"
 2019-01-18 11:58:35.060 Tor logged: "Jan 18 11:58:35.060 [notice] Opening
 Socks listener on 0.0.0.0:58579", waiting for "Opened Socks listener"
 2019-01-18 11:58:35.060 Tor logged: "Jan 18 11:58:35.060 [debug]
 connection_add_impl: new conn type Socks listener, socket 7, address
 0.0.0.0, n_conns 4.", waiting for "Opened Socks listener"
 2019-01-18 11:58:35.060 Tor logged: "Jan 18 11:58:35.060 [debug]
 connection_listener_new: Socks listener listening on port 58579.", waiting
 for "Opened Socks listener"
 2019-01-18 11:58:35.060 Tor logged: "Jan 18 11:58:35.060 [notice] Opened
 Socks listener on 0.0.0.0:58579"
 2019-01-18 11:58:35.060 FAIL
 Cannot connect to SOCKSPort: error Connection reset by peer
 }}}

 `setrlimit()` failed to raise number of open file descriptors we can have.
 Note that it tries to raise it to `LLONG_MAX`
 (http://pubs.opengroup.org/onlinepubs/009604499/basedefs/limits.h.html),
 which is suspicious. Perhaps that causes listener failure to happen?
 Perhaps we should sanity check `rlim.rlim_max` that we get from
 `getrlimit()` before trying to use 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] #28836 [Applications/Tor Browser]: Links on about:tor are not clickable anymore on Windows starting with 8.5a5

[Tor Bug Tracker & Wiki]

#28836: Links on about:tor are not clickable anymore on Windows starting with 
8.5a5
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-regression,  |  Actual Points:
  TorBrowserTeam201901R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-regression, TorBrowserTeam201901R, tbb-backport => tbb-
 regression, TorBrowserTeam201901R


Comment:

 Correct, 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] #28836 [Applications/Tor Browser]: Links on about:tor are not clickable anymore on Windows starting with 8.5a5

[Tor Bug Tracker & Wiki]

#28836: Links on about:tor are not clickable anymore on Windows starting with 
8.5a5
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-regression,  |  Actual Points:
  TorBrowserTeam201901R, tbb-backport|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by mcs):

 Replying to [comment:9 gk]:
 > mcs/brade which commit exactly did cause that (I am wondering about the
 need for backporting this. Marking this as `tbb-backport` so that we don't
 forget about it for now.)?

 Non-clickable links on desktop were caused by
 61deb44d0c07eb1ec1d71eac2f0a7aeca87ea054. Specifically, the first change
 to src/chrome/skin/aboutTor.css within that commit. You might want to
 double-check, but I don't think that change is in stable Tor Browser.

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

Re: [tor-bugs] #28982 [Core Tor/Tor]: Refactor GETINFO dir/ so that new tor/ URLs automatically become GETINFOs

[Tor Bug Tracker & Wiki]

#28982: Refactor GETINFO dir/ so that new tor/ URLs automatically become 
GETINFOs
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-control, technical-debt  |  Actual Points:
Parent ID:  #7646| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by rl1987):

 * cc: rl1987 (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] #27895 [Internal Services/Service - git]: Add push access to alexishan

[Tor Bug Tracker & Wiki]

#27895: Add push access to alexishan
-+
 Reporter:  legind   |  Owner:  tor-gitadm
 Type:  task | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by irl):

 {{{
 Alexis Hancock (uid=alexishan,ou=users,dc=torproject,dc=org)
 }}}

 The user definitely exists in LDAP so it should just be a key issue.

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

Re: [tor-bugs] #27895 [Internal Services/Service - git]: Add push access to alexishan

[Tor Bug Tracker & Wiki]

#27895: Add push access to alexishan
-+
 Reporter:  legind   |  Owner:  tor-gitadm
 Type:  task | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - git  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by irl):

 Updating your SSH key is a self-service task.

 https://db.torproject.org/doc-mail.html

 Please ask on #tor-project on irc.oftc.net if you have problems using this
 service, and someone there will be able to help 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] #28836 [Applications/Tor Browser]: Links on about:tor are not clickable anymore on Windows starting with 8.5a5

[Tor Bug Tracker & Wiki]

#28836: Links on about:tor are not clickable anymore on Windows starting with 
8.5a5
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-regression,  |  Actual Points:
  TorBrowserTeam201901R, tbb-backport|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  tbb-regression, TorBrowserTeam201901R => tbb-regression,
 TorBrowserTeam201901R, tbb-backport
 * status:  needs_review => closed
 * resolution:   => fixed


Comment:

 This works for me, too. On mobile I've tested the patch with my upcoming
 work for #29035. Merged to `master` (commit
 0a628166a527bb643fa256e20332fbf54357697c).

 mcs/brade which commit exactly did cause that (I am wondering about the
 need for backporting this. Marking this as `tbb-backport` so that we don't
 forget about it for now.)?

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

Re: [tor-bugs] #29069 [Core Tor/Tor]: shellcheck: autogen.sh issues

[Tor Bug Tracker & Wiki]

#29069: shellcheck: autogen.sh issues
+--
 Reporter:  rl1987  |  Owner:  rl1987
 Type:  defect  | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  technical-debt  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by rl1987):

 * status:  accepted => needs_review


Comment:

 https://github.com/torproject/tor/pull/658

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

Re: [tor-bugs] #29069 [Core Tor/Tor]: shellcheck: autogen.sh issues

[Tor Bug Tracker & Wiki]

#29069: shellcheck: autogen.sh issues
+--
 Reporter:  rl1987  |  Owner:  rl1987
 Type:  defect  | Status:  accepted
 Priority:  Medium  |  Milestone:
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  technical-debt  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by rl1987):

 * status:  new => accepted
 * owner:  (none) => rl1987


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

Re: [tor-bugs] #29108 [Core Tor/Tor]: Refactor crypto_digest.c to have fewer ifdefs

[Tor Bug Tracker & Wiki]

#29108: Refactor crypto_digest.c to have fewer ifdefs
-+-
 Reporter:  nickm|  Owner:  rl1987
 Type:  task | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  041-proposed refactor technical- |  Actual Points:
  debt   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by rl1987):

 * status:  accepted => needs_review


Comment:

 https://github.com/torproject/tor/pull/657

 I could try unifying this patch with #28837, if that's needed.

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

Re: [tor-bugs] #27083 [Applications/Tor Browser]: TBA: Window size rounding isn't used

[Tor Bug Tracker & Wiki]

#27083: TBA: Window size rounding isn't used
-+-
 Reporter:  sysrqb   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-fingerprinting-  |  Actual Points:
  resolution, TorBrowserTeam201901   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8
-+-
Changes (by pili):

 * sponsor:   => Sponsor8


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

Re: [tor-bugs] #28802 [Applications/Tor Browser]: Integrate PTs and bridge support into Tor Browser

[Tor Bug Tracker & Wiki]

#28802: Integrate PTs and bridge support into Tor Browser
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, TBA-a3,  |  Actual Points:
  TorBrowserTeam201901   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor8
-+-
Changes (by pili):

 * sponsor:   => Sponsor8


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

Re: [tor-bugs] #28836 [Applications/Tor Browser]: Links on about:tor are not clickable anymore on Windows starting with 8.5a5

[Tor Bug Tracker & Wiki]

#28836: Links on about:tor are not clickable anymore on Windows starting with 
8.5a5
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-regression,  |  Actual Points:
  TorBrowserTeam201901R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by igt0):

 On mobile it looks great, with and without the banner. All the links are
 clickable.

 Replying to [comment:7 mcs]:
 > Replying to [comment:6 gk]:
 > > While testing on a Windows system I got
 > > ...
 > > with the banner on. Is this expected? (Without the banner it looks
 fine)
 >
 > No, that is a bug. We had to remove a CSS rule related to the banner.
 Here is a revised patch:
 >
 
https://gitweb.torproject.org/user/brade/torbutton.git/commit/?h=bug28836-02=3d3a6b06de45f92bf87114272241d4964a87bec0
 >
 > We did test with the banner both showing and hidden this time, although
 it would be great if someone could test again on mobile.

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

Re: [tor-bugs] #28482 [Applications/Tor Browser]: Image reversed on home screen when opening for browser

[Tor Bug Tracker & Wiki]

#28482: Image reversed on home screen when opening for browser
--+---
 Reporter:  jlatino_11|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by gk):

 I wonder whether https://blog.torproject.org/comment/279413#comment-279413
 is the same underlying issue (with text, though).

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

Re: [tor-bugs] #29108 [Core Tor/Tor]: Refactor crypto_digest.c to have fewer ifdefs

[Tor Bug Tracker & Wiki]

#29108: Refactor crypto_digest.c to have fewer ifdefs
-+-
 Reporter:  nickm|  Owner:  rl1987
 Type:  task | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  041-proposed refactor technical- |  Actual Points:
  debt   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
 |  Sponsor31-can
-+-
Changes (by rl1987):

 * status:  new => accepted
 * owner:  (none) => rl1987


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

Re: [tor-bugs] #29050 [Community/Tor Support]: Connecting to tor over a socks 5 connection no longer works in 3.5.7

[Tor Bug Tracker & Wiki]

#29050: Connecting to tor over a socks 5 connection no longer works in 3.5.7
---+---
 Reporter:  arj|  Owner:  dgoulet
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Community/Tor Support  |Version:  Tor: 0.3.5.7
 Severity:  Normal | Resolution:
 Keywords:  regression?|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by rl1987):

 Lets investigate this a bit further. How is your SOCKSPort configured? Do
 you use any flags for process isolation? Can you still try torsocks with
 `-d` and show us what it prints? For example, you could run `torsocks
 --port 9050 -u fox -p trustno1 wget https://www.google.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] #29075 [Webpages/Support]: Sort support glossary by target language

[Tor Bug Tracker & Wiki]

#29075: Sort support glossary by target language
--+--
 Reporter:  traumschule   |  Owner:  hiro
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Support  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by traumschule):

 Script on the {{{glossary}}} branch to create file structure from
 [https://gitweb.torproject.org/tor-
 glossary.git/plain/glossary_all_langs.csv glossary_all_langs.csv]:
 {{{content/glossary/glossary-X/contents.lr}}} .

 https://github.com/torproject/support/pull/5

 The CSV needs some sanitizing, on a test run it created 2500 folders.

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

Re: [tor-bugs] #28960 [Applications/Tor Browser]: Tor Browser 8 does not support legacy OS like Win2000, WinXP

[Tor Bug Tracker & Wiki]

#28960: Tor Browser 8 does not support legacy OS like Win2000, WinXP
--+--
 Reporter:  nigger_from_africa|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  wontfix
 Keywords:  CIA   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

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


Comment:

 Replying to [comment:2 nigger_from_africa]:
 > >There is no conspiracy here
 > there is
 >
 > >Firefox (which Tor Browser is derived from) dropped support for those
 older platforms, so Tor Browser had to drop support as well.
 > wrong. Tor Browser is not Firefox, Tor Project is not Mozilla.
 > Tor Project could make necessary changes in Firefox to make it work on
 legacy platforms.
 > Or Tor Project could select another web browser as base for Tor Browser.

 We won't do either of those. Please do not reopen this ticket, 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