Re: [tor-bugs] #32808 [Core Tor/Tor]: I can't connect anymore to tor 2

[Tor Bug Tracker & Wiki]

#32808: I can't connect anymore to tor 2
--+--
 Reporter:  rlko  |  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:
--+--

Comment (by rlko):

 someoe?

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

Re: [tor-bugs] #29801 [Core Tor/Tor]: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients

[Tor Bug Tracker & Wiki]

#29801: Write a proposal for IPv6 "Happy Eyeballs" on Tor clients
-+-
 Reporter:  neel |  Owner:  neel
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, prop299,   |  Actual Points:
  042-deferred-20190918  |
Parent ID:  #17835   | Points:
 Reviewer:  nickm, asn, teor |Sponsor:
-+-
Changes (by neel):

 * status:  needs_revision => needs_review


Comment:

 It probably isn't perfect, but I have made revisions:
 https://lists.torproject.org/pipermail/tor-dev/2019-December/014113.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] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by starlight):

 next above seems a direct an reasonably clean way to solve it, easy to
 tweak to exclude different authorities that might become difficult to
 reach; will give that a try

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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by starlight):

 oops, I incorrectly projected 'data' had a config for authorities, so
 instead perhaps a dict with authorities to not check directly while
 eliminating the hard-coded tor26 removal from the list acquired from STEM
 via stem.directory.Authority.from_cache()?

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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by starlight):

 Replying to [comment:12 atagar]:
 > > Alternately if DocTor were to check the consensus for tor26, it might
 as well check for the presence of all authorities and report any missing.
 >
 > Actually, DocTor already does...

 Would a new flag in the authority config that suppresses direct checking,
 in place of the present hard-coded exclusion for tor26 work?  The config
 for tor26 goes back in with the flag set, direct checks are disabled and
 the existing in-consensus check will report when it's missing?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32848 [Core Tor]: torsocks autentication clarification

[Tor Bug Tracker & Wiki]

#32848: torsocks autentication clarification
-+--
 Reporter:  toruser2019  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Component:  Core Tor
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
 I need a bit more clarification on these options, I am not sure I
 understand it correctly.
 To avoid confusion between terms (client, server, socks, proxy, etc), I
 better explain exactly what I am doing:

 I use commands like torsocks with wget to get content from .onion
 website(s), like so:

 **torsocks wget somewebsite12345.onion/file.html**

 but network is not very reliable and I want to try that from additional
 locations (additional "tor clients" I guess).

 I understand I can configure my additional servers to connect to tor, I
 did this by enabling this in my second server **torrc** file:

 # listen on own server 2 IP
 SOCKSPort 2.2.2.2:9050

 # allow connections from server 1 IP
 SOCKSPolicy accept 1.1.1.1
 SOCKSPolicy reject *

 So now from my server 1.1.1.1 I can connect to tor network using second
 server like this:

 **torsocks --address 2.2.2.2 wget somewebsite12345.onion/file.html**

 But my server 1 IP is not static, considering all the many options inside
 **torrc** and **torsocks.conf** , is there an option to configure
 autentication for the above ? (So I can then set server 2 torrc file to
 allow connections from any ip).

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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by atagar):

 > Which is "less bad?

 The best option is for tor26 to remove its block. Second best is one of
 the following...

 a. Do nothing (which is why I closed this ticket).
 b. Adjust DocTor's _get_documents() to monkey patch or do other hackery
 work around tor26's dysfunction.
 c. Adjust the has_authority_flag test to specially handle tor26.

 > Alternately if DocTor were to check the consensus for tor26, it might as
 well check for the presence of all authorities and report any missing.

 Actually, DocTor already does...

 https://gitweb.torproject.org/doctor.git/tree/consensus_health_checker.py#n632

 > Seems to me nothing special should be required for testing DocTor except
 changing the email notification address, is is that true?

 You shouldn't need to do anything. When ran locally DocTor prints its
 notification rather than emailing it.

 https://gitweb.torproject.org/doctor.git/tree/util.py#n21

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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by starlight):

 I see

 >commit 5bae2023
 >Date:   Wed Apr 11 08:58:31 2018 -0700
 >To cut down on abuse tor26 rejects DirPort requests without a '.z' suffix
 (technically it throttles them, but I've never seen one work so
 effectively it's blocked). Stem no longer appends this suffix, using
 headers to indicatee the compression it wants instead.

 This could be solved by reverting 5bae2023 and 93c3a9b4 and making the
 change described above to STEM to add .z when any compression is
 requested, but it seems you dislike the approach.  Or by checking the
 consensus for Tor26 as first indicated above, which is probably more work
 though I have not looked at at it.  Which is "less bad?"  If the .z hack
 were applied only when an option in STEM was present would it be more
 palpable?  Alternately if DocTor were to check the consensus for tor26, it
 might as well check for the presence of all authorities and report any
 missing.

 Seems to me nothing special should be required for testing DocTor except
 changing the email notification address, is is that true?

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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by atagar):

 > an adjustment to _download_descriptors() in stem/descriptor/remote.py

 Sorry, a patch to account for tor26's dysfunction will need to reside
 within DocTor rather than Stem.

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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by starlight):

 I can write one, an adjustment to _download_descriptors() in
 stem/descriptor/remote.py to append .z when compression is enabled covers
 it?  Or more to it?

 Before the making the change, I notice tor26 appears to have no problem
 serving descriptors and full consensus in PLAIN / GZIP / ZSTD form on both
 the dir and or ports to STEM.  Perhaps the patch or iptables rule
 suppressing requests absent a .z suffix has been left out or eliminated?

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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by atagar):

 Could. There's many hacks that can work around it. I just don't see merit
 in tor26's block.

 If someone else cares enough to submit a patch I'll merge 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] #32847 [Applications/Tor Browser]: Tor crashes when quitting Tor Browser nightly on macOS

[Tor Bug Tracker & Wiki]

#32847: Tor crashes when quitting Tor Browser nightly on macOS
--+--
 Reporter:  rex4539   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:  Tor: 0.4.2.5
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by rex4539):

 * Attachment "tor.real_2019-12-26-211706_MacBook-Pro-2018.crash" 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

[tor-bugs] #32847 [Applications/Tor Browser]: Tor crashes when quitting Tor Browser nightly on macOS

[Tor Bug Tracker & Wiki]

#32847: Tor crashes when quitting Tor Browser nightly on macOS
--+--
 Reporter:  rex4539   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Component:  Applications/Tor Browser
  Version:  Tor: 0.4.2.5  |   Severity:  Normal
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 Reproducibility: often

 Steps:
 Quit Tor Browser Nightly.

 What happened:
 Crash.

 Expected result:
 No crash.

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

Re: [tor-bugs] #32846 [Core Tor/Tor]: Tor Manual: Alphabetize Client Options

[Tor Bug Tracker & Wiki]

#32846: Tor Manual: Alphabetize Client Options
-+-
 Reporter:  swati|  Owner:  (none)
 Type:  project  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation, tor-client, manpage,  |  Actual Points:
  gsod   |
Parent ID:  #4310| Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 swati: I just added you to GRP_user on trac, which should give you more
 permissions than you had before.

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

Re: [tor-bugs] #32846 [Core Tor/Tor]: Tor Manual: Alphabetize Client Options

[Tor Bug Tracker & Wiki]

#32846: Tor Manual: Alphabetize Client Options
-+-
 Reporter:  swati|  Owner:  (none)
 Type:  project  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation, tor-client, manpage,  |  Actual Points:
  gsod   |
Parent ID:  #4310| Points:
 Reviewer:   |Sponsor:
-+-
Changes (by arma):

 * status:  new => needs_review


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

Re: [tor-bugs] #32846 [Core Tor/Tor]: Tor Manual: Alphabetize Client Options

[Tor Bug Tracker & Wiki]

#32846: Tor Manual: Alphabetize Client Options
-+-
 Reporter:  swati|  Owner:  (none)
 Type:  project  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  documentation, tor-client, manpage,  |  Actual Points:
  gsod   |
Parent ID:  #4310| Points:
 Reviewer:   |Sponsor:
-+-

Comment (by swati):

 This is the PR for this ticket -
 https://github.com/torproject/tor/pull/1632.

 Please review.

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

[tor-bugs] #32846 [Core Tor/Tor]: Tor Manual: Alphabetize Client Options

[Tor Bug Tracker & Wiki]

#32846: Tor Manual: Alphabetize Client Options
-+-
 Reporter:  swati|  Owner:  (none)
 Type:  project  | Status:  new
 Priority:  Medium   |  Component:  Core
 |  Tor/Tor
  Version:   |   Severity:  Normal
 Keywords:  documentation, tor-client, manpage,  |  Actual Points:
  gsod   |
Parent ID:  #4310| Points:
 Reviewer:   |Sponsor:
-+-
 This ticket is for the alphabetical sorting of Client options. Making this
 a child ticket for #4310.

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

Re: [tor-bugs] #31011 [Core Tor/Tor]: Make the bridge authority reject private PT addresses when DirAllowPrivateAddresses is 0

[Tor Bug Tracker & Wiki]

#31011: Make the bridge authority reject private PT addresses when
DirAllowPrivateAddresses is 0
---+---
 Reporter:  teor   |  Owner:  cjb
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:  Tor:
   |  unspecified
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:
 Keywords:  anti-censorship-roadmap-september  |  Actual Points:
Parent ID:  #31009 | Points:  1
 Reviewer: |Sponsor:
   |  Sponsor28-can
---+---
Changes (by cjb):

 * owner:  (none) => cjb
 * status:  new => assigned


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

Re: [tor-bugs] #32842 [Core Tor/DocTor]: Give notifications if tor26 is missing from the consensus

[Tor Bug Tracker & Wiki]

#32842: Give notifications if tor26 is missing from the consensus
-+-
 Reporter:  Sebastian|  Owner:  atagar
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Core Tor/DocTor  |Version:
 Severity:  Normal   | Resolution:  wontfix
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by starlight):

 interesting, so compression can be requested either via .z suffix or a
 HTTP attribute, why not just tack on the .z anyway?

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

Re: [tor-bugs] #32840 [Internal Services/Tor Sysadmin Team]: Issue with cloud.ipnett.se

[Tor Bug Tracker & Wiki]

#32840: Issue with cloud.ipnett.se
-+
 Reporter:  hiro |  Owner:  tpa
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by hiro):

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


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

[tor-bugs] #32845 [Core Tor/Tor]: Add UTF-8 validation unit tests

[Tor Bug Tracker & Wiki]

#32845: Add UTF-8 validation unit tests
--+
 Reporter:  teor  |  Owner:  teor
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  043-should, utf-8, Unicode
Actual Points:|  Parent ID:
   Points:  0.2   |   Reviewer:
  Sponsor:|
--+
 We should add unit tests for the following UTF-8 sequences. Their validity
 varies between different programming languages. We should go with the
 common case (if it matches the standard).

 Invalid:
 surrogate nullsurrog threehigh
 EDA081 3000EDA081 EDBFBF

 fourhigh fivebyte sixbyte sixhigh
 F490BFBF FB80808080 FD80808080 FDBFBFBFBF

 Valid:
 fourbyte fourbyte2
 F0908D88 F0BFBFBF

 Valid in the Unicode standard, invalid in torrcs and directory documents:
 nullbyte
 3031320033

 See proposal 285 for details, and for the null byte exception:
 https://gitweb.torproject.org/torspec.git/tree/proposals/285-utf-8.txt

 Test Case Source:
 `POC||GTFO 19`, page 43
 https://www.alchemistowl.org/pocorgtfo/

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