Re: [tor-bugs] #31992 [Applications/Tor Browser]: Remove apktool workaround in #31564

[Tor Bug Tracker & Wiki]

#31992: Remove apktool workaround in #31564
---+--
 Reporter:  gk |  Owner:  sisbell
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201911  |  Actual Points:
Parent ID: | Points:  0.25
 Reviewer: |Sponsor:
---+--

Comment (by sisbell):

 As outlined in the original issue, the following resource(s) cause aapt to
 fail

 {{{
 W: res/drawable-v21/$avd_hide_password__0.xml: Invalid file name: must
 contain only [a-z0-9_.]
 W: res/drawable-v21/$avd_hide_password__1.xml: Invalid file name: must
 contain only [a-z0-9_.]
 W: res/drawable-v21/$avd_hide_password__2.xml: Invalid file name: must
 contain only [a-z0-9_.]
 W: res/drawable-v21/$avd_show_password__0.xml: Invalid file name: must
 contain only [a-z0-9_.]
 W: res/drawable-v21/$avd_show_password__1.xml: Invalid file name: must
 contain only [a-z0-9_.]
 W: res/drawable-v21/$avd_show_password__2.xml: Invalid file name: must
 contain only [a-z0-9_.]
 }}}


 So after running the debugger, I could see everything was fine until the
 process execution of aapt. After digging through source code in various
 repos, I found the following commit for the custom aapt that iBotPeaches
 is including in the apktool. This patch ignores illegal characters in
 resource file names.

 
https://github.com/iBotPeaches/platform_frameworks_base/commit/672206c5229c259e174b0a8d6d2bfdeeb753149c

 So there is no way the aapt packaged in Debian (regardless of version) is
 going to work without this patch. This is not a bug in the Debian version
 as aapt should reject resources.

 Unless we are planning on removing apktool completely and trying another
 approach, we can close this issue.

 
 For reference these resources are coming from a google support library

 
https://developer.android.com/reference/android/support/design/R.drawable.html#avd_show_password

 https://android.googlesource.com/platform/frameworks/support/+/support-
 library-27.0.2/design/res/drawable-v21/

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32552 [Core Tor/Nyx]: stem says "dictionary keys changed during iteration" with new python (was: can't connect to for, whether using cookie or password)

[Tor Bug Tracker & Wiki]

#32552: stem says "dictionary keys changed during iteration" with new python
--+--
 Reporter:  cypherpunks   |  Owner:  atagar
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:  Tor: 0.4.1.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by arma):

 I closed #32566 and #32596 as a duplicate.

 And giving this ticket a better title.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32596 [Core Tor/Nyx]: Python 3.8.0 RuntimeError: dictionary keys changed during iteration

[Tor Bug Tracker & Wiki]

#32596: Python 3.8.0 RuntimeError: dictionary keys changed during iteration
--+---
 Reporter:  iiwwnnaa  |  Owner:  atagar
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Nyx  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by arma):

 * status:  new => closed
 * owner:  (none) => atagar
 * component:  - Select a component => Core Tor/Nyx
 * resolution:   => duplicate


Comment:

 Yep, this is a bug with using the old stem with the new python.

 See #32552 for the fix.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32596 [- Select a component]: Python 3.8.0 RuntimeError: dictionary keys changed during iteration

[Tor Bug Tracker & Wiki]

#32596: Python 3.8.0 RuntimeError: dictionary keys changed during iteration
--+
 Reporter:  iiwwnnaa  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by iiwwnnaa):

 OH I missed version
 tor --version
 Tor version 0.4.1.6.
 python --version
 Python 3.8.0

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32596 [- Select a component]: Python 3.8.0 RuntimeError: dictionary keys changed during iteration

[Tor Bug Tracker & Wiki]

#32596: Python 3.8.0 RuntimeError: dictionary keys changed during iteration
--+--
 Reporter:  iiwwnnaa  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Component:  - Select a component
  Version:|   Severity:  Normal
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 I was using python 3.7.4 and update python to 3.8.0
 and try to use tor, this error is showed (when 3.7.4 working good)

 File "/usr/lib/python3.8/site-packages/stem/control.py", line 1100, in
 authenticate
 stem.connection.authenticate(self, *args, **kwargs)
 File "/usr/lib/python3.8/site-packages/stem/connection.py", line 592, in
 authenticate
 controller._post_authentication()
 File "/usr/lib/python3.8/site-packages/stem/control.py", line 3902, in
 _post_authentication
 owning_pid = self.get_conf('__OwningControllerProcess', None)
 File "/usr/lib/python3.8/site-packages/stem/control.py", line 2170, in
 get_conf
 entries = self.get_conf_map(param, default, multiple)
 File "/usr/lib/python3.8/site-packages/stem/control.py", line 2273, in
 get_conf_map
 for key in reply:
 RuntimeError: dictionary keys changed during iteration

 Smialar issues other github project
 https://github.com/vispy/vispy/issues/1729

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32453 [Applications/Tor Browser]: connection no longer available

[Tor Bug Tracker & Wiki]

#32453: connection no longer available
--+---
 Reporter:  aldo341   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by cypherpunks):

 Windows 8 is long dead.
 https://redmondmag.com/articles/2016/01/13/windows-8-loss-of-support.aspx

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32595 [HTTPS Everywhere/EFF-HTTPS Everywhere]: errors when opening options

[Tor Bug Tracker & Wiki]

#32595: errors when opening options
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:  new
 Priority:  Medium   |  Component:  HTTPS Everywhere/EFF-HTTPS
 |  Everywhere
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
 errors:
 {{{
 Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
 TypeError: chromeWin.gBrowserInit is undefined ext-webNavigation.js:140:1
 }}}

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

Re: [tor-bugs] #31992 [Applications/Tor Browser]: Remove apktool workaround in #31564

[Tor Bug Tracker & Wiki]

#31992: Remove apktool workaround in #31564
---+--
 Reporter:  gk |  Owner:  sisbell
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201911  |  Actual Points:
Parent ID: | Points:  0.25
 Reviewer: |Sponsor:
---+--

Comment (by sisbell):

 I tried the buster version (2.3.4-dirty) and then a custom deb install
 (2.4.0-dirty) and neither one works. At this point I think the report that
 this is an aapt issue (and not an apktool issue) is probably accurate.

 The downloaded version of apktool which we are currently using has a
 packaged version of its own build of aapt. This one works

 {{{
 Android Asset Packaging Tool, v0.2-eng.ibotpe.20190216.092407
 }}}

 While buster uses the following which doesn't work
 {{{
 Android Asset Packaging Tool, v0.2-27.0.1
 }}}

 It difficult to know what the difference is due to the custom build. Both
 look to be some variation of 0.2 versions

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32575 [Core Tor/Tor]: CID 1455953: Resource leak in options_act_reversible()

[Tor Bug Tracker & Wiki]

#32575: CID 1455953:  Resource leak in options_act_reversible()
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:  fixed
 Keywords:  coverity  |  Actual Points:  .1
Parent ID:| Points:  .1
 Reviewer:  teor  |Sponsor:  Sponsor31-can
--+
Changes (by teor):

 * status:  needs_review => closed
 * version:   => Tor: unspecified
 * resolution:   => fixed


Comment:

 Looks good to me.
 Merged to master.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32108 [Core Tor/Tor]: tor can overrun its accountingmax if it enters soft hibernation first

[Tor Bug Tracker & Wiki]

#32108: tor can overrun its accountingmax if it enters soft hibernation first
-+-
 Reporter:  arma |  Owner:  arma
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.4.0.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  extra-review consider-backport-  |  Actual Points:
  after-0424 network-health 042-backport |
  041-backport 040-backport BugSmashFund |
Parent ID:   | Points:
 Reviewer:  dgoulet, teor|Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.4.0.x-final


Comment:

 Merged to 0.4.0 and later.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31091 [Core Tor/Tor]: Bug stracktrace when pluggable transport cannot bind to port

[Tor Bug Tracker & Wiki]

#31091: Bug stracktrace when pluggable transport cannot bind to port
-+-
 Reporter:  s7r  |  Owner:  ahf
 Type:  defect   | Status:  closed
 Priority:  Very High|  Milestone:  Tor:
 |  0.4.0.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:  fixed
 Keywords:  042-must, consider-backport- |  Actual Points:
  after-0424, 040-backport, 041-backport |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * keywords:  042-must, consider-backport-after-0424 => 042-must, consider-
 backport-after-0424, 040-backport, 041-backport
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.4.0.x-final


Comment:

 Merged to 0.4.0 and later.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32058 [Core Tor/Tor]: mainloop: make periodic events restartable

[Tor Bug Tracker & Wiki]

#32058: mainloop: make periodic events restartable
-+-
 Reporter:  teor |  Owner:  dgoulet
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.4.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  consider-backport-after-0424,|  Actual Points:  0.1
  042-should, regression?, 035-backport, |
  040-backport, 041-backport, 042-backport,  |
  BugSmashFund   |
Parent ID:   | Points:  0.5
 Reviewer:  nickm|Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.3.5.x-final


Comment:

 Merged to 0.3.5 and later.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28970 [Core Tor/Tor]: tor_bug_occurred_(): Bug: ../src/or/hs_client.c:624: setup_intro_circ_auth_key: Non-fatal assertion

[Tor Bug Tracker & Wiki]

#28970: tor_bug_occurred_(): Bug: ../src/or/hs_client.c:624:
setup_intro_circ_auth_key: Non-fatal assertion
-+-
 Reporter:  torcrash |  Owner:  dgoulet
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.4.9
 Severity:  Critical | Resolution:  fixed
 Keywords:  consider-backport-after-0424,|  Actual Points:  0.1
  042-backport, 041-backport, 040-backport,  |
  035-backport, tor-client, tor-hs, postfreeze-  |
  ok, 040-unreached-must, network-team-roadmap-  |
  august, regression?, 041-unreached-must,   |
  042-should |
Parent ID:  #29995   | Points:  5
 Reviewer:  teor |Sponsor:
 |  Sponsor27-must
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.3.5.x-final


Comment:

 Merged to 0.3.5 and later.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #30344 [Core Tor/Tor]: conn_read_callback is called on connections that are marked for closed

[Tor Bug Tracker & Wiki]

#30344: conn_read_callback is called on connections that are marked for closed
-+-
 Reporter:  robgjansen   |  Owner:  asn
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.5.8
 Severity:  Normal   | Resolution:  fixed
 Keywords:  consider-backport-after-0424, tor-   |  Actual Points:
  conn, 035-backport, 041-deferred-20190530, |
  042-should, nickm-merge, BugSmashFund  |
Parent ID:   | Points:
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.3.5.x-final


Comment:

 Merged to 0.3.5 and later.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31939 [Core Tor/Tor]: log spam: Bug: buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion !(buf->datalen >= INT_MAX - at_most) failed.

[Tor Bug Tracker & Wiki]

#31939: log spam: Bug: buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion
!(buf->datalen >= INT_MAX - at_most) failed.
-+-
 Reporter:  catalyst |  Owner:  teor
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.4-rc
 Severity:  Normal   | Resolution:  fixed
 Keywords:  consider-backport-after-0424,|  Actual Points:  0.1
  assert, fast-fix, 042-should, 035-backport,|
  040-backport, 041-backport, BugSmashFund   |
Parent ID:  #32022   | Points:  0.1
 Reviewer:  catalyst |Sponsor:
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.3.5.x-final


Comment:

 Merged to 0.3.5 and later.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31548 [Core Tor/Tor]: hs-v3: Service can pick more than HiddenServiceNumIntroductionPoints intro points

[Tor Bug Tracker & Wiki]

#31548: hs-v3: Service can pick more than HiddenServiceNumIntroductionPoints 
intro
points
-+-
 Reporter:  dgoulet  |  Owner:  dgoulet
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  consider-backport-after-0424, tor-   |  Actual Points:  0.2
  hs, service, hs-v3, 035-backport,  |
  040-backport, 041-backport, 042-should |
Parent ID:  #29995   | Points:  0.2
 Reviewer:  asn  |Sponsor:
 |  Sponsor27-must
-+-
Changes (by teor):

 * status:  merge_ready => closed
 * resolution:   => fixed
 * milestone:  Tor: 0.4.1.x-final => Tor: 0.3.5.x-final


Comment:

 Merged to 0.3.5 and later.

 Merged #32575, #31939, #31548, #30344, #30258, #28970, #31091, and #32108
 together.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32476 [Applications/Tor Browser]: Support Launching TorService Using JNI

[Tor Bug Tracker & Wiki]

#32476: Support Launching TorService Using JNI
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, tbb-mobile, |  Actual Points:
  TorBrowserTeam201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 I realize its early development. Some review comments.

 1) I still see that we need to wait for the control port creation file.
 This is what was causing some earlier problems. Will this be fixed with
 the JNI code in the future or does the problem lie in the tor code itself?

 2) Authentication appears to just be default, with no cookies. If we add
 cookie base auth, I think we would also need to wait for that file
 creation as well.

 I bring up (1) and (2) specifically since these were pain points in the
 past and don't seem to be mitigated in the current code.

 3) The JNI code will lock down the implementation class as TorService,
 which is also the Android service class. I think it would be better to
 move the JNI interaction to a different class, which is then called by
 TorService class. This will make it more reusable by third-parties.

 4) We are using file descriptor for the control port with the JNI version.
 This is good. (It does mean this only support *nix based systems).

 I agree we should move forward with JNI integration since we shouldn't be
 spawning processes on Android. However, outside of this general principle,
 I don't see any additional JNI advantages at this point.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32476 [Applications/Tor Browser]: Support Launching TorService Using JNI

[Tor Bug Tracker & Wiki]

#32476: Support Launching TorService Using JNI
-+-
 Reporter:  sisbell  |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  Android, tbb-mobile, |  Actual Points:
  TorBrowserTeam201911   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sisbell):

 The version of ​https://gitlab.com/eighthave/tor-android is not
 referencing the version of tor that contains the JNI classes so app fails
 at runtime. I did find the correct JNI code in the following commit that I
 used for review.

 
https://gitlab.com/eighthave/tor/commit/a453e9faf3e4be946506111754b18f9fcf1ac595

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32559 [Core Tor/Tor]: Travis: run chutney with clang for better diagnostics

[Tor Bug Tracker & Wiki]

#32559: Travis: run chutney with clang for better diagnostics
---+---
 Reporter:  teor   |  Owner:  teor
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:  Tor:
   |  0.4.3.x-final
Component:  Core Tor/Tor   |Version:
 Severity:  Normal | Resolution:  wontfix
 Keywords:  network-team-roadmap-november  |  Actual Points:
Parent ID: | Points:  0.1
 Reviewer: |Sponsor:  Sponsor31-can
---+---
Changes (by teor):

 * keywords:
 network-team-roadmap-november, consider-backport-immediately,
 029-backport, 035-backport, 040-backport, 041-backport, 042-backport
 => network-team-roadmap-november


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20218 [Core Tor/Tor]: Fix and refactor and redocument routerstatus_has_changed

[Tor Bug Tracker & Wiki]

#20218: Fix and refactor and redocument routerstatus_has_changed
-+-
 Reporter:  nickm|  Owner:  (none)
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ipv6, 029-proposed, tor-control, |  Actual Points:  0.5
  easy, spec-conformance, review-group-31,   |
  034-triage-20180328, 034-removed-20180328  |
Parent ID:   | Points:  .1
 Reviewer:  nickm, teor  |Sponsor:
-+-
Changes (by teor):

 * status:  needs_review => needs_revision
 * reviewer:  nickm => nickm, teor


Comment:

 Just a few changes needed to the fields, comments, and changes file.

 I also think we need unit tests for:
 * `routerstatus_has_changed()`, and
 * `routerstatus_format_entry(..., NS_CONTROL_PORT, ...)`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32574 [Internal Services/Service - github tpo]: set up mirror repo on GitHub torproject/jtorctl

[Tor Bug Tracker & Wiki]

#32574: set up mirror repo on GitHub torproject/jtorctl
-+-
 Reporter:  eighthave|  Owner:  hiro
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Service - github   |Version:
  tpo|
 Severity:  Normal   | Resolution:
 Keywords:  Android, tbb-mobile, jtorctl,|  Actual Points:
  TorBrowserTeam202001   |
Parent ID:  #32534   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * owner:  tbb-team => hiro
 * component:  Applications/Tor Browser => Internal Services/Service -
 github tpo
 * type:  defect => task


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32575 [Core Tor/Tor]: CID 1455953: Resource leak in options_act_reversible()

[Tor Bug Tracker & Wiki]

#32575: CID 1455953:  Resource leak in options_act_reversible()
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.4.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  coverity  |  Actual Points:  .1
Parent ID:| Points:  .1
 Reviewer:  teor  |Sponsor:  Sponsor31-can
--+

Comment (by nickm):

 Closed #32594 as a duplicate of this.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32594 [Core Tor/Tor]: Fix CID 1455953: Resource leaks in #32427

[Tor Bug Tracker & Wiki]

#32594: Fix CID 1455953:  Resource leaks in #32427
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  unspecified
 Severity:  Normal   | Resolution:
 Keywords:  043-must, network-team-roadmap-  |  duplicate
  november   |  Actual Points:
Parent ID:  #32408   | Points:  0.1
 Reviewer:   |Sponsor:
 |  Sponsor31-must
-+-
Changes (by nickm):

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


Comment:

 Unless I'm confused, this is a duplicate of #32575.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #7164 [Core Tor/Tor]: microdesc.c:378: Bug: microdesc_free() called, but md was still referenced 1 node(s); held_by_nodes == 1

[Tor Bug Tracker & Wiki]

#7164: microdesc.c:378: Bug: microdesc_free() called, but md was still 
referenced
1 node(s); held_by_nodes == 1
-+-
 Reporter:  jaj123   |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.4.19
 Severity:  Normal   | Resolution:
 Keywords:  tor-client, 025-backport, nickm- |  Actual Points:
  should-review, review-group-24,|
  033-triage-20180320, 033-removed-20180320, |
  BugSmashFund   |
Parent ID:   | Points:  2
 Reviewer:  asn  |Sponsor:
-+-

Comment (by arma):

 On moria1:
 {{{
 Oct 04 09:20:34.684 [warn] microdesc_cache_clean(): Bug: Microdescriptor
 seemed very old (last listed 168 hours ago vs 168 hour cutoff), but is
 still marked as being held by 1 node(s). I found 1 node(s) holding it.
 Current networkstatus is 0 hours old. Hashtable badness is 0. (on Tor
 0.4.2.1-alpha-dev 69a1f9c8a7a9c822)
 Oct 04 09:20:34.685 [warn] microdesc_cache_clean(): Bug:   [0]:
 ID=F5F76C12B07AC124B3B02E03AC526D6F1B20EB77. md=0x55a95055ced0,
 rs=0x55a994a42af0, ri=(nil). Microdesc digest in RS matches. RS okay in
 networkstatus. (on Tor 0.4.2.1-alpha-dev 69a1f9c8a7a9c822)
 }}}

 {{{
 Oct 10 02:16:56.676 [warn] microdesc_cache_clean(): Bug: Microdescriptor
 seemed very old (last listed 168 hours ago vs 168 hour cutoff), but is
 still marked as being held by 1 node(s). I found 1 node(s) holding it.
 Current networkstatus is 0 hours old. Hashtable badness is 0. (on Tor
 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 02:16:56.676 [warn] microdesc_cache_clean(): Bug:   [0]:
 ID=5E6D82B5F73EE48D5755949EE42C755D9BA7C5CC. md=0x55bcfd5ed2d0,
 rs=0x55bd13955b40, ri=0x55bd08462740. Microdesc digest in RS matches. RS
 okay in networkstatus. (on Tor 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 }}}

 {{{
 Oct 10 15:16:56.901 [warn] microdesc_cache_clean(): Bug: Microdescriptor
 seemed very old (last listed 168 hours ago vs 168 hour cutoff), but is
 still marked as being held by 1 node(s). I found 1 node(s) holding it.
 Current networkstatus is 0 hours old. Hashtable badness is 0. (on Tor
 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 15:16:56.901 [warn] microdesc_cache_clean(): Bug:   [0]:
 ID=FCB454EAB56713C641C7A8F2E45B85E7921B9760. md=0x55bcfbe67330,
 rs=0x55bd177f72a0, ri=(nil). Microdesc digest in RS matches. RS okay in
 networkstatus. (on Tor 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 15:16:56.902 [warn] microdesc_cache_clean(): Bug: Microdescriptor
 seemed very old (last listed 168 hours ago vs 168 hour cutoff), but is
 still marked as being held by 1 node(s). I found 1 node(s) holding it.
 Current networkstatus is 0 hours old. Hashtable badness is 0. (on Tor
 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 15:16:56.902 [warn] microdesc_cache_clean(): Bug:   [0]:
 ID=CA3733C8774CCF863A47153B2DC9D70C1550C847. md=0x55bcfd72ba70,
 rs=0x55bd047e9bb0, ri=(nil). Microdesc digest in RS matches. RS okay in
 networkstatus. (on Tor 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 15:16:56.903 [warn] microdesc_cache_clean(): Bug: Microdescriptor
 seemed very old (last listed 168 hours ago vs 168 hour cutoff), but is
 still marked as being held by 1 node(s). I found 1 node(s) holding it.
 Current networkstatus is 0 hours old. Hashtable badness is 0. (on Tor
 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 15:16:56.903 [warn] microdesc_cache_clean(): Bug:   [0]:
 ID=9A0D54D3A6D2E0767596BF1515E6162A75B3293F. md=0x55bcfbcfd410,
 rs=0x55bd0dbf8ac0, ri=(nil). Microdesc digest in RS matches. RS okay in
 networkstatus. (on Tor 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 15:16:56.904 [warn] microdesc_cache_clean(): Bug: Microdescriptor
 seemed very old (last listed 168 hours ago vs 168 hour cutoff), but is
 still marked as being held by 1 node(s). I found 1 node(s) holding it.
 Current networkstatus is 0 hours old. Hashtable badness is 0. (on Tor
 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 Oct 10 15:16:56.904 [warn] microdesc_cache_clean(): Bug:   [0]:
 ID=8CB3BBC8CEEA91734CF2A275FA52FC55ECBC8A5B. md=0x55bcfd80e120,
 rs=0x55bd18e00f00, ri=(nil). Microdesc digest in RS matches. RS okay in
 networkstatus. (on Tor 0.4.2.2-alpha-dev 0d82a8be77ae8d7f)
 }}}

 {{{
 Oct 11 13:16:57.285 [warn] microdesc_cache_clean(): Bug: Microdescriptor
 seemed very old (last listed 168 hours ago vs 168 hour cutoff), but is
 still marked as being held by 1 node(s). I found 1 node(s) holding 

Re: [tor-bugs] #32036 [Core Tor/Tor]: output debug logs to logcat as early as possible on Android

[Tor Bug Tracker & Wiki]

#32036: output debug logs to logcat as early as possible on Android
-+-
 Reporter:  eighthave|  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.3.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, Android, 043-should, |  Actual Points:
  BugSmashFund   |
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by sisbell):

 * cc: sisbell (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] #30972 [Core Tor/Fallback Scripts]: 0-1. Run an opt-in process for relay operators to become fallbacks in 2019-2020

[Tor Bug Tracker & Wiki]

#30972: 0-1. Run an opt-in process for relay operators to become fallbacks in
2019-2020
---+
 Reporter:  teor   |  Owner:  (none)
 Type:  task   | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Fallback Scripts  |Version:
 Severity:  Normal | Resolution:
 Keywords:  fallback   |  Actual Points:
Parent ID:  #30971 | Points:  1
 Reviewer: |Sponsor:
---+

Comment (by teor):

 An operator asked us to update the addresses on
 4E8CE6F5651E7342C1E7E5ED031E82078134FB0D:
 https://lists.torproject.org/pipermail/tor-
 relays/2019-November/017924.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

[tor-bugs] #32594 [Core Tor/Tor]: Fix CID 1455953: Resource leaks in #32427

[Tor Bug Tracker & Wiki]

#32594: Fix CID 1455953:  Resource leaks in #32427
-+-
 Reporter:  teor |  Owner:  nickm
 Type:  defect   | Status:  assigned
 Priority:  High |  Milestone:  Tor: 0.4.3.x-final
Component:  Core |Version:  Tor: unspecified
  Tor/Tor|   Keywords:  043-must, network-team-roadmap-
 Severity:  Normal   |  november
Actual Points:   |  Parent ID:  #32408
   Points:  0.1  |   Reviewer:
  Sponsor:   |
  Sponsor31-must |
-+-
 {{{
 ** CID 1455953:  Resource leaks  (RESOURCE_LEAK)
 /src/app/config/config.c: 1983 in options_act_reversible()


 

 *** CID 1455953:  Resource leaks  (RESOURCE_LEAK)
 /src/app/config/config.c: 1983 in options_act_reversible()
 1977   tor_assert(*msg);
 1978
 1979   options_rollback_log_transaction(log_transaction);
 1980   options_rollback_listener_transaction(listener_transaction);
 1981
 1982  done:
CID 1455953:  Resource leaks  (RESOURCE_LEAK)
Variable "listener_transaction" going out of scope leaks the storage it
 points to.
 1983   return r;
 1984 }
 1985
 1986 /** If we need to have a GEOIP ip-to-country map to run with our
 configured
 1987  * options, return 1 and set *reason_out to a description
 of why. */
 1988 int
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32453 [Applications/Tor Browser]: connection no longer available

[Tor Bug Tracker & Wiki]

#32453: connection no longer available
--+---
 Reporter:  aldo341   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  duplicate
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by aldo341):

 I dwnloaded and installed 118 updates with windows update. Searched again
 : no longer upedate available.

 But the error message is still there when I try to open Tor browser :
 imposible to open the program, lack of api-ms-win-crt-convert-l1-1-0.dll,
 try to install again.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31341 [Applications/TorBirdy]: TorBirdy does not support Thunderbird 68

[Tor Bug Tracker & Wiki]

#31341: TorBirdy does not support Thunderbird 68
--+-
 Reporter:  ozozoz|  Owner:  sukhbir
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/TorBirdy |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBirdy, Thunderbird 68  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 I just stumbled across this, too, since Thunderbird connects to mail
 provider(s) directly if TorBirdy was deactivated after upgrading to
 Thunderbird 68.x .

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

[tor-bugs] #32593 [- Select a component]: weedit

[Tor Bug Tracker & Wiki]

#32593: weedit
-+--
 Reporter:  digital1 |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Component:  - Select a component
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
 Need outsource photo editing with fast turnaround time and simple
 application? We suggest using Weedit.photos.com which offers portrait
 enhancement, removing the background, and clipping path services.
 [http://weedit.photos/photo-enhancement-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

[tor-bugs] #32592 [- Select a component]: old photo

[Tor Bug Tracker & Wiki]

#32592: old photo
-+--
 Reporter:  reto11   |  Owner:  (none)
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Component:  - Select a component
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
 Tattered memories captured on paper will be given a new breath by hands of
 our auteurs. Restoration photo is the only thing that will be effective in
 this case.
 [https://damagedphotorestoration.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] #32591 [Community]: photo 7

[Tor Bug Tracker & Wiki]

#32591: photo 7
---+---
 Reporter:  ottodamag  |  Owner:  ggus
 Type:  project| Status:  new
 Priority:  Medium |  Component:  Community
  Version: |   Severity:  Normal
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---
 Photo retouchers team offers quick digital retouching services: real
 estate photo enhancement portrait retouching, family portraits retouching,
 color correction, wedding retouching, body retouching
 [http://fixthephoto.com/editing-newborn-photos-services]

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31341 [Applications/TorBirdy]: TorBirdy does not support Thunderbird 68

[Tor Bug Tracker & Wiki]

#31341: TorBirdy does not support Thunderbird 68
--+-
 Reporter:  ozozoz|  Owner:  sukhbir
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/TorBirdy |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBirdy, Thunderbird 68  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by cypherpunks):

 So, where does this leave regular TorBirdy users?

 Anyone able and willing to take on the following workaround?

 > Thunderbird 68 already only supports !MailExtensions, but legacy
 extensions can supposedly be converted to[wiki:MailExtensions] relatively
 easily: It requires converting the old RDF manifest to a JSON manifest,
 and then in the JSON manifest the legacy key can be used to load the
 legacy XUL extension.
 > !https://developer.thunderbird.net/add-ons/tb68
 > !https://developer.thunderbird.net/add-ons/tb68/overlays

 (via https://redmine.tails.boum.org/code/issues/17219)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21952 [Applications/Tor Browser]: Onion-location: increasing the use of onion services through automatic redirects and aliasing

[Tor Bug Tracker & Wiki]

#21952: Onion-location: increasing the use of onion services through automatic
redirects and aliasing
-+-
 Reporter:  linda|  Owner:  acat
 Type:  project  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ux-team, tor-hs, network-team-   |  Actual Points:  5.5
  roadmap-november, TorBrowserTeam201911,|
  tbb-9.5|
Parent ID:  #30024   | Points:  6
 Reviewer:   |Sponsor:
 |  Sponsor27-must
-+-

Comment (by cypherpunks):

 Replying to [comment:80 antonela]:

 > 4. I don't think we need a menu under the [...] It adds noise and I
 don't see a real use case for it. Do you think I'm missing something? Let
 me know.
 >

 it tells about eyedropper. shouldnt it be spelled eavesdropper?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32588 [Core Tor/Tor]: Setting ORPort [ipv6]:auto mistakenly advertises port 94

[Tor Bug Tracker & Wiki]

#32588: Setting ORPort [ipv6]:auto mistakenly advertises port 94
--+--
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.4.1.6
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 last two bytes parsed as portnumber

 0x5e = 94 in decimal :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #31939 [Core Tor/Tor]: log spam: Bug: buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion !(buf->datalen >= INT_MAX - at_most) failed.

[Tor Bug Tracker & Wiki]

#31939: log spam: Bug: buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion
!(buf->datalen >= INT_MAX - at_most) failed.
-+-
 Reporter:  catalyst |  Owner:  teor
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.0.4-rc
 Severity:  Normal   | Resolution:
 Keywords:  consider-backport-after-0424,|  Actual Points:  0.1
  assert, fast-fix, 042-should, 035-backport,|
  040-backport, 041-backport, BugSmashFund   |
Parent ID:  #32022   | Points:  0.1
 Reviewer:  catalyst |Sponsor:
-+-

Comment (by cypherpunks):

 Replying to [ticket:31939 catalyst]:
 > (I assume the `#` in the middle of `INT_MAX` is a paste/transcription
 artifact, but then again it might not be.)

 ignore this
 {{{
 #
 }}}
  it is not there actually looks like:

 {{{
 Nov 24 07:14:18.000 [warn] {BUG} Bug: Non-fatal assertion !(buf->datalen
 >= INT_MAX - at_most) failed in buf_read_from_tls at buffers_tls.c:73.
 (Stack trace not available) (on Tor 0.4.1.6 )
 Nov 24 07:14:18.000 [warn] {BUG} tor_bug_occurred_(): Bug:
 buffers_tls.c:73: buf_read_from_tls: Non-fatal assertion !(buf->datalen >=
 INT_MAX - at_most) failed. (Future instances of this warning will be
 silenced.) (o
 n Tor 0.4.1.6 )
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32577 [Core Tor/Torsocks]: torsocks is not fully capable of performing required downloads

[Tor Bug Tracker & Wiki]

#32577: torsocks is not fully capable of performing required downloads
---+---
 Reporter:  estellnb   |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/Torsocks  |Version:  sbws: unspecified
 Severity:  Major  | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+---

Comment (by estellnb):

 I have now retried it with tor+torsocks on the tampered system and rustup
 works there without any problems. Obviously the NSA is selectively
 blocking this download for anonymous users. You will also need to try it
 from a clean boot medium. If it works well on your base system then it is
 likely compromised as well. I had a strange occurence with 'https://static
 .rust-lang.org/dist/2019-11-22/rustc-nightly-x86_64-unknown-linux-
 gnu.tar.xz' as well. At first rustup blocked on different clean tor
 systems on download of this file. As I discovered it to be easily
 downloadable without tor I have invoked torsocks wget on it. wget failed
 three times downloading the file and the fourth time it succeeded. From
 this time on rustc.xz could be easily downloaded via tor also by rustup.
 However since then rustup blocks on another download where you can not
 identify the file in question that easily.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #32590 [Circumvention/Snowflake]: Remove the "Experimental" label on the AMO listing of the Snowflake WebExt

[Tor Bug Tracker & Wiki]

#32590: Remove the "Experimental" label on the AMO listing of the Snowflake 
WebExt
-+-
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  defect   | Status:  new
 Priority:  Very Low |  Component:  Circumvention/Snowflake
  Version:   |   Severity:  Normal
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
 You can see an "Experimental" label when you go to
 https://addons.mozilla.org/en-US/firefox/addon/torproject-snowflake/

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

[tor-bugs] #32589 [Circumvention/Snowflake]: Update the logos of Firefox and Chrome in https://snowflake.torproject.org/

[Tor Bug Tracker & Wiki]

#32589: Update the logos of Firefox and Chrome in 
https://snowflake.torproject.org/
-+-
 Reporter:  cypherpunks  |  Owner:  (none)
 Type:  task | Status:  new
 Priority:  Very Low |  Component:  Circumvention/Snowflake
  Version:   |   Severity:  Trivial
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-


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