Re: [tor-bugs] #25317 [Metrics/CollecTor]: Enable webstats to process large (> 2G) logfiles

[Tor Bug Tracker & Wiki]

#25317: Enable webstats to process large (> 2G) logfiles
---+
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  defect | Status:  needs_revision
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by iwakeh):

 * status:  needs_review => needs_revision


Comment:

 This patch needs revision.  One more memory issue to clean out.

 (Anyway, a yearly batched import could already be attempted, 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] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
--+---
 Reporter:  kiokawasaki1998   |  Owner:  (none)
 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 cypherpunks):

 Replying to [comment:35 mario]:
 > 1) I can only confirm that the issue is present ONLY when I use Tor
 browser and I attempt to use the https protocol. http is working with TOR
 (at least for the few website that I tested)

 Can you please go to http://example.com/ in the Tor Browser, then click on
 `Ctrl+U` to see the source and copy paste it 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] #6236 [Core Tor/Tor]: Remove duplicate code between parse_{c, s}method_line

[Tor Bug Tracker & Wiki]

#6236: Remove duplicate code between parse_{c,s}method_line
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client easy refactor duplicate-  |  Actual Points:
  code   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by fristonio):

 Thanks for your feedback asn, I have added your patch to the branch. Here
 is the final patch https://github.com/fristonio/tor/tree/ticket-6236.

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

Re: [tor-bugs] #6236 [Core Tor/Tor]: Remove duplicate code between parse_{c, s}method_line

[Tor Bug Tracker & Wiki]

#6236: Remove duplicate code between parse_{c,s}method_line
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  task | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client easy refactor duplicate-  |  Actual Points:
  code   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by fristonio):

 * status:  needs_revision => merge_ready


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

Re: [tor-bugs] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
--+---
 Reporter:  kiokawasaki1998   |  Owner:  (none)
 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 mario):

 Replying to [comment:34 Dude_Virus]:
 My dear Dude_Virus,
 I can't provide more info about a part my workaround as above.

 1) I can only confirm that the issue is present ONLY when I use Tor
 browser and I attempt to use the https protocol. http is working with TOR
 (at least for the few website that I tested)
 2) The issue disappears if I uncheck the kaspersky setting "do not scan
 encrypted ..."
 3) If I switch off the TOR browser and restore the standard Kaspersky
 settings ALL is perfectly working

 Bye
 Mario


 > I am not sure how kaspersky can suddenly cause a problem. Last I used
 TOR was 5 days ago where everything is working fine. In Kaspersky I always
 had scan encrypted connection enabled because I use the protection
 components Safe Money, Private Browsing, Web Anti Virus and Anti-Banner".
 I havent tweaked anything in the last 5 days so not sure what changed
 suddenly.
 >
 > Further testing on this shows that it is not only https site but even
 http sites which are having the issue. This only is happening in the TOR
 browser and not in any other browser including firefox.
 >
 > The Kaspersky setting is not set to always scan encrypted connection but
 is set to scan encrypted connection on request from protection components
 (that too kaspersky components).

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

Re: [tor-bugs] #25161 [Metrics/CollecTor]: Fix any memory problem caused by number of log files to be imported by the webstats module

[Tor Bug Tracker & Wiki]

#25161: Fix any memory problem caused by number of log files to be imported by 
the
webstats module
---+---
 Reporter:  karsten|  Owner:  iwakeh
 Type:  defect | Status:  needs_information
 Priority:  Medium |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by iwakeh):

 The import should either be attempted on less than yearly batches or wait
 for the patch to #25317.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25343 [Applications/Tor Browser]: disable F11 as fullscreen

[Tor Bug Tracker & Wiki]

#25343: disable F11 as fullscreen
--+--
 Reporter:  catperson |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: unspecified
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 My cat walked on my keyboard and fullscreen'd my tor browser with the F11
 key, since this could be arguably critical for some users, wouldn't it
 make sense to disable F11 eliminating the possibility of fullscreening by
 accident or due to cat?

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

Re: [tor-bugs] #25137 [Obfuscation/Censorship analysis]: Tor blocked in UAE

[Tor Bug Tracker & Wiki]

#25137: Tor blocked in UAE
-+
 Reporter:  mwolfe   |  Owner:  dcf
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Obfuscation/Censorship analysis  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  censorship block ae  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by mwolfe):

 On Sat 24 Feb 18, at about 4 pm GMT, Snowflake flaked out in the UAE.
 Working fine at 3:30 pm GMT, unable to connect at 4 pm. Meek still works.
 I have not tried bridges from bridges.torproject.org. I downloaded 3, but
 always try the menu items first. obfs4 is now blocked, and snowflake seems
 to be blocked, but Meek works. If Meek stops, I'll try the private
 bridges.

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

Re: [tor-bugs] #25137 [Obfuscation/Censorship analysis]: Tor blocked in UAE

[Tor Bug Tracker & Wiki]

#25137: Tor blocked in UAE
-+
 Reporter:  mwolfe   |  Owner:  dcf
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Obfuscation/Censorship analysis  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  censorship block ae  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by cypherpunks):

 Replying to [comment:27 mwolfe]:
 > On Sat 24 Feb 18, at about 4 pm GMT, Snowflake flaked out in the UAE.
 Working fine at 3:30 pm GMT, unable to connect at 4 pm. Meek still works.
 I have not tried bridges from bridges.torproject.org. I downloaded 3, but
 always try the menu items first. obfs4 is now blocked, and snowflake seems
 to be blocked, but Meek works. If Meek stops, I'll try the private
 bridges.
 Are you really sure that Snowflake is blocked? Some notes however: 1)
 snowflake is still experimental, and there's a bug with it where it
 reaches 100% CPU usage and , that may lead in some cases to it stopping
 working, 2) there is still a very low number of people who run snowflake
 bridges, 3) since snowflake is essentially WebRTC maybe they're actually
 blocking as well other WebRTC traffic? 4) can you access the snowflake
 domain front, i.e. 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

[tor-bugs] #25344 [Obfuscation/Snowflake]: proxy-go needs to relax between polls

[Tor Bug Tracker & Wiki]

#25344: proxy-go needs to relax between polls
---+
 Reporter:  dcf|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 The JavaScript proxy has `DEFAULT_BROKER_POLL_INTERVAL`, but there's
 nothing like that in proxy-go. The standalone broker is getting 2 to 5
 /proxy requests per second from the 3 round-the-clock proxy-go instances.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25345 [Obfuscation/Snowflake]: Adapt broker to use ACME HTTP-01 challenge for automatic certificates

[Tor Bug Tracker & Wiki]

#25345: Adapt broker to use ACME HTTP-01 challenge for automatic certificates
---+--
 Reporter:  dcf|  Owner:  dcf
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 See #24928 for the equivalent ticket for meek. The TLS-SNI-01 challenge
 that we were using doesn't work anymore. Because of this, the standalone
 broker has been broken since 2018-01-18 :/

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

Re: [tor-bugs] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
--+---
 Reporter:  kiokawasaki1998   |  Owner:  (none)
 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 mario):

 Replying to [comment:36 cypherpunks]:
 > Replying to [comment:35 mario]:
 > > 1) I can only confirm that the issue is present ONLY when I use Tor
 browser and I attempt to use the https protocol. http is working with TOR
 (at least for the few website that I tested)
 >
 > Can you please go to http://example.com/ in the Tor Browser, then click
 on `Ctrl+U` to see the source and copy paste it here? (while Kaspesky is
 enabled with its problematic settings)

 Hi,
 here it is wht you required:

 
 
 
 Example Domain

 
 
 
 
 body {
 background-color: #f0f0f2;
 margin: 0;
 padding: 0;
 font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial,
 sans-serif;

 }
 div {
 width: 600px;
 margin: 5em auto;
 padding: 50px;
 background-color: #fff;
 border-radius: 1em;
 }
 a:link, a:visited {
 color: #38488f;
 text-decoration: none;
 }
 @media (max-width: 700px) {
 body {
 background-color: #fff;
 }
 div {
 width: auto;
 margin: 0 auto;
 border-radius: 0;
 padding: 1em;
 }
 }
 
 

 
 
 Example Domain
 This domain is established to be used for illustrative examples in
 documents. You may use this
 domain in examples without prior coordination or asking for
 permission.
 http://www.iana.org/domains/example;>More
 information...
 
 
 

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

Re: [tor-bugs] #23863 [Core Tor/Tor]: When our directory guards don't have each others' microdescs, we should try an authority or fallback

[Tor Bug Tracker & Wiki]

#23863: When our directory guards don't have each others' microdescs, we should 
try
an authority or fallback
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.4.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.3.0.6
 Severity:  Normal | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client  |  Actual Points:
Parent ID:  #21969 | Points:  1
 Reviewer: |Sponsor:
---+---

Comment (by s7r):

 My laptop's TBB 7.5 just got hit by this, I think. I am not sure if it's
 this or #21969. Basically, it is running but being useless (can't load any
 web page, other apps using the SocksPort opened by this Tor instance are
 also disconnected). It is in this state fore more than 4 hours now. I will
 leave it to see if it recovers by itself. Tried new identity, but does not
 fix it. Funny the heartbeat counts circuits:

 {{{
 2/24/2018 11:05:35 AM.600 [NOTICE] Heartbeat: Tor's uptime is 2 days 17:59
 hours, with 3 circuits open. I've sent 37.58 MB and received 116.72 MB.
 2/24/2018 11:05:35 AM.600 [NOTICE] Average packaged cell fullness:
 29.597%. TLS write overhead: 5%
 2/24/2018 15:15:44 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:16:14 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:18:30 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:18:50 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:19:06 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:20:30 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:20:50 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:21:06 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:22:30 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:22:50 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:23:06 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:26:30 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:28:30 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:30:30 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:32:32 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 16:34:32 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 17:05:35 PM.600 [NOTICE] Heartbeat: Tor's uptime is 2 days 23:59
 hours, with 7 circuits open. I've sent 40.25 MB and received 122.63 MB.
 2/24/2018 17:05:35 PM.600 [NOTICE] Average packaged cell fullness:
 28.339%. TLS write overhead: 5%
 2/24/2018 17:12:13 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:443. Giving up. (waiting for circuit)
 2/24/2018 17:16:52 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:443. Giving up. (waiting for circuit)
 2/24/2018 17:38:32 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:443. Giving up. (waiting for circuit)
 2/24/2018 17:41:02 PM.700 [NOTICE] New control connection opened from
 127.0.0.1.
 2/24/2018 17:43:08 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:443. Giving up. (waiting for circuit)
 2/24/2018 17:46:02 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 17:53:47 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:993. Giving up. (waiting for circuit)
 2/24/2018 17:55:00 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:587. Giving up. (waiting for circuit)
 2/24/2018 17:55:47 

Re: [tor-bugs] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
--+---
 Reporter:  kiokawasaki1998   |  Owner:  (none)
 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 cypherpunks):

 @mario

 Okay, it doesn't look like Kaspersky has been tampering with pages as it
 does with clearnet so I'm not sure why only HTTPS websites are messed up
 in your 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] #25137 [Obfuscation/Censorship analysis]: Tor blocked in UAE

[Tor Bug Tracker & Wiki]

#25137: Tor blocked in UAE
-+
 Reporter:  mwolfe   |  Owner:  dcf
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Obfuscation/Censorship analysis  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  censorship block ae  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by cypherpunks):

 Replying to [comment:27 mwolfe]:
 > On Sat 24 Feb 18, at about 4 pm GMT, Snowflake flaked out in the UAE.
 Working fine at 3:30 pm GMT, unable to connect at 4 pm. Meek still works.
 I have not tried bridges from bridges.torproject.org. I downloaded 3, but
 always try the menu items first. obfs4 is now blocked, and snowflake seems
 to be blocked, but Meek works. If Meek stops, I'll try the private
 bridges.

 Well it doesn't work even for me, so no worries, the censors still have no
 clue about snowflake ;)

 {{{
 Finishing handshake with first hop. (DONE; DONE; count 1; recommendation
 warn; host 2B280B23E1107BB62ABFC40DDCC8824814F80A72 at 0.0.3.0:1)
 [warn] 1 connections have failed:
 [warn]  1 connections died in state handshaking (TLS) with SSL state
 SSLv2/v3 read server hello A in HANDSHAKE}}}

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

Re: [tor-bugs] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
-+-
 Reporter:  asn  |  Owner:  asn
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Blocker  | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client,   |  Actual Points:
  tbb-usability-website, tbb-needs   |
Parent ID:   | Points:  1.5
 Reviewer:   |Sponsor:
 |  SponsorV
-+-

Comment (by s7r):

 I have been just hit by this on TBB 7.5. It is using the default guard
 context, no bridges. I am not sure if it is this or #23863. It is running
 but basically useless, it cannot load any web pages and all other apps
 using this Tor's instance SocksPort are also disconnected. It is in this
 state for about 4 hours, want to leave it a little bit more to see if it
 recovers. I get this:

 {{{
 2/24/2018 18:20:34 PM.800 [NOTICE] Our directory information is no longer
 up-to-date enough to build circuits: We're missing descriptors for 1/2 of
 our primary entry guards (total microdescriptors: 6051/6077).
 2/24/2018 18:20:34 PM.800 [NOTICE] I learned some more directory
 information, but not enough to build a circuit: We're missing descriptors
 for 1/2 of our primary entry guards (total microdescriptors: 6051/6077).
 }}}

 and even after:
 {{{
 2/24/2018 18:20:35 PM.200 [NOTICE] We now have enough directory
 information to build circuits.
 }}}

 It is still not working and not being able to load any web page:
 {{{
 2/24/2018 19:03:18 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:443. Giving up. (waiting for circuit)
 }}}

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

Re: [tor-bugs] #24857 [Core Tor/Tor]: tor 0.3.1.9 100% cpu load

[Tor Bug Tracker & Wiki]

#24857: tor 0.3.1.9 100% cpu load
-+
 Reporter:  Eugene646|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.2.9
 Severity:  Normal   | Resolution:
 Keywords:  cpu, windows, linux  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by cypherpunks):

 Replying to [comment:10 AlexRad]:
 > I see next log messages when tor service use 100% CPU
 >
 > and so on...

 For a long time (10 and more minutes)?

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

Re: [tor-bugs] #24857 [Core Tor/Tor]: tor 0.3.1.9 100% cpu load

[Tor Bug Tracker & Wiki]

#24857: tor 0.3.1.9 100% cpu load
-+
 Reporter:  Eugene646|  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor: 0.3.2.9
 Severity:  Normal   | Resolution:
 Keywords:  cpu, windows, linux  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by cypherpunks):

 Please, test with https://blog.torproject.org/tor-0332-alpha-released-
 bugfixes-and-dos-prevention

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25342 [Internal Services/Tor Sysadmin Team]: Please sync recent Apache web server logs from torproject.org hosts to colchicifolium

[Tor Bug Tracker & Wiki]

#25342: Please sync recent Apache web server logs from torproject.org hosts to
colchicifolium
-+-
 Reporter:  karsten  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 We're soon going to sanitize and publish web server logs from
 torproject.org hosts on CollecTor. It's going to take over the job that's
 currently running on wendelboi, but please don't shut that down yet.

 As first step, can you please sync all recent Apache web server logs from
 torproject.org hosts to colchicifolium? I just created a new directory
 there, `/srv/collector.torproject.org/collector/in/webstats/` where all
 logs can be synced to, ideally using the same directory structure as on
 wendelboi.

 We'd like to set up everything on CollecTor and run it for a few weeks
 before switching over. That would be a new ticket then.

 Thanks in advance!

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

Re: [tor-bugs] #23136 [Applications/Tor Launcher]: moat integration (fetch bridges for the user)

[Tor Bug Tracker & Wiki]

#23136: moat integration (fetch bridges for the user)
---+--
 Reporter:  mcs|  Owner:  brade
 Type:  defect | Status:  needs_review
 Priority:  Very High  |  Milestone:
Component:  Applications/Tor Launcher  |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201802R  |  Actual Points:
Parent ID:  #24689 | Points:
 Reviewer: |Sponsor:  Sponsor4
---+--

Comment (by anonym):

 BTW, I've noticed that the Moat radio button ("Request a bridge…") is only
 available if default bridges are available (currently we ship none in
 Tails, so I'd say it is not a rare edge case). IMHO, since default bridges
 in fact are not required for Moat, it would make sense to show the Moat
 and custom text entry options 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] #6236 [Core Tor/Tor]: Remove duplicate code between parse_{c, s}method_line

[Tor Bug Tracker & Wiki]

#6236: Remove duplicate code between parse_{c,s}method_line
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client easy refactor duplicate-  |  Actual Points:
  code   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by asn):

 Replying to [comment:13 fristonio]:
 > Sorry asn I was a bit busy with my exams.
 >
 > I have created a patch for this
 https://github.com/fristonio/tor/tree/ticket-6236
 > Please have a look and suggest any changes if required.

 Hello! Thanks for the code! Concept looks pretty good!

 Some simplification suggestions:
 a) You don't really need to compare `proto_method` with `PROTO_CMETHOD`
 since you control those two things yourself anyway. Instead of
 `proto_method`, I'd pass an `is_smethod` boolean variable to the helper
 function which would specify whether it's an SMETHOD or CMETHOD line. That
 way you don't need to do all these strcmps either, and you can just do `if
 (is_smethod) { }`.
 b) You don't really need this `proxy_manager` thing. You just use it in a
 log statement, and there you can do:
 {{{
 log_warn(LD_CONFIG, "%s managed proxy sent us a %s line "
  "with too few arguments.", is_smethod ? "Server" : "Client",
  proto_method);
 }}}
 c) You don't need the `else` clause in the final logging if block. Since
 you have already validated on top that `proto_method` is either CMETHOD or
 SMETHOD.
 d) You don't need to pass `SMETHOD_MIN_ARGS_COUNT` as a function argument.
 Instead you can set `min_args_count` inside the helper function based on
 `is_smethod`.

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

Re: [tor-bugs] #6236 [Core Tor/Tor]: Remove duplicate code between parse_{c, s}method_line

[Tor Bug Tracker & Wiki]

#6236: Remove duplicate code between parse_{c,s}method_line
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client easy refactor duplicate-  |  Actual Points:
  code   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by asn):

 * status:  new => needs_revision


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

Re: [tor-bugs] #6236 [Core Tor/Tor]: Remove duplicate code between parse_{c, s}method_line

[Tor Bug Tracker & Wiki]

#6236: Remove duplicate code between parse_{c,s}method_line
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client easy refactor duplicate-  |  Actual Points:
  code   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by fristonio):

 Thanks a lot, those strcmp's were looking a real pain when I was writing
 them. It was a valuable suggestion from your side. :)

 I have updated the branch with the changes you asked, can you have another
 look https://github.com/fristonio/tor/tree/ticket-6236.

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

Re: [tor-bugs] #6236 [Core Tor/Tor]: Remove duplicate code between parse_{c, s}method_line

[Tor Bug Tracker & Wiki]

#6236: Remove duplicate code between parse_{c,s}method_line
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  task | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-client easy refactor duplicate-  |  Actual Points:
  code   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by asn):

 Replying to [comment:16 fristonio]:
 > Thanks a lot, those strcmp's were looking a real pain when I was writing
 them. It was a valuable suggestion from your side. :)
 >
 > I have updated the branch with the changes you asked, can you have
 another look https://github.com/fristonio/tor/tree/ticket-6236.

 Hello, that looks good.

 I also pushed a squash commit in branch `ticket-6236` in my repo:
 https://gitweb.torproject.org/user/asn/tor.git

 Please check it out, and if you like it, squash it into your branch (so
 that the final branch only has one commit) and push it out. Then mark this
 ticket as `merge_ready`.

 Thanks! And props for writing a changes 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] #21323 [Applications/Tor Browser]: Activate mixed content blocking

[Tor Bug Tracker & Wiki]

#21323: Activate mixed content blocking
-+-
 Reporter:  arthuredelstein  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  TorBrowserTeam201705R,   |  Actual Points:
  GeorgKoppen201705  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 Mozilla implemented in FF60 Mixed Content upgrading for static content
 https://bugzilla.mozilla.org/show_bug.cgi?id=1435733 Doesn't fix the
 underlying issue with HTTPS-E but may be interesting to flip for more
 security.

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

Re: [tor-bugs] #24309 [Applications/Tor Browser]: Activity 4.1: Improve how circuits are displayed to the user

[Tor Bug Tracker & Wiki]

#24309: Activity 4.1: Improve how circuits are displayed to the user
---+--
 Reporter:  isabela|  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ux-team, TorBrowserTeam201802  |  Actual Points:
Parent ID: | Points:
 Reviewer:  antonela   |Sponsor:
---+--

Comment (by cypherpunks):

 Wouldn't what antonela proposed apply to the Android version as well so as
 to incorporate a circuit display and a new identity button in the Tor
 Browser for mobile? Firefox for Android, just like the desktop version,
 does show the padlock icon with HTTPS and shows a globe icon with HTTP,
 when clicking on them one can have the same result as when one clicks on
 the "i" icon in the URL bar in the desktop version.

 (Credits: This idea was inspired by gk's proposal, in particular the
 discussion in 2.2 https://lists.torproject.org/pipermail/tbb-
 dev/2018-February/000756.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] #25345 [Obfuscation/Snowflake]: Adapt broker to use ACME HTTP-01 challenge for automatic certificates

[Tor Bug Tracker & Wiki]

#25345: Adapt broker to use ACME HTTP-01 challenge for automatic certificates
---+--
 Reporter:  dcf|  Owner:  dcf
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by dcf):

 * Attachment "0001-Use-Manager.HTTPHandler-for-automatic-TLS-
 support.patch" 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] #25345 [Obfuscation/Snowflake]: Adapt broker to use ACME HTTP-01 challenge for automatic certificates

[Tor Bug Tracker & Wiki]

#25345: Adapt broker to use ACME HTTP-01 challenge for automatic certificates
---+--
 Reporter:  dcf|  Owner:  dcf
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by dcf):

 * status:  assigned => needs_review


Comment:

 Here is a simple patch for review. I just now started it running on https
 ://snowflake-broker.bamsoftware.com/ and it seems to be working (just
 issued a fresh certificate).

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

Re: [tor-bugs] #24928 [Obfuscation/meek]: Use `Manager.HTTPHandler` (ACME "HTTP-01" challenge) for automatic certificates

[Tor Bug Tracker & Wiki]

#24928: Use `Manager.HTTPHandler` (ACME "HTTP-01" challenge) for automatic
certificates
--+-
 Reporter:  dcf   |  Owner:  dcf
 Type:  project   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by dcf):

 Similar ticket for Snowflake broker: #25345.

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

Re: [tor-bugs] #25137 [Obfuscation/Censorship analysis]: Tor blocked in UAE

[Tor Bug Tracker & Wiki]

#25137: Tor blocked in UAE
-+
 Reporter:  mwolfe   |  Owner:  dcf
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Obfuscation/Censorship analysis  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  censorship block ae  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by dcf):

 Replying to [comment:29 cypherpunks]:
 > Well it doesn't work even for me, so no worries, the censors still have
 no clue about snowflake ;)

 It's working for me just now (using the command-line client, I didn't test
 in Tor Browser).
 {{{
 tor -f torrc.local SOCKSPort auto
 }}}
 torrc.local contains:
 {{{
 UseBridges 1
 ClientTransportPlugin snowflake exec ./client -url https://snowflake-
 reg.appspot.com/ -front www.google.com -ice stun:stun.l.google.com:19302
 -log snowflake.log
 Bridge snowflake 0.0.3.0:1
 }}}
 I upgraded and restarted
 
[https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6915AB06BFB7F
 the bridge] a few hours ago, and the transport plugin didn't start back up
 immediately, so that may be why you weren't able to connect.

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

Re: [tor-bugs] #24191 [Internal Services/Service - trac]: Remove trac spam prevention from GRP_devel people

[Tor Bug Tracker & Wiki]

#24191: Remove trac spam prevention from GRP_devel people
--+-
 Reporter:  arma  |  Owner:  qbi
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by dcf):

 I noticed ewyatt had trouble at comment:2:ticket:25336:
 > The posting was originally rejected for containing (the non-modified
 versions of) these two words: he[@]lthy and m![0]ney.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor: 0.3.3.x-final
Component:  Core |Version:  Tor: 0.3.0.6
  Tor/Tor|   Keywords:  033-must, tor-guard, tor-client,
 Severity:  Normal   |  tbb-usability-website, tbb-needs
Actual Points:   |  Parent ID:  #21969
   Points:  1|   Reviewer:
  Sponsor:   |
-+-
 When Tor can't download microdescriptors (#21969), maybe it should try
 authorities or fallbacks (#23863), before it runs out of microdesc retries
 (#24113).

 But even after Tor has the microdescs it needs, it sometimes doesn't start
 building circuits again. Instead, it is in state "waiting for circuit".

 For the log messages, see:
 https://trac.torproject.org/projects/tor/ticket/21969#comment:82

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

Re: [tor-bugs] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
-+-
 Reporter:  asn  |  Owner:  asn
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Blocker  | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client,   |  Actual Points:
  tbb-usability-website, tbb-needs   |
Parent ID:   | Points:  1.5
 Reviewer:   |Sponsor:
 |  SponsorV
-+-

Comment (by teor):

 Please don't post the same logs on multiple tickets, it makes it hard to
 track the response.

 Here are all the related tickets:

 When Tor can't download microdescriptors (#21969), maybe it should try
 authorities or fallbacks (#23863), before it runs out of microdesc retries
 (#24113). But even after Tor has the microdescs it needs, it sometimes
 doesn't start building circuits again. Instead, it is in state "waiting
 for circuit" (#25347).

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

Re: [tor-bugs] #23863 [Core Tor/Tor]: When our directory guards don't have each others' microdescs, we should try an authority or fallback

[Tor Bug Tracker & Wiki]

#23863: When our directory guards don't have each others' microdescs, we should 
try
an authority or fallback
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client,   |  Actual Points:
  033-maybe-must |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  tor-guard, tor-bridge, tor-client => tor-guard, tor-bridge,
 tor-client, 033-maybe-must
 * milestone:  Tor: 0.3.4.x-final => Tor: 0.3.3.x-final


Comment:

 Here are all the related tickets:

 When Tor can't download microdescriptors (#21969), maybe it should try
 authorities or fallbacks (#23863), before it runs out of microdesc retries
 (#24113). But even after Tor has the microdescs it needs, it sometimes
 doesn't start building circuits again. Instead, it is in state "waiting
 for circuit" (#25347).

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

Re: [tor-bugs] #24113 [Core Tor/Tor]: We stop trying to download an md after 8 failed tries

[Tor Bug Tracker & Wiki]

#24113: We stop trying to download an md after 8 failed tries
-+-
 Reporter:  asn  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client,   |  Actual Points:
  033-maybe-must |
Parent ID:  #21969   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  tor-guard, tor-bridge, tor-client => tor-guard, tor-bridge,
 tor-client, 033-maybe-must
 * milestone:  Tor: 0.3.4.x-final => Tor: 0.3.3.x-final


Comment:

 We are potentially seeing this issue in 0.3.2.9, see the logs on #21969.

 When Tor can't download microdescriptors (#21969), maybe it should try
 authorities or fallbacks (#23863), before it runs out of microdesc retries
 (#24113). But even after Tor has the microdescs it needs, it sometimes
 doesn't start building circuits again. Instead, it is in state "waiting
 for circuit" (#25347).

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

Re: [tor-bugs] #25343 [Applications/Tor Browser]: disable F11 as fullscreen

[Tor Bug Tracker & Wiki]

#25343: disable F11 as fullscreen
--+--
 Reporter:  catperson |  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 teor):

 * version:  Tor: unspecified =>


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

Re: [tor-bugs] #25348 [Community/Relays]: Add instructions for OpenBSD, amend FreeBSD to also mention obfs4

[Tor Bug Tracker & Wiki]

#25348: Add instructions for OpenBSD, amend FreeBSD to also mention obfs4
--+
 Reporter:  attila|  Owner:  Nusenu
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Relays  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by attila):

 * Attachment "tpo-relayguide.diff" added.

 patch to TorRelayGuide.txt

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

Re: [tor-bugs] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  033-must, tor-guard, tor-client, tbb-usability-website, tbb-
 needs =>
 031-backport, 032-backport, 033-must, tor-guard, tor-client, tbb-
 usability-website, tbb-needs


Comment:

 I think we just need to fix #25347 in 0.3.3, all the other related tickets
 are ok.
 And when we fix it. We should backport to 031 and 032.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25346 [Obfuscation/Snowflake]: Adapt snowflake-server to use ACME HTTP-01 challenge for automatic certificates

[Tor Bug Tracker & Wiki]

#25346: Adapt snowflake-server to use ACME HTTP-01 challenge for automatic
certificates
---+
 Reporter:  dcf|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 As with the broker (#25345), we need to make the Snowflake server
 transport plugin use the HTTP-01 challenge.

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

Re: [tor-bugs] #25020 [Applications/Tor Browser]: There should be an easy way to detect the version of an installed bundle.

[Tor Bug Tracker & Wiki]

#25020: There should be an easy way to detect the version of an installed 
bundle.
+--
 Reporter:  yawning |  Owner:  tbb-team
 Type:  enhancement | Status:  closed
 Priority:  Low |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-rbm, TorBrowserTeam201802R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by cypherpunks):

 The file name is tbb_verson.json instead of tbb_version.json

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

Re: [tor-bugs] #25020 [Applications/Tor Browser]: There should be an easy way to detect the version of an installed bundle.

[Tor Bug Tracker & Wiki]

#25020: There should be an easy way to detect the version of an installed 
bundle.
+--
 Reporter:  yawning |  Owner:  tbb-team
 Type:  enhancement | Status:  closed
 Priority:  Low |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-rbm, TorBrowserTeam201802R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by boklm):

 Thanks for reporting this. I fixed the file name in commit
 e7e4cbd526d767d46fe6f728c99492e7e3d6e76c.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25348 [Community/Relays]: Add instructions for OpenBSD, amend FreeBSD to also mention obfs4

[Tor Bug Tracker & Wiki]

#25348: Add instructions for OpenBSD, amend FreeBSD to also mention obfs4
--+
 Reporter:  attila|  Owner:  Nusenu
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Community/Relays  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I really like the new TorRelayGuide and have attached a patch to improve
 it in two ways:

 1. add a section for OpenBSD under Tor Relay Setup
 2. amend the FreeBSD section to mention obfs4proxy

 Patch attached

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

Re: [tor-bugs] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
-+-
 Reporter:  asn  |  Owner:  asn
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Blocker  | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client,   |  Actual Points:
  tbb-usability-website, tbb-needs   |
Parent ID:   | Points:  1.5
 Reviewer:   |Sponsor:
 |  SponsorV
-+-

Comment (by teor):

 I think we just need to fix #25347 in 0.3.3.

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

Re: [tor-bugs] #24113 [Core Tor/Tor]: We stop trying to download an md after 8 failed tries

[Tor Bug Tracker & Wiki]

#24113: We stop trying to download an md after 8 failed tries
---+---
 Reporter:  asn|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.4.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.3.0.6
 Severity:  Normal | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client  |  Actual Points:
Parent ID:  #21969 | Points:
 Reviewer: |Sponsor:
---+---
Changes (by teor):

 * keywords:  tor-guard, tor-bridge, tor-client, 033-maybe-must => tor-
 guard, tor-bridge, tor-client
 * milestone:  Tor: 0.3.3.x-final => Tor: 0.3.4.x-final


Comment:

 I think we just need to fix #25347 in 0.3.3.

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

Re: [tor-bugs] #23863 [Core Tor/Tor]: When our directory guards don't have each others' microdescs, we should try an authority or fallback

[Tor Bug Tracker & Wiki]

#23863: When our directory guards don't have each others' microdescs, we should 
try
an authority or fallback
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:  Tor:
   |  0.3.4.x-final
Component:  Core Tor/Tor   |Version:  Tor:
   |  0.3.0.6
 Severity:  Normal | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client  |  Actual Points:
Parent ID:  #21969 | Points:  1
 Reviewer: |Sponsor:
---+---
Changes (by teor):

 * keywords:  tor-guard, tor-bridge, tor-client, 033-maybe-must => tor-
 guard, tor-bridge, tor-client
 * milestone:  Tor: 0.3.3.x-final => Tor: 0.3.4.x-final


Comment:

 I think we can fix this issue by fixing #25347 in 0.3.3 and backporting.

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

[tor-bugs] #25349 [Webpages/Website]: http://deb.torproject.org/ Is offline

[Tor Bug Tracker & Wiki]

#25349: http://deb.torproject.org/ Is offline
--+
 Reporter:  Dbryrtfbcbhgf |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 http://deb.torproject.org/ Is offline and I can not apt update tor from my
 relay.

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

Re: [tor-bugs] #25349 [Webpages/Website]: http://deb.torproject.org/ Is offline

[Tor Bug Tracker & Wiki]

#25349: http://deb.torproject.org/ Is offline
--+-
 Reporter:  Dbryrtfbcbhgf |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  invalid
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by pastly):

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


Comment:

 Someone is DDoSing Tor infrastructure. Lots of stuff is down.

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

Re: [tor-bugs] #21969 [Core Tor/Tor]: We're missing descriptors for some of our primary entry guards

[Tor Bug Tracker & Wiki]

#21969: We're missing descriptors for some of our primary entry guards
-+-
 Reporter:  asn  |  Owner:  asn
 Type:  defect   | Status:  new
 Priority:  Immediate|  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Blocker  | Resolution:
 Keywords:  tor-guard, tor-bridge, tor-client,   |  Actual Points:
  tbb-usability-website, tbb-needs   |
Parent ID:   | Points:  1.5
 Reviewer:   |Sponsor:
 |  SponsorV
-+-

Comment (by s7r):

 I agree teor, especially because the hang occurs even long after Tor said
 it has enough directory info to build circuits and even claims to open
 one:
 {{{
 2/24/2018 19:47:29 PM.300 [NOTICE] Tor has successfully opened a circuit.
 Looks like client functionality is working.
 2/24/2018 20:50:07 PM.600 [NOTICE] Tried for 120 seconds to get a
 connection to [scrubbed]:443. Giving up. (waiting for circuit)
 }}}

 Not even a full restart will make it heal. I'll post logs and details in
 #25347

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

Re: [tor-bugs] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by s7r):

 * Attachment "tbb-hang-253347.png" 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] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by s7r):

 * Attachment "debug_25347.zip" 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] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by s7r):

 * Attachment "info_25347.zip" 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] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by s7r):

 Looks like it's more serious.
 So the jammed Tor instance that generated the logs in #21969 never healed
 even after 7 hours of waiting. Was running TBB 7.5 so it was Tor 0.3.2.9.

 Switched to info log level, closed TBB and launched again. Tor launcher
 never fully load, and was just blocked in the loading state with text
 "Establishing a Tor circuit". Captured and attached a screenshot for this.
 I gathered info log for few minutes in this state, and terminated by
 clicking cancel on Tor launcher.

 Then I switched to debug log level and launched again. Tor launcher
 remained blocked at the same loading level as before. I left it in this
 state and gathered debug logs for about 20 minutes, then clicked cancel on
 Tor launcher to close.

 Tried about 5 more times, still the same result. The only thing that fixed
 it was the deletion of the '''state''' file. After I deleted the state
 file, Tor launcher fully loaded in about 3 seconds and browsing went on
 just 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] #25333 [Applications/Tor Browser]: NOT SECURE CONECTION please help

[Tor Bug Tracker & Wiki]

#25333: NOT SECURE CONECTION please help
--+---
 Reporter:  kiokawasaki1998   |  Owner:  (none)
 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 Dude_Virus):

 Replying to [comment:35 mario]:
 > Replying to [comment:34 Dude_Virus]:
 > My dear Dude_Virus,
 > I can't provide more info about a part my workaround as above.
 >
 > 1) I can only confirm that the issue is present ONLY when I use Tor
 browser and I attempt to use the https protocol. http is working with TOR
 (at least for the few website that I tested)
 > 2) The issue disappears if I uncheck the kaspersky setting "do not scan
 encrypted ..."
 > 3) If I switch off the TOR browser and restore the standard Kaspersky
 settings ALL is perfectly working
 >
 > Bye
 > Mario


 Hi Mario

 For me even if I try www.google.com it fails because the URL is changing
 to https://www.google.com. Even after disabling HTTPS everywhere it still
 forces the site to go to https.

 Another thing that I noticed was that at the bottom the status keeps
 flipping between connected and then connecting. It keeps doing that for a
 few times and then I get the secure connection failed.
 I found another workaround that if you add the websites in the exclusion
 list then in spite of the setting being

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

Re: [tor-bugs] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 I wonder if (both?) your guards stopped responding to your extend
 requests, due to a DDoS defence? (Or due to overload?)
 Do you still have your old guard state?
 What are the versions of your guards?

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

[tor-bugs] #25350 [Core Tor/Tor]: Cannot connect, even with bridges

[Tor Bug Tracker & Wiki]

#25350: Cannot connect, even with bridges
--+
 Reporter:  twoball   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Major |   Keywords:  Net Neutrality, connection
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 I am unable to make any connections with the TOR network through my
 verizon FIOS home connections using the up to date TOR browser.  I cannot
 reach check.torproject.org at all.  I have tried all routine bridges:
 obfs4, obfs3, direct connections, etc.  I have never had any trouble
 connecting before now.  I have tried to connect from Android, Windows 10,
 Ubuntu LTS 16 and two other linux distros and cannot get a connection to
 the network.  I am worried verizon is abusing the net neutrality rules
 that were just rescinded to block my access to the network.

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

Re: [tor-bugs] #25347 [Core Tor/Tor]: Tor stops building circuits, and doesn't start when it has enough directory information

[Tor Bug Tracker & Wiki]

#25347: Tor stops building circuits, and doesn't start when it has enough 
directory
information
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.6
 Severity:  Normal   | Resolution:
 Keywords:  031-backport, 032-backport,  |  Actual Points:
  033-must, tor-guard, tor-client, tbb-  |
  usability-website, tbb-needs   |
Parent ID:  #21969   | Points:  1
 Reviewer:   |Sponsor:
-+-

Comment (by s7r):

 Usually when guards stop responding Tor logs a message that guard X is
 failing more circuits than usual.

 I have the guards versions yes, they are all 3 online with no downtime in
 the last days.

 Guard 1/3: Tor 0.2.5.16
 Guard 2/3: Tor 0.2.9.14
 Guard 3/3: Tor 0.2.9.14

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25351 [- Select a component]: https://www.torproject.org not work

[Tor Bug Tracker & Wiki]

#25351: https://www.torproject.org not work
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 http://www.isitdownrightnow.com/torproject.org.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] #25350 [Applications/Tor Check]: Cannot connect, even with bridges

[Tor Bug Tracker & Wiki]

#25350: Cannot connect, even with bridges
+-
 Reporter:  twoball |  Owner:  arlolra
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Check  |Version:
 Severity:  Normal  | Resolution:  invalid
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+-
Changes (by teor):

 * status:  new => closed
 * severity:  Major => Normal
 * component:  Core Tor/Tor => Applications/Tor Check
 * priority:  High => Medium
 * owner:  (none) => arlolra
 * milestone:  Tor: unspecified =>
 * keywords:  Net Neutrality, connection =>
 * resolution:   => invalid


Comment:

 check.torproject.org is down.
 You can use any of the onion sites at https://onion.torproject.org to
 check instead.

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