[tor-bugs] #33549 [Metrics]: Simplify logging configuration across code bases

[Tor Bug Tracker & Wiki]

#33549: Simplify logging configuration across code bases
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  assigned
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 We're using different logging configurations in our code bases, some of
 which are broken and others are more complex than we need them to be. Some
 examples:

  - CollecTor has a shutdown console logger, but it's not being printed to
 anymore since we refactored package names.
  - CollecTor has five separate log files for the modules that existed back
 when we added those log files, but these are not being written to since we
 refactored package names. We also added more modules but did not update
 the logging configuration for them.
  - Onionoo and a few others have a separate error log file which logs only
 ERROR messages, but we're not doing anything with that file.
  - Some code bases have a separate statistics log file that we likewise do
 not pay any attention to.
  - All code bases rotate log files whenever they reach a size of 1 MiB,
 but they do not restrict the number or total size of log files being
 written. It would be easier to handle 1 file per day even if that grows to
 100 MiB or more.
  - There could be a more reasonable default for the log directory than
 `LOGBASE_IS_UNDEFINED`.
  - It would be convenient to be able to configure the log level that
 doesn't require providing a full logging configuration, like
 `-DLOGLEVEL=DEBUG`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33549 [Metrics]: Simplify logging configuration across code bases

[Tor Bug Tracker & Wiki]

#33549: Simplify logging configuration across code bases
-+--
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:
Component:  Metrics  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

 * status:  assigned => needs_review


Comment:

 I have the beginning of a patch in
 [https://gitweb.torproject.org/user/karsten/metrics-
 base.git/commit/?h=task-33549&id=fd856466bcb260f53ef69a24c102d0e49d171cc3
 commit fd85646 in my metrics-base branch task-33549] that I'd like to
 discuss here together with the general direction as laid out above.

 Next steps after merging that metrics-base patch are to remove
 `logback.xml` files from other code bases, to remove logging code in all
 code bases to log to their class logger, and to test everything in local
 deployments.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33550 [- Select a component]: Bandbreiten Problem mit der Brücke

[Tor Bug Tracker & Wiki]

#33550: Bandbreiten Problem mit der Brücke
+--
 Reporter:  habus   |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  - Select a component
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
 Hi everyone.

 It looks like I can no longer reach the full bandwidth with my relay or my
 bridge. Are there currently problems in the network or is it due to my
 server? I released 16Mbits. And it looks like my bridge is not valid.
 Sorry, but I'm an absolute amateur.

 This is my bridge:
 
[https://metrics.torproject.org/rs.html#details/0A2A19DCF7D6C3D07CBDA06AF44A8B90114B8033]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33551 [Applications/Tor Browser]: Drag & Drop creation of Bookmark replaces title by url

[Tor Bug Tracker & Wiki]

#33551: Drag & Drop creation of Bookmark replaces title by url
--+--
 Reporter:  lkjfdgdsinms  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  Applications/Tor Browser
  Version:  0.4.2.6   |   Severity:  Normal
 Keywords:  bookmarks |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 I cannot select a TorBrowser version, I use 9.0.5, but I observed this
 years ago already. When you create a bookmark using drag & drop from the
 leftmost part of the navigation bar (information symbol, lock symbol etc.)
 the title of the bookmark is set with the value of the url, not with the
 title of the website.

 This does not happen with other "create bookmark" use cases and not in
 Firefox, so this is probably a 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

[tor-bugs] #33552 [Core Tor/Torsocks]: Unsupported syscall number 229 on Debian on torsocks 2.3.0

[Tor Bug Tracker & Wiki]

#33552: Unsupported syscall number 229 on Debian on torsocks 2.3.0
+---
 Reporter:  secureyourself  |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Very Low|  Component:  Core Tor/Torsocks
  Version:  0.4.2.6 |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
 arch is x64.
 Versions:
 Tor 0.4.2.6 running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.1d,
 Zlib 1.2.11, Liblzma 5.2.4, and Libzstd 1.3.8.

 I'm testing Interactive Brokers' TWS software on Tails OS (just for fun, I
 see it's not a use case, however, I hope this can help), but I've met a
 problem launching it:

 1583671114 WARNING torsocks[25196]: [syscall] Unsupported syscall number
 229. Denying the call (in tsocks_syscall() at syscall.c:605)
 1583671115 ERROR torsocks[25196]: Unable to resolve. Status reply: 4 (in
 socks5_recv_resolve_reply() at socks5.c:677)

 The application show an error message: Update Failed. Check log file for
 details: /home/amnesia/Jts/.intall4j/updater.log (see below).

 

 Steps to reproduce:
 1. Launch Tails 4.3.
 2. Download tws-latest-linux-x64.sh or tws-stable-linux-x64.sh from
 [https://www.interactivebrokers.com/en/index.php?f=14099#tws-software the
 official website].
 3. Run the installer: for example,
 {{{
 ./tws-stable-linux-x64.sh
 }}}

 4. After the installation, launch the application: from the installer or
 from Terminal:

 {{{
 torify "/home/amnesia/Jts/tws" -J-DjtsConfigDir="/home/amnesia/Jts" %U
 }}}

 or

 {{{
 . torsocks on
 "/home/amnesia/Jts/tws" -J-DjtsConfigDir="/home/amnesia/Jts" %U
 }}}


 5. You get:

 {{{
 1583672301 WARNING torsocks[26808]: [syscall] Unsupported syscall number
 229. Denying the call (in tsocks_syscall() at syscall.c:605)
 1583672301 ERROR torsocks[26808]: Unable to resolve. Status reply: 4 (in
 socks5_recv_resolve_reply() at socks5.c:677)
 1583672301 ERROR torsocks[26808]: Unable to resolve. Status reply: 4 (in
 socks5_recv_resolve_reply() at socks5.c:677)
 1583672302 ERROR torsocks[26808]: Unable to resolve. Status reply: 4 (in
 socks5_recv_resolve_reply() at socks5.c:677)
 1583672379 PERROR torsocks[26808]: socks5 libc connect: Invalid argument
 (in socks5_connect() at socks5.c:202)
 }}}

 

 See the log (Jts/.intall4j/updater.log):
 {{{
 [INFO] com.install4j.runtime.beans.actions.control.SetVariableAction [ID
 4839]: Execute action
Property script: com.install4j.script.I4jScript_Internal_62
Property variableName: updateDescriptorUrl
Property failIfNull: true
Property onlyIfUndefined: false
Property responseFileVariable: false
Property rollbackSupported: false
Variable changed:
 
updateDescriptorUrl=https://download2.interactivebrokers.com/installers/tws/stable
 /tws-stable-linux-x64.xml[class java.lang.String]
Execute action successful after 3 ms
 [INFO] com.install4j.runtime.beans.actions.update.CheckForUpdateAction [ID
 479]: Execute action
Property connectTimeout: 1
Property connectionFailureScript: null
Property readTimeout: 2
Property requestHeaders: []
Property url:
 https://download2.interactivebrokers.com/installers/tws/stable/tws-stable-
 linux-x64.xml
Property variable: updateDescriptor
Property acceptAllCertificates: false
Property askForProxy: true
Property rollbackSupported: false
Property showError: true
 [ERROR] com.install4j.runtime.beans.actions.update.CheckForUpdateAction
 [ID 479]: could not download file
 java.net.ConnectException: Invalid argument (connect failed)
 java.net.ConnectException: Invalid argument (connect failed)
 at java.net.PlainSocketImpl.socketConnect(Native Method)
 at
 java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
 at
 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
 at
 java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
 at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
 at java.net.Socket.connect(Socket.java:589)
 at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673)
 at sun.net.NetworkClient.doConnect(NetworkClient.java:175)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:463)
 at sun.net.www.http.HttpClient.openServer(HttpClient.java:558)
 at
 sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264)
 at
 sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367)
 at
 
sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191)
 at
 
sun.net.www.protocol.http.

Re: [tor-bugs] #16516 [Applications/Tor Browser]: TBB doesn't use page title when bookmarking by dragging globe/lock icon

[Tor Bug Tracker & Wiki]

#16516: TBB doesn't use page title when bookmarking by dragging globe/lock icon
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Thorin):

 #33551 is a duplicate

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

Re: [tor-bugs] #33551 [Applications/Tor Browser]: Drag & Drop creation of Bookmark replaces title by url

[Tor Bug Tracker & Wiki]

#33551: Drag & Drop creation of Bookmark replaces title by url
--+---
 Reporter:  lkjfdgdsinms  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by Thorin):

 * status:  new => closed
 * keywords:  bookmarks => tbb-usability
 * version:  0.4.2.6 =>
 * resolution:   => duplicate


Comment:

 duplicate of #16516

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33550 [- Select a component]: Bandbreiten Problem mit der Brücke

[Tor Bug Tracker & Wiki]

#33550: Bandbreiten Problem mit der Brücke
--+
 Reporter:  habus |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:   => Tor: 0.4.4.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33550 [Core Tor/Tor]: Bandbreiten Problem mit der Brücke

[Tor Bug Tracker & Wiki]

#33550: Bandbreiten Problem mit der Brücke
--+
 Reporter:  habus |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * component:  - Select a component => Core Tor/Tor


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33428 [Core Tor/Chutney]: Make chutney check for relay microdescriptors before verifying

[Tor Bug Tracker & Wiki]

#33428: Make chutney check for relay microdescriptors before verifying
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Chutney   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311, outreachy-ipv6  |  Actual Points:
Parent ID:  #33232 | Points:  1
 Reviewer: |Sponsor:  Sponsor55-can
---+---

Comment (by anuradha1904):

 Hey, I am anuradha, an outreachy applicant, would like to work on the
 following issue. Can someone give me context on how to start with the
 following issue? Thank you.

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

Re: [tor-bugs] #33065 [Metrics/Website]: metrics dirbytes graph either underreports or leaves out dir auths?

[Tor Bug Tracker & Wiki]

#33065: metrics dirbytes graph either underreports or leaves out dir auths?
-+-
 Reporter:  arma |  Owner:  karsten
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:  3
Parent ID:   | Points:  3
 Reviewer:  irl  |Sponsor:
-+-
Changes (by karsten):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * actualpoints:  1.5 => 3


Comment:

 This is now merged and deployed. Closing.

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

[tor-bugs] #33553 [Core Tor]: Target and Eliminate http & adjacent algorithms & increase algorithm complexity given set standard.

[Tor Bug Tracker & Wiki]

#33553: Target and Eliminate http & adjacent algorithms & increase algorithm
complexity given set standard.
-+--
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Component:  Core Tor
  Version:   |   Severity:  Major
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
 Core network of nodes limit to https only by default for clear net
 interaction.
 Eliminate "128" algorithms and weak SSL&TLS
 Focus on quantum and PQ encryption of traffic.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33550 [Core Tor/Tor]: Bandbreiten Problem mit der Brücke

[Tor Bug Tracker & Wiki]

#33550: Bandbreiten Problem mit der Brücke
--+
 Reporter:  habus |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by habus):

 My Relay:
 
[https://metrics.torproject.org/rs.html#details/6C5BC67DAE6E6D98FFD7E75558032F28EADFF2FA]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32121 [Core Tor/Tor]: Refactor some common configs and functions out of the git scripts.

[Tor Bug Tracker & Wiki]

#32121: Refactor some common configs and functions out of the git scripts.
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  enhancement  | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  git-scripts, 044-should, |  Actual Points:  .5
  043-backport   |
Parent ID:   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+-

Comment (by nickm):

 (do you agree with merging without that change?)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33544 [Core Tor/Tor]: dir/param_voting_lookup unit-test fails when ALL_BUGS_ARE_FATAL is set

[Tor Bug Tracker & Wiki]

#33544: dir/param_voting_lookup unit-test fails when ALL_BUGS_ARE_FATAL is set
--+
 Reporter:  rl1987|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  backport? |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * keywords:   => backport?
 * milestone:   => Tor: 0.4.4.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33131 [Core Tor/Tor]: Bug: buf->datalen >= 0x7fffffff

[Tor Bug Tracker & Wiki]

#33131: Bug: buf->datalen >= 0x7fff
--+
 Reporter:  cypherpunks   |  Owner:  (none)
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.4.2.5
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * priority:  Low => Medium
 * 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] #33469 [Core Tor/Tor]: INTERNAL ERROR: Raw assertion failed at src/lib/malloc/map_anon.c:239: lock_result == 0

[Tor Bug Tracker & Wiki]

#33469: INTERNAL ERROR: Raw assertion failed at src/lib/malloc/map_anon.c:239:
lock_result == 0
-+-
 Reporter:  m95d |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  0.4.2.6
 Severity:  Normal   | Resolution:
 Keywords:  malloc map_anon windows  |  Actual Points:
  042-backport 043-must  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 I also suspect that this is related to #24857.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33428 [Core Tor/Chutney]: Make chutney check for relay microdescriptors before verifying

[Tor Bug Tracker & Wiki]

#33428: Make chutney check for relay microdescriptors before verifying
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Chutney   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311, outreachy-ipv6  |  Actual Points:
Parent ID:  #33232 | Points:  1
 Reviewer: |Sponsor:  Sponsor55-can
---+---

Comment (by nickm):

 Sure! The context here is that Chutney
 (https://github.com/torproject/chutney) is a program that runs a small Tor
 network on your desktop.  Part of its functionality is to see whether the
 network has successfully bootstrapped or not.  In #33232 (specifically
 #33379), there's work to see whether relays have the information they need
 in order to use the network.  But that work doesn't cover the kind of
 information called a "microdescriptor".  Microdescriptors are more fully
 documented in dir-spec.txt in the tor specifications directory.  As part
 of this ticket, you'd want to extend the work of #33379 to check for
 microdescriptors as well.

 Teor, is there more that anuradha1904 should know here?  Would it make
 sense to share a link to your existing #33379 work-in-progress, so they
 have something to base theirs on?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32905 [Core Tor/Tor]: Remove the ClientAutoIPv6ORPort option

[Tor Bug Tracker & Wiki]

#32905: Remove the ClientAutoIPv6ORPort option
--+
 Reporter:  neel  |  Owner:  neel
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ipv6  |  Actual Points:
Parent ID:  #29641| Points:
 Reviewer:  dgoulet   |Sponsor:
--+
Changes (by neel):

 * status:  needs_revision => needs_review


Comment:

 Should be good 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

[tor-bugs] #33554 [Core Tor/Tor]: Excessive CPU usage in windows tor_cond_t code?

[Tor Bug Tracker & Wiki]

#33554: Excessive CPU usage in windows tor_cond_t code?
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  backport?
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 On #33411, gvanem reports excdessive CPU consumption in the windows
 tor_cond_t code.  We should see if we can fix that.

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

Re: [tor-bugs] #33554 [Core Tor/Tor]: Excessive CPU usage in windows tor_cond_t code?

[Tor Bug Tracker & Wiki]

#33554: Excessive CPU usage in windows tor_cond_t code?
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  backport? |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * cc: gvanem (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] #33411 [Core Tor/Tor]: Make DirCache default to 0 on Windows relays

[Tor Bug Tracker & Wiki]

#33411: Make DirCache default to 0 on Windows relays
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.9
 Severity:  Normal   | Resolution:
 Keywords:  044-should, cpu, windows, linux, |  Actual Points:
  performance, regression, 033-triage-20180326,  |
  033-removed-20180326, 034-deferred-20180602,   |
  035-removed-20180711, 032-unreached-backport,  |
  040-roadmap-proposed, 033-unreached-backport-  |
  maybe, network-health  |
Parent ID:  #24857   | Points:  0.2
 Reviewer:   |Sponsor:
-+-

Comment (by nickm):

 Hmm.  If that helps, then there is probably another bug in the function.
 Are you saying that this function is busy-looping even when there is
 nothing to do?  If you're looking at this in a debugger, can you tell me
 the values for ms, cond->n_to_wake, and cond->generation_at_start, when
 the critical section is entered?

 Hm. Now that WinXP is obsolete, maybe we should move this function to use
 CONDITION_VARIABLE instead...

 (I've opened a ticket #33554 for this CPU issue you're talking about here,
 since this ticket seems to be about changing the dircache default. If you
 can answer there, that would 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

[tor-bugs] #33555 [Core Tor/Tor]: Space out the line.key/line.value in test_policy_summary_helper_family_flags()

[Tor Bug Tracker & Wiki]

#33555: Space out the line.key/line.value in
test_policy_summary_helper_family_flags()
--+--
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  easy
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--


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

Re: [tor-bugs] #33555 [Core Tor/Tor]: Space out the line.key/line.value in test_policy_summary_helper_family_flags()

[Tor Bug Tracker & Wiki]

#33555: Space out the line.key/line.value in
test_policy_summary_helper_family_flags()
--+--
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by neel):

 * cc: neel (added)
 * status:  assigned => needs_review


Comment:

 PR: https://github.com/torproject/tor/pull/1778

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33555 [Core Tor/Tor]: Space out the line.key/line.value in test_policy_summary_helper_family_flags()

[Tor Bug Tracker & Wiki]

#33555: Space out the line.key/line.value in
test_policy_summary_helper_family_flags()
--+
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * milestone:   => Tor: 0.4.4.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33375 [Core Tor/Tor]: Stop advertising an IPv6 exit policy when DNS is broken for IPv6

[Tor Bug Tracker & Wiki]

#33375: Stop advertising an IPv6 exit policy when DNS is broken for IPv6
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.14
 Severity:  Normal   | Resolution:
 Keywords:  security-review-dos-risk, extra- |  Actual Points:
  review, no-backport, ipv6, tor-exit, tor-dns   |
Parent ID:  #24833   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by neel):

 * status:  needs_revision => needs_review


Comment:

 I added unit tests. However, this still only counts DNS errors on timeout.

 Setting as needs review, feel free to put as needs revision if more DNS
 errors are necessary.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33527 [Core Tor/Tor]: Write walking onions specification

[Tor Bug Tracker & Wiki]

#33527: Write walking onions specification
-+-
 Reporter:  gaba |  Owner:  nickm
 Type:  project  | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  walking-onions network-team- |  Actual Points:
  roadmap-2020Q1 |
Parent ID:   | Points:  16
 Reviewer:   |Sponsor:
 |  Sponsor69
-+-
Changes (by nickm):

 * status:  assigned => accepted
 * milestone:   => Tor: 0.4.4.x-final


Comment:

 I'm sending weekly updates about the progress here to tor-dev; I sent the
 first one at https://lists.torproject.org/pipermail/tor-
 dev/2020-March/014178.html

 I'm using a temporary repository at https://github.com/nmathewson/walking-
 onions-wip to keep track of my work 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] #26646 [Core Tor/Tor]: add support for multiple OutboundBindAddressExit IP(ranges)

[Tor Bug Tracker & Wiki]

#26646: add support for multiple OutboundBindAddressExit IP(ranges)
-+-
 Reporter:  nusenu   |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  needs-proposal, tor-exit, ipv6,  |  Actual Points:
  censorship |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by teor):

 Yes, a short proposal would be helpful.

 I'd like to see a sketch of the design:
 * how are the ranges specified in the torrc
 * how does the exit decide when to use a new IP
 * how are the new IPs chosen from the range

 And also a discussion of the risks:
 * clients use the same circuit and exit for the same website, because some
 broken websites expect the same user to have the same IP for different
 connections
   * do clients deliberately use the same exit through different circuits?
 I don't think so, but I'm not sure
 * some circuits can be distinguished, because they come from different IP
 addresses
 * does the new syntax also apply to outbound OR connections?
   * if relays use a different address to their published address for
 directory requests, authorities may refuse those requests
   * relays try to keep canonical connections open with other relays, and
 different addresses make them rotate connections faster

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17011 [Core Tor/Chutney]: chutney doesn't verify using IPv6 addresses

[Tor Bug Tracker & Wiki]

#17011: chutney doesn't verify using IPv6 addresses
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Core Tor/Chutney |Version:
 Severity:  Normal   | Resolution:
 Keywords:  outreachy-ipv6, testing, ipv6, tor-  |  Actual Points:
  tests-integration  |
Parent ID:  #17811   | Points:  3
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * keywords:  SponsorS, testing, ipv6, tor-tests-integration => outreachy-
 ipv6, testing, ipv6, tor-tests-integration
 * sponsor:  SponsorS-can =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #17013 [Core Tor/Chutney]: Does chutney need to test various rare IPv6/IPv4 combinations?

[Tor Bug Tracker & Wiki]

#17013: Does chutney need to test various rare IPv6/IPv4 combinations?
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  testing, tor-tests-integration, ipv6  |  Actual Points:
Parent ID:  #17011| Points:  3
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:  testing, SponsorS, tor-tests-integration, ipv6 => testing,
 tor-tests-integration, ipv6
 * sponsor:  SponsorS-can =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20068 [Core Tor/Chutney]: Chutney tests for IPv6-only bridge clients

[Tor Bug Tracker & Wiki]

#20068: Chutney tests for IPv6-only bridge clients
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  outreachy-ipv6, ipv6  |  Actual Points:
Parent ID:  #17011| Points:  1
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:  ipv6 => outreachy-ipv6, ipv6


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #30182 [Core Tor/Chutney]: IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv6

[Tor Bug Tracker & Wiki]

#30182: IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support 
IPv6
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  outreachy-ipv6, chutney-ci, ipv6  |  Actual Points:
Parent ID:  #26664| Points:  1
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:  chutney-ci, ipv6 => outreachy-ipv6, chutney-ci, ipv6


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #30182 [Core Tor/Chutney]: IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv6

[Tor Bug Tracker & Wiki]

#30182: IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support 
IPv6
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  outreachy-ipv6, chutney-ci, ipv6  |  Actual Points:
Parent ID:  #17011| Points:  1
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * parent:  #26664 => #17011


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31543 [Core Tor/Tor]: Add unit tests or chutney tests for IPv6Traffic

[Tor Bug Tracker & Wiki]

#31543: Add unit tests or chutney tests for IPv6Traffic
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.4.1.5
 Severity:  Normal| Resolution:
 Keywords:  outreachy-ipv6, ipv6  |  Actual Points:
Parent ID:  #17011| Points:
 Reviewer:|Sponsor:
--+--
Changes (by teor):

 * keywords:  ipv6 => outreachy-ipv6, ipv6
 * parent:  #26664 => #17011


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33555 [Core Tor/Tor]: Space out the line.key/line.value in test_policy_summary_helper_family_flags()

[Tor Bug Tracker & Wiki]

#33555: Space out the line.key/line.value in
test_policy_summary_helper_family_flags()
--+
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by neel):

 * status:  needs_review => needs_revision
 * milestone:  Tor: 0.4.4.x-final =>


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33375 [Core Tor/Tor]: Stop advertising an IPv6 exit policy when DNS is broken for IPv6

[Tor Bug Tracker & Wiki]

#33375: Stop advertising an IPv6 exit policy when DNS is broken for IPv6
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.14
 Severity:  Normal   | Resolution:
 Keywords:  security-review-dos-risk, extra- |  Actual Points:
  review, no-backport, ipv6, tor-exit, tor-dns   |
Parent ID:  #24833   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by neel):

 * status:  needs_review => 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] #33555 [Core Tor/Tor]: Space out the line.key/line.value in test_policy_summary_helper_family_flags()

[Tor Bug Tracker & Wiki]

#33555: Space out the line.key/line.value in
test_policy_summary_helper_family_flags()
--+
 Reporter:  neel  |  Owner:  neel
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  easy  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by neel):

 * status:  needs_revision => needs_review
 * milestone:   => Tor: 0.4.4.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #30182 [Core Tor/Chutney]: IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv6

[Tor Bug Tracker & Wiki]

#30182: IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support 
IPv6
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  outreachy-ipv6, chutney-ci, ipv6  |  Actual Points:
Parent ID:  #17011| Points:  1
 Reviewer:|Sponsor:
--+
Description changed by teor:

Old description:

> So maybe we're not actually testing IPv6 traffic?
>
> See also #20067.

New description:

 So maybe we're not actually testing IPv6 traffic?

 Here are the symptoms of this bug:
 * Travis Linux VMs don't have IPv6
 * Travis macOS VMs have IPv6
 * Most IPv6 tests succeed on Travis macOS, but fail on Travis Linux
 * The IPv6 exit test succeeds on Travis Linux, but it should not

--

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

Re: [tor-bugs] #33428 [Core Tor/Chutney]: Make chutney check for relay microdescriptors before verifying

[Tor Bug Tracker & Wiki]

#33428: Make chutney check for relay microdescriptors before verifying
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Chutney   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311, outreachy-ipv6  |  Actual Points:
Parent ID:  #33232 | Points:  1
 Reviewer: |Sponsor:  Sponsor55-can
---+---

Comment (by teor):

 Hi anuradha1904, this ticket is one of the stretch goals for the Tor IPv6
 Outreachy project. You're welcome to start working on it, but we're not
 sure how difficult it will be. Please stay in touch, so we can help you
 out if you get stuck.

 A lot of the work on the IPv6 project is in the `tor` binary, which is
 written in C. Do you know how to program in C ?

 If you don't know how to program in C, that's ok. There is plenty of
 Python work to do in Chutney. I have added some more chutney tasks to the
 Outreachy project description, and the
 [https://trac.torproject.org/projects/tor/query?status=!closed&keywords
 =~outreachy-ipv6 outreachy-ipv6 keyword].

 I'm working on the branch for #33379 right now. Once it passes the tests,
 I'll post a link to the pull request here.


 Nick, is reading a file containing the ed25519 key is a good design for
 this feature?

 For the RSA key, we use `tor --list-fingerprint`. We could add a feature
 to tor so it accepts a key type argument:
 * `tor --list-fingerprint rsa`
 * `tor --list-fingerprint ed25519`

 If we want to read a file, we could just read
 `keys/ed25519_master_id_public_key`, so we don't have to depend on #30642.

 What do you think?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #30642 [Core Tor/Tor]: Add an ed25519-identity file to the data directory (was: Add an ed25519_identity file to the data directory)

[Tor Bug Tracker & Wiki]

#30642: Add an ed25519-identity file to the data directory
+
 Reporter:  teor|  Owner:  neel
 Type:  enhancement | Status:  needs_revision
 Priority:  Medium  |  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tor-relay easy 043-can  |  Actual Points:
Parent ID:  | Points:  1
 Reviewer:  dgoulet |Sponsor:
+

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

Re: [tor-bugs] #33375 [Core Tor/Tor]: Stop advertising an IPv6 exit policy when DNS is broken for IPv6

[Tor Bug Tracker & Wiki]

#33375: Stop advertising an IPv6 exit policy when DNS is broken for IPv6
-+-
 Reporter:  teor |  Owner:  neel
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.14
 Severity:  Normal   | Resolution:
 Keywords:  security-review-dos-risk, extra- |  Actual Points:
  review, no-backport, ipv6, tor-exit, tor-dns   |
Parent ID:  #24833   | Points:
 Reviewer:  teor |Sponsor:
-+-

Comment (by neel):

 There is one problem with unit tests: The code this adds relies on code
 that calls the relay module, and some compilations don't include this, so
 that's why the tests fail.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33556 [Applications/Tor Browser]: Add TBB project for android-components

[Tor Bug Tracker & Wiki]

#33556: Add TBB project for android-components
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 Contains dependent libraries of Fenix

 Source: !https://github.com/mozilla-mobile/android-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

[tor-bugs] #33557 [Applications/Tor Browser]: Update Android Toolchain for Fenix

[Tor Bug Tracker & Wiki]

#33557: Update Android Toolchain for Fenix
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 Fenix uses an updated Android SDK and NDK.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33184 [Applications/Tor Browser]: Support for Fenix

[Tor Bug Tracker & Wiki]

#33184: Support for Fenix
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sisbell):

 * cc: bolklm (removed)
 * cc: boklm (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] #33375 [Core Tor/Tor]: Stop advertising an IPv6 exit policy when DNS is broken for IPv6

[Tor Bug Tracker & Wiki]

#33375: Stop advertising an IPv6 exit policy when DNS is broken for IPv6
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.14
 Severity:  Normal   | Resolution:
 Keywords:  security-review-dos-risk, extra- |  Actual Points:
  review, no-backport, ipv6, tor-exit, tor-dns   |
Parent ID:  #24833   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by neel):

 * owner:  neel => (none)
 * status:  needs_revision => 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] #33375 [Core Tor/Tor]: Stop advertising an IPv6 exit policy when DNS is broken for IPv6

[Tor Bug Tracker & Wiki]

#33375: Stop advertising an IPv6 exit policy when DNS is broken for IPv6
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.4.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.9.14
 Severity:  Normal   | Resolution:
 Keywords:  security-review-dos-risk, extra- |  Actual Points:
  review, no-backport, ipv6, tor-exit, tor-dns   |
Parent ID:  #24833   | Points:
 Reviewer:  teor |Sponsor:
-+-
Changes (by neel):

 * status:  assigned => 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

[tor-bugs] #33558 [Applications/Tor Browser]: Update TOPL To Use Updated Android Toolchain

[Tor Bug Tracker & Wiki]

#33558: Update TOPL To Use Updated Android Toolchain
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 We need to upgrade android toolchain to support fenix. This requires
 update to TOPL build as well.

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

[tor-bugs] #33559 [Applications/Tor Browser]: Update tor-android-service To Use Updated Android Toolchain

[Tor Bug Tracker & Wiki]

#33559: Update tor-android-service To Use Updated Android Toolchain
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 We need to upgrade android toolchain to support fenix. This requires
 update to tor-android-service.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #30954 [Core Tor/Tor]: Address torrc option is ignored if set second time for the IPv6 address

[Tor Bug Tracker & Wiki]

#30954: Address torrc option is ignored if set second time for the IPv6 address
--+--
 Reporter:  s7r   |  Owner:  neel
 Type:  enhancement   | Status:  assigned
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  ipv6  |  Actual Points:
Parent ID:  #5940 | Points:
 Reviewer:|Sponsor:
--+--
Changes (by neel):

 * status:  new => assigned
 * cc: neel (added)
 * owner:  (none) => neel


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33560 [- Select a component]: Settings immediately after install

[Tor Bug Tracker & Wiki]

#33560: Settings immediately after install
---+--
 Reporter:  KatBloodgood   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Component:  - Select a component
  Version:  Tor: unspecified   |   Severity:  Normal
 Keywords:  client-transport?  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 3/9/20, 04:33:18.780 [NOTICE] Bootstrapped 10% (conn_done): Connected to a
 relay
 3/9/20, 04:33:19.122 [NOTICE] Bootstrapped 14% (handshake): Handshaking
 with a relay
 3/9/20, 04:33:19.336 [NOTICE] Bootstrapped 15% (handshake_done): Handshake
 with a relay done
 3/9/20, 04:33:19.337 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded
 enough directory info to build circuits
 3/9/20, 04:33:19.338 [NOTICE] Bootstrapped 90% (ap_handshake_done):
 Handshake finished with a relay to build circuits
 3/9/20, 04:33:19.340 [NOTICE] Bootstrapped 95% (circuit_create):
 Establishing a Tor circuit
 3/9/20, 04:33:20.168 [NOTICE] Bootstrapped 100% (done): Done
 3/9/20, 04:33:21.105 [NOTICE] New control connection opened from
 127.0.0.1.
 3/9/20, 04:33:21.354 [NOTICE] New control connection opened from
 127.0.0.1.
 3/9/20, 04:34:59.416 [WARN] CreateProcessA() failed: The system cannot
 find the file specified.
 3/9/20, 04:34:59.416 [WARN] Pluggable Transport process terminated with
 status code 0
 3/9/20, 04:34:59.417 [WARN] Failed to start process: (null)
 3/9/20, 04:34:59.417 [WARN] Managed proxy at
 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
 3/9/20, 04:34:59.417 [NOTICE] Switching to guard context "bridges" (was
 using "default")
 3/9/20, 04:34:59.504 [NOTICE] Delaying directory fetches: No running
 bridges
 3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:00.507 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:00.508 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:00.509 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:01.511 [WARN] We were supposed to connect to bridge
 '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a
 pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:01.511 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:02.523 [WARN] We were supposed to connect to bridge
 '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find
 a pluggable transport proxy supporting 'obfs4'. This can happen if you
 haven't provided a ClientTransportPlugin line, or if your pluggable
 transport proxy stopped running.
 3/9/20, 04:35:02.523 [WARN] We were supposed to connect to bridge
 '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't
 find a pluggable transport proxy supporting 'obfs4'. This can happen if
 you haven't provi

Re: [tor-bugs] #33560 [- Select a component]: Settings immediately after install

[Tor Bug Tracker & Wiki]

#33560: Settings immediately after install
--+--
 Reporter:  KatBloodgood  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:  client-transport? |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by KatBloodgood):

 * Attachment "3.docx" added.

 Log (I am not a computer dev/prog.etc)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33557 [Applications/Tor Browser]: Update Android Toolchain for Fenix

[Tor Bug Tracker & Wiki]

#33557: Update Android Toolchain for Fenix
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sisbell):

 Require support for

  * API: Platform 29
  * NDK 21
  * Gradle 5.6.4
  * Build Tools and Platform Tools: 28.0.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] #33184 [Applications/Tor Browser]: Support for Fenix

[Tor Bug Tracker & Wiki]

#33184: Support for Fenix
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sisbell):

 Replying to [comment:2 sisbell]:


 > So this first issue we have to resolve is this one
 >
 > https://github.com/mozilla-mobile/fenix/issues/6932
 >
 > Fenix doesn't build out-of-the-box on a clean clone of the repo.
 >
 This caused by not having ANDROID_SDK_HOME and ANDROID_NDK_HOME properties
 set. Since this is handled by the android-toolchain setup, its not a
 problem for the tbb build.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33561 [Applications/Tor Browser]: Upgrade openssl to use Android NDK 21

[Tor Bug Tracker & Wiki]

#33561: Upgrade openssl to use Android NDK 21
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 This is based of the current work done in branch for android support. We
 need to upgrade to build with NDK 21.

 Make standalone toolchain is not longer supported in NDK 21 so need to
 configure to use new locations.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33562 [Applications/Tor Browser]: Upgrade libevent to use NDK 21

[Tor Bug Tracker & Wiki]

#33562: Upgrade libevent to use NDK 21
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 This is based of the current work done in branch for android support. We
 need to upgrade to build with NDK 21.

 Make standalone toolchain is not longer supported in NDK 21 so need to
 configure to use new locations.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33563 [Applications/Tor Browser]: Upgrade Tor To Use Android NDK 21

[Tor Bug Tracker & Wiki]

#33563: Upgrade Tor To Use Android NDK 21
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 This is based of the current work done in branch for android support. We
 need to upgrade to build with NDK 21.

 Make standalone toolchain is not longer supported in NDK 21 so need to
 configure to use new locations

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33564 [Applications/Tor Browser]: Upgrade ZSTD to use Android NDK 21

[Tor Bug Tracker & Wiki]

#33564: Upgrade ZSTD to use Android NDK 21
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 This is based of the current work done in branch for android support. We
 need to upgrade to build with NDK 21.

 Make standalone toolchain is not longer supported in NDK 21 so need to
 configure to use new locations

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33565 [Applications/Tor Browser]: Upgrade LZMA to use Android NDK 21

[Tor Bug Tracker & Wiki]

#33565: Upgrade LZMA to use Android NDK 21
--+
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-mobile,
  |  Android
Actual Points:|  Parent ID:  #33184
   Points:|   Reviewer:
  Sponsor:|
--+
 This is based of the current work done in branch for android support. We
 need to upgrade to build with NDK 21.

 Make standalone toolchain is not longer supported in NDK 21 so need to
 configure to use new locations

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33557 [Applications/Tor Browser]: Update Android Toolchain for Fenix

[Tor Bug Tracker & Wiki]

#33557: Update Android Toolchain for Fenix
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sisbell):

 I've updated to handle toolchain used by fenix (and android-components).
 The standalone toolchain script is no longer supported. The following link
 covers the changes we need to make. On the plus side, the tar file will be
 smaller.

 https://developer.android.com/ndk/guides/other_build_systems

 In the config, I made more param versions configurable, as I expect we
 will need to upgrade frequently as fenix is in rapid development. I also
 added gradle to the path which means we don't need to specify full-path in
 projects.

 The Commit:

 https://github.com/sisbell/tor-browser-build/commits/bug-33557

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33557 [Applications/Tor Browser]: Update Android Toolchain for Fenix

[Tor Bug Tracker & Wiki]

#33557: Update Android Toolchain for Fenix
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sisbell):

 * 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

[tor-bugs] #33566 [Applications/Tor Browser]: 'No video with supported format and MIME type found.'

[Tor Bug Tracker & Wiki]

#33566: 'No video with supported format and MIME type found.'
---+--
 Reporter:  torpersia  |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Medium |  Component:  Applications/Tor Browser
  Version: |   Severity:  Normal
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 Hi i use torbrowser android 9.0.5
 I get a warning when I watch a video
 'No video with supported format and MIME type found.'
 My android: 9
 Plz fix this 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

[tor-bugs] #33567 [Applications/Tor Browser]: 'No video with supported format and MIME type found.'

[Tor Bug Tracker & Wiki]

#33567: 'No video with supported format and MIME type found.'
---+--
 Reporter:  torpersia  |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Very High  |  Component:  Applications/Tor Browser
  Version: |   Severity:  Normal
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 Hi i use torbrowser android 9.0.5
 I get a warning when I watch a video
 'No video with supported format and MIME type found.'
 My android: 9
 Plz fix this bug
 i test pornhub video

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33428 [Core Tor/Chutney]: Make chutney check for relay microdescriptors before verifying

[Tor Bug Tracker & Wiki]

#33428: Make chutney check for relay microdescriptors before verifying
---+---
 Reporter:  teor   |  Owner:  (none)
 Type:  enhancement| Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Chutney   |Version:
 Severity:  Normal | Resolution:
 Keywords:  ipv6, prop311, outreachy-ipv6  |  Actual Points:
Parent ID:  #33232 | Points:  1
 Reviewer: |Sponsor:  Sponsor55-can
---+---

Comment (by teor):

 Here is my work-in-progress branch for #33379. It still has some bugs. It
 works for about half the chutney networks in tor's `make test-network-
 all`:
 * do not merge: https://github.com/torproject/chutney/pull/57

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33556 [Applications/Tor Browser]: Add TBB project for android-components

[Tor Bug Tracker & Wiki]

#33556: Add TBB project for android-components
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sisbell):

 This one is not complete so its more of a preview. This works with network
 turned on. Its a work in progress for network turned off.

 Some problems I detected, mostly around changes to local repos

  * Setting of the local maven repo is not working with gradle 5.6.x:
 -Dmaven.repo.local=$gradle_repo
  * There are a couple of dozen downloads that the build tries to download
 but they are all 404 (from same repo). This doesn't appear to affect the
 build.
  * Customs Gradle Plugins need a different repo location than the rest of
 the build. I've managed to get one of the plugins poiting to the correct
 local repo but having trouble with the second one.

 On the plus side, the parsing of the logs for dependencies works without
 needing any changes.

 So the way this works is that we build all the components into an aar and
 the invoke the gradle task ''publishToMavenLocal''

 This will publish to a local repo that the build then packages up to be
 used by fenix.

 https://github.com/sisbell/tor-browser-build/commits/bug-33556

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33556 [Applications/Tor Browser]: Add TBB project for android-components

[Tor Bug Tracker & Wiki]

#33556: Add TBB project for android-components
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:  #33184| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sisbell):

 android-components build pulls the git hash and adds it as meta-data to
 the aar. The git.patch removes this feature. This is necessary since the
 build doesn't have the git meta-data included. Without the patch the build
 fails.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #33184 [Applications/Tor Browser]: Support for Fenix

[Tor Bug Tracker & Wiki]

#33184: Support for Fenix
--+--
 Reporter:  sisbell   |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile, Android   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sisbell):

 This is preview. It has similar problems as #33556 with working with
 network disabled. You can see in the gradle-dependencies-list there are a
 bunch of snapshots for the android-components. These snapshot hashes will
 change without warning so those will be replaced with the ones that will
 be packaged locally from the tbb android-components build.

 !https://github.com/sisbell/tor-browser-build/commits/bug-33184

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