Re: [tor-bugs] #22560 [Applications/Tor Browser]: Update privacy.thirdparty.isolate preference in Torbutton

[Tor Bug Tracker & Wiki]

#22560: Update privacy.thirdparty.isolate preference in Torbutton
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-7.0-issues, tbb-regression,  |  Actual Points:
  TorBrowserTeam201706R  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arthuredelstein):

 Looks good to me as well. I'd also suggest changing the var
 `block_thirdparty` to `firstparty_isolate` or something similar.

--
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] #22610 [Applications/Tor Browser]: Tor Browser 7.5a1 crashes when opening a PDF file on my desktop

[Tor Bug Tracker & Wiki]

#22610: Tor Browser 7.5a1 crashes when opening a PDF file on my desktop
--+---
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * status:  new => needs_information
 * priority:  Medium => High
 * severity:  Normal => Major


Comment:

 Hm, there is no download box showing up for me. The document loads
 directly in the pdf viewer. Do you have a particular file causing this
 (maybe one I could download and then load from the desktop)?

 Note as well, the alpha and the stable are basically identical at this
 time apart from a Windows related patch being in the alpha series but not
 the stable one. So, that issue should happen on stable 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

Re: [tor-bugs] #20348 [Metrics/Censorship analysis]: Kazakhstan blocking of vanilla Tor, obfs4, and meek, starting 2016-06

[Tor Bug Tracker & Wiki]

#20348: Kazakhstan blocking of vanilla Tor, obfs4, and meek, starting 2016-06
-+--
 Reporter:  dcf  |  Owner:
 Type:  project  | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Metrics/Censorship analysis  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  censorship block kz  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by dcf):

 I attempted to summarize this ticket in an easier-to-read form at
 [[/doc/OONI/censorshipwiki/CensorshipByCountry/Kazakhstan#a20348]].

--
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] #22551 [Applications/Tor Browser]: F-Droid's Orfox APK file not updated to Tor Browser 7.0 yet

[Tor Bug Tracker & Wiki]

#22551: F-Droid's Orfox APK file not updated to Tor Browser 7.0 yet
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by tokotoko):

 * cc: fdsfgs@… (added)


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

[tor-bugs] #22612 [Applications/Tor Browser]: Provide a list sha256's for verified binary downloads from mirrors

[Tor Bug Tracker & Wiki]

#22612: Provide a list sha256's for verified binary downloads from mirrors
--+--
 Reporter:  BenjaminCarr  |  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  sha256
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 While attempting to bump the version in the OSX Homebrew system in the
 middle of the night I discovered that the list of sha256s provided did not
 allign with the downloaded DMGs that were on the mirrors:
 shasum -a 256 TorBrowser-7.0.1-osx64_ar.dmg
 96127d410647bc63b592238e7a5473a63c9588a88fbc501cbce93b02e546bf2e
 TorBrowser-7.0.1-osx64_ar.dmg
 when on the list it is:
 325550bf93c24e302354d4bcf90bda04540c4e8c78c270b735b5598e1dcd988d
 TorBrowser-7.0.1-osx64_ar.dmg

 Since distributing tainted software is of concern particularly on security
 related matters, I halted the PR and flagged it. Contributors on two other
 continents checked their mirrors, and we were all getting the same
 sha256s, but these did not align with the only published list of shas. The
 only publiclly avaailable sha list is for the signed software (here is
 v7.0.1): https://dist.torproject.org/torbrowser/7.0.1/sha256sums-unsigned-
 build.txt

 While we acknowledge the utility and use of the PGP *.asc signing, the
 homebrew (I have no idea what kind of reach we have for Tor products)
 currently require a sha256 on a downloaded file even if other verification
 methods are used. Thus to implement PGP verification we would need to do
 it on top of the sha256 unless we switch TorBrowser to `:latest` which we
 do not want to do for security reasons.

 As the tested sha256s are consistent across mirrors a published list of
 sha256s for known good installers/DMGs is requested; as I was not the only
 one confused; but rather four homebrew contributors/maintainers.

 Needing to wget all of the binaries to verify the sha's presents two
 problems, one the mirror used could be tainted/compromised; given recent
 seizures like those in France this is of modest concern. But even in
 affluent countries like the US highspeed broadband is not evenly
 distributed; and needing to pull 16 ~62MB DMG's is nearly a gigabyte of
 data just to verify the sha256s. A `verified` sha256 list solves both
 these problems.

--
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] #22573 [Webpages/Website]: GPG-key fetch instructions are out of date on verifying signatures website

[Tor Bug Tracker & Wiki]

#22573: GPG-key fetch instructions are out of date on verifying signatures 
website
--+---
 Reporter:  gk|  Owner:  linda
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by pastly):

 I believe this is an intermittent issue that may be caused by unreliable
 key servers in the pool. I was able to fetch the TB signing key from the
 pool with this command, and with this command wrapped with `torsocks`. I
 suspect the user was either unlucky or wasn't connect to the Internet.

 Why do we have users specify pool.sks-keyservers.net?

--
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] #22611 [Webpages/Website]: Make TB uninstall instructions more detailed in FAQ

[Tor Bug Tracker & Wiki]

#22611: Make TB uninstall instructions more detailed in FAQ
--+---
 Reporter:  pastly|  Owner:  linda
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by cypherpunks):

 +1, I was actually shocked when I discovered that the FAQ didn't mention
 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

[tor-bugs] #22611 [Webpages/Website]: Make TB uninstall instructions more detailed in FAQ

[Tor Bug Tracker & Wiki]

#22611: Make TB uninstall instructions more detailed in FAQ
--+---
 Reporter:  pastly|  Owner:  linda
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+---
 macOS requires special treatment.

 See https://github.com/pastly/webwml branch macos-tb-uninstall

--
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] #22597 [Internal Services/Tor Sysadmin Team]: Please make an LDAP account for Chelsea

[Tor Bug Tracker & Wiki]

#22597: Please make an LDAP account for Chelsea
-+-
 Reporter:  isis |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by chelseakomlo):

 Replying to [comment:4 weasel]:
 > Chelsea might want to have a key that doesn't expire in less than 4
 weeks time.

 My apologies, thanks for pointing this out. I've updated this key.

 Let me know what else I can do!

--
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] #22610 [Applications/Tor Browser]: Tor Browser 7.5a1 crashes when opening a PDF file on my desktop

[Tor Bug Tracker & Wiki]

#22610: Tor Browser 7.5a1 crashes when opening a PDF file on my desktop
--+---
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-crash
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+---
 Tor Browser 7.5a1 (7.0.1 doesn't have this issue as far as I tested)

 Platform: Debian sid 64 bits.

 Steps to reproduce:

 1. Open Tor Browser,
 2. Ctrl+O
 3. Select some PDF file and click open
 4. Download box will show up, click on cancel
 5. it should crash

 When debugging:

 {{{
 [Parent 3674] ###!!! ABORT: __delete__()d actor: file /home/debian/build
 /tor-browser/ipc/glue/ProtocolUtils.cpp, line 299
 [Parent 3674] ###!!! ABORT: __delete__()d actor: file /home/debian/build
 /tor-browser/ipc/glue/ProtocolUtils.cpp, line 299
 Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close
 with reason=AbnormalShutdown (t=8.69987) [GFX1-]: Receive IPC close with
 reason=AbnormalShutdown
 [Child 3795] WARNING: pipe error (3): Connection reset by peer: file
 /home/debian/build/tor-
 browser/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 322
 [Child 3795] ###!!! ABORT: Aborting on channel error.: file
 /home/debian/build/tor-browser/ipc/glue/MessageChannel.cpp, line 2152
 [Child 3795] ###!!! ABORT: Aborting on channel error.: file
 /home/debian/build/tor-browser/ipc/glue/MessageChannel.cpp, line 2152
 [notice] Owning controller connection has closed -- exiting now.
 [notice] Catching signal TERM, exiting cleanly.
 ./Browser/start-tor-browser: line 369:  3674 Segmentation fault  (core
 dumped) TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor
 Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" <
 /dev/null
 }}}

--
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] #22609 [Webpages/Website]: Fix 3 links in FAQ "What would The Tor Project do with more funding?"

[Tor Bug Tracker & Wiki]

#22609: Fix 3 links in FAQ "What would The Tor Project do with more funding?"
--+---
 Reporter:  pastly|  Owner:  linda
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+---
 See https://github.com/pastly/webwml branch usage-link-fixes

 Update to fix metrics.tp.o links.

--
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] #20348 [Metrics/Censorship analysis]: Kazakhstan blocking of vanilla Tor, obfs4, and meek, starting 2016-06 (was: Kazakhstan blocking of vanilla Tor and obfs4 by Allot Communications ha

[Tor Bug Tracker & Wiki]

#20348: Kazakhstan blocking of vanilla Tor, obfs4, and meek, starting 2016-06
-+--
 Reporter:  dcf  |  Owner:
 Type:  project  | Status:  reopened
 Priority:  Medium   |  Milestone:
Component:  Metrics/Censorship analysis  |Version:
 Severity:  Normal   | Resolution:
 Keywords:  censorship block kz  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by dcf):

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


--
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] #20348 [Metrics/Censorship analysis]: Kazakhstan blocking of vanilla Tor and obfs4 by Allot Communications hardware, 2016-06

[Tor Bug Tracker & Wiki]

#20348: Kazakhstan blocking of vanilla Tor and obfs4 by Allot Communications
hardware, 2016-06
-+-
 Reporter:  dcf  |  Owner:
 Type:  project  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Metrics/Censorship analysis  |Version:
 Severity:  Normal   | Resolution:  invalid
 Keywords:  censorship block kz  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by dcf):

 Replying to [comment:145 dcf]:
 > Blocked sites are redirected to !http://92.63.88.128/?NTDzLZ

 Doing a web search for "NTDzLZ" found a few threads with other people
 noticing the blocks. The latest is dated December 25, 2016, which is
 slightly later than the latest injection I saw myself, which was December
 21, 2016 (comment:173).

  * 2016-11-22 http://www.cyberforum.ru/viruses/thread1857039.html
 
([https://web.archive.org/web/20170614212433/http://www.cyberforum.ru/viruses/thread1857039.html
 archive])
  Translated: "Hello, I'm here for the first time. In general, here's
 the problem: I can not go to some sites (xvideos.com, redtube.com) (the
 problem is certainly not in them) but still want to fix them. When I come,
 I throw it at !http://92.63.88.128/?NTDzLZ and there it is empty"
  * 2016-11-25 http://ping-
 admin.ru/free_test/result/148005106722x8h272z9w4y2r3517e7.html
 ([https://web.archive.org/web/20170614213022/http://ping-
 admin.ru/free_test/result/148005106722x8h272z9w4y2r3517e7.html archive])
  Connectivity test. The line for unihost.kz in Alatau refers to the
 URL.
  "rus.porn/videos/14854/
  Казахстан, Алатау При поддержке Unihost.kz. Кол-во редиректов: 1
 !http://92.63.88.128/?NTDzLZ;
  * 2016-12-16 http://www.cyberforum.ru/viruses/thread1880138.html
 
([https://web.archive.org/web/20170614212224/http://www.cyberforum.ru/viruses/thread1880138.html
 archive])
  Translated: "I'm trying to go to the site newgrounds.com, it does not
 enter and I throw it on the link !http://92.63.88.128/?NTDzLZ , but before
 it stopped . Kaspersky swears, writes a virus site, there are no viruses
 on the computer, it was checked by another web, Kaspersky"
  * 2016-12-16 https://prezi.com/vwyiuh9dgbv4/pokemon-bloody-platinum-
 download-free/
 ([https://web.archive.org/web/20170614212749/https://prezi.com/vwyiuh9dgbv4
 /pokemon-bloody-platinum-download-free/ archive])
  Looks like a spam presentation with HTML in the description that
 refers to Kaspersky antivirus. Puts a `=` at the end of the URL, unlike
 other sources.
  "Веб-адрес:http://92.63.88.128/?NTDzLZ=;>!http://92.63.88.128/?NTDzLZ=
 Заблокирован Веб-Антивирусом Причина: опасный веб-
 адрес http://touch.kaspersky.com/kfa_cup_f8f731b4-629f-
 4b7c-923c-495d87bf7e09/1481884315">Нажмите здесь, если считаете, что веб-
 страница заблокирована ошибочно."
  * 2016-12-22 https://vk.com/wall297604842_11
 ([https://web.archive.org/web/20170614212555/https://vk.com/wall297604842_11
 archive])
  A wall post that says only "!http://92.63.88.128/?NTDzLZ;
  * 2016-12-25 http://ping-
 admin.com/free_test/result/14817131651081dy5bl67oc53bs4b1081.html
 ([https://web.archive.org/web/20170614213317/http://ping-
 admin.com/free_test/result/14817131651081dy5bl67oc53bs4b1081.html
 archive])
  Connectivity test. The lines for unihost.kz in Alatau, Internet-
 Kompanii PS in Almaty, and hoster.kz in Karaganda refer to the URL.
  "kissk.ru
  Казахстан, Алатау При поддержке Unihost.kz. Кол-во редиректов: 1
 !http://92.63.88.128/?NTDzLZ
  Казахстан, Алматы При поддержке интернет-компании PS. Кол-во
 редиректов: 1 !http://92.63.88.128/?NTDzLZ
  Казахстан, Караганда При поддержке Hoster.KZ. Кол-во редиректов: 1
 !http://92.63.88.128/?NTDzLZ;

--
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] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 https://hg.mozilla.org/mozilla-central/rev/169d5dfe505f

--
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] #22608 [Core Tor/Tor]: Refactor connection_or_set_state(OPEN) to connection_or_set_state_open()

[Tor Bug Tracker & Wiki]

#22608: Refactor connection_or_set_state(OPEN) to connection_or_set_state_open()
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  .2
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * owner:   => nickm
 * status:  new => accepted


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

Re: [tor-bugs] #22608 [Core Tor/Tor]: Refactor connection_or_set_state(OPEN) to connection_or_set_state_open()

[Tor Bug Tracker & Wiki]

#22608: Refactor connection_or_set_state(OPEN) to connection_or_set_state_open()
--+
 Reporter:  nickm |  Owner:  nickm
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:  .2
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * status:  accepted => 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] #22608 [Core Tor/Tor]: Refactor connection_or_set_state(OPEN) to connection_or_set_state_open()

[Tor Bug Tracker & Wiki]

#22608: Refactor connection_or_set_state(OPEN) to connection_or_set_state_open()
--+
 Reporter:  nickm |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:  .2|   Reviewer:
  Sponsor:|
--+
 I have a patch in branch "callgraph_reduction" that takes the size of our
 largest SCC from down to 26 functions (from ~64).

--
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] #22067 [Applications/Tor Browser]: NoScript Click-to-Play bypass with embedded videos and audios

[Tor Bug Tracker & Wiki]

#22067: NoScript Click-to-Play bypass with embedded videos and audios
--+--
 Reporter:  samantharis   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-security, noscript|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Holy shit!!! Forbid all plugins!!!

--
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] #22067 [Applications/Tor Browser]: NoScript Click-to-Play bypass with embedded videos and audios

[Tor Bug Tracker & Wiki]

#22067: NoScript Click-to-Play bypass with embedded videos and audios
--+--
 Reporter:  samantharis   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-security, noscript|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by ma1):

 This does not happen in NoScript's default configuration, only in Tor
 Browser's custom setup.

 Easiest work-around: turn "Forbid other plugins" (noscript.forbidPlugins)
 to true.

 Working on a fix for 5.0.6, hopefully by this week.

--
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] #22607 [Applications/Tor Browser Sandbox]: Make it clear that basically 0 active development is happening.

[Tor Bug Tracker & Wiki]

#22607: Make it clear that basically 0 active development is happening.
--+-
 Reporter:  yawning   |  Owner:  yawning
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser Sandbox  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 Mostly a documentation fix.

 https://lists.torproject.org/pipermail/tbb-dev/2017-May/000556.html
 {{{
 Anyway, it's fairly clear to me that there is no clear plan for how to
 handle sandboxing's requirements vs `tor-launcher`, so I will continue
 with:

   "the only guaranteed maintenance it gets is that it will get fixes
when it breaks on Yawning's laptop, or when people submit detailed
bug reports that Yawning can fix in spare time"
 }}}

--
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] #22603 [Applications/Tor Browser]: tor browser crashing on start up windows 10

[Tor Bug Tracker & Wiki]

#22603: tor browser crashing on start up windows 10
--+---
 Reporter:  No1   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by No1):

 no i've deleted and installed it multiple times on the desktop and usb
 drive i normally use still nothing

--
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] #21321 [Applications/Tor Browser]: .onion HTTP is shown as non-secure in Tor Browser

[Tor Bug Tracker & Wiki]

#21321: .onion HTTP is shown as non-secure in Tor Browser
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Blocker   | Resolution:
 Keywords:  ff52-esr, tbb-usability, ux-team  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by mo):

 It also shows severe warnings when you try to submit a form "over HTTP"
 (to an onion).

--
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] #16010 [Applications/Tor Browser]: Get a working content process sandbox for Tor Browser on Windows

[Tor Bug Tracker & Wiki]

#16010: Get a working content process sandbox for Tor Browser on Windows
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  ff52-esr, tbb-e10s, tbb-gitian,  |  Actual Points:
  tbb-security, TorBrowserTeam201706,|
  GeorgKoppen201706  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by cypherpunks):

 Replying to [comment:38 gk]:
 > Replying to [comment:37 cypherpunks]:
 > > Georg, which way did you decide to go?
 >
 > Not sure yet. I ripped out all the problematic parts and got it compiled
 and running without exploding in my face.
 You've removed sandbox protections, right? :)
 > I'll post a build for others to test tomorrow probably. I hope to find
 cases where that build is exploding while normal Firefox works fine to
 fill then the missing gaps with something smart. :)
 Then you'll need to attack the chrome process through IPC, see
 https://dxr.mozilla.org/mozilla-
 esr52/source/security/sandbox/chromium/sandbox/win/src/crosscall_server.cc#131
 > > GCC's attempts seem to be finished with
 https://gcc.gnu.org/wiki/WindowsGCCImprovementsGSoC2008
 >
 > Well, thanks for this page but looking at the SEH Suppport section it
 seems there was still a bunch of stuff to do back at that time.
 Yes, this page is about that they have a lot of things partially
 completed/investigated.

--
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] #21999 [Applications/Tor Browser]: The "request English language web pages"-prompt is not working in 7.0a3

[Tor Bug Tracker & Wiki]

#21999: The "request English language web pages"-prompt is not working in 7.0a3
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-e10s, tbb-7.0-must,|  Actual Points:
  TorBrowserTeam201706R, tbb-7.0-issues, tbb-|
  regression |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * status:  needs_review => needs_revision


Comment:

 Replying to [comment:10 mcs]:
 > Replying to [comment:9 arthuredelstein]:
 > > Here's a patch for review:
 > > https://github.com/arthuredelstein/torbutton/commit/21999
 >
 > The code looks okay but Kathy and I have a couple of questions:
 > * Why is the delay before showing the prompt only imposed for about:tor?
 > * The old code only showed the prompt when the user accessed an HTTP
 page. The new code will show it at startup on about:tor, which seems like
 a less friendly "first run" experience (mostly because the prompt will
 cover up a lot of the about:tor content). Are we okay with this change in
 behavior?

 No. I think we should try to get it going the way it was implemented in
 #18019. Or at least the patch should give a similar experience.

--
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] #22606 [Webpages/Website]: update the meta data information for the website

[Tor Bug Tracker & Wiki]

#22606: update the meta data information for the website
--+--
 Reporter:  isabela   |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Description changed by isabela:

Old description:

> We want to update the meta data of torproject.org homepage to optimize it
> for search eng as well as to leave a tip for users who might be in places
> where our site is blocked and they are trying to download Tor. In those
> cases, they will be able to see a tip that teaches them to use get tor to
> get tor browser.
>
> We want to change the 'keywords' and 'description' meta tags to:
>
> {{{
>

> }}}
> {{{
> mailto:get...@torproject.org] for help downloading Tor Browser.">
> }}}
> {{{
>

> }}}
> {{{
> 
> }}}

New description:

 We want to update the meta data of torproject.org homepage to optimize it
 for search eng as well as to leave a tip for users who might be in places
 where our site is blocked and they are trying to download Tor. In those
 cases, they will be able to see a tip that teaches them to use get tor to
 get tor browser.

 We want to change the 'keywords' and 'description' meta tags to:

 {{{
 mailto:get...@torproject.org]
 for help downloading Tor Browser.">
 }}}
 {{{
 
 }}}

--

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

Re: [tor-bugs] #21321 [Applications/Tor Browser]: .onion HTTP is shown as non-secure in Tor Browser

[Tor Bug Tracker & Wiki]

#21321: .onion HTTP is shown as non-secure in Tor Browser
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Blocker   | Resolution:
 Keywords:  ff52-esr, tbb-usability, ux-team  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mcs):

 * cc: mcs (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] #21321 [Applications/Tor Browser]: .onion HTTP is shown as non-secure in Tor Browser

[Tor Bug Tracker & Wiki]

#21321: .onion HTTP is shown as non-secure in Tor Browser
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Blocker   | Resolution:
 Keywords:  ff52-esr, tbb-usability, ux-team  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mrphs):

 * severity:  Major => Blocker


Comment:

 bumping the severity to "blocker" as I'm seeing on a day to day basis this
 has started to make users wonder about the security of sites accessible by
 .onion. People are falling back to other (less safe and potentially
 dangerous) communication methods because 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] #22606 [Webpages/Website]: update the meta data information for the website

[Tor Bug Tracker & Wiki]

#22606: update the meta data information for the website
--+--
 Reporter:  isabela   |  Owner:  hiro
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by isabela):

 * owner:  linda => hiro
 * status:  new => assigned


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

Re: [tor-bugs] #20105 [Applications/Tor Browser]: Selecting Open With TorBrowser on a Mac Opens the File in Default Browser Instead

[Tor Bug Tracker & Wiki]

#20105: Selecting Open With TorBrowser on a Mac Opens the File in Default 
Browser
Instead
--+--
 Reporter:  hdub  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #17670| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 This behaviour appears to be fixed in 7.0.1 on macOS 10.12.5, but it now
 also opens a second TorBrowser window when you open a local file in
 TorBrowser.

--
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] #22606 [Webpages/Website]: update the meta data information for the website

[Tor Bug Tracker & Wiki]

#22606: update the meta data information for the website
--+---
 Reporter:  isabela   |  Owner:  linda
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+---
 We want to update the meta data of torproject.org homepage to optimize it
 for search eng as well as to leave a tip for users who might be in places
 where our site is blocked and they are trying to download Tor. In those
 cases, they will be able to see a tip that teaches them to use get tor to
 get tor browser.

 We want to change the 'keywords' and 'description' meta tags to:

 {{{


 }}}
 {{{
 mailto:get...@torproject.org]
 for help downloading Tor Browser.">
 }}}
 {{{


 }}}
 {{{
 
 }}}

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

[tor-bugs] #22605 [Core Tor/Tor]: sandbox_intern_string(): Bug: No interned sandbox parameter found for /etc/tor/torrc.d/

[Tor Bug Tracker & Wiki]

#22605: sandbox_intern_string(): Bug: No interned sandbox parameter found for
/etc/tor/torrc.d/
--+
 Reporter:  toralf|  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: 0.3.1.3-alpha
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 got this today at a stable hardened Gentoo linux server:
 {{{
 mr-fox ~ # cat x.log
 Jun 14 21:19:55.000 [warn] sandbox_intern_string(): Bug: No interned
 sandbox parameter found for /etc/tor/torrc.d/ (on Tor 0.3.1.3-alpha
 dc47d936d47ffc25)
 Jun 14 21:19:55.000 [warn] sandbox_intern_string(): Bug: No interned
 sandbox parameter found for /etc/tor/torrc.d/ (on Tor 0.3.1.3-alpha
 dc47d936d47ffc25)

  T= 1497467995
 (Sandbox) Caught a bad syscall attempt (syscall open)
 /usr/bin/tor(+0x18e5f5)[0x55ec9b7a75f5]
 /lib64/libc.so.6(opendir+0x11)[0x7f5dfe271421]
 /lib64/libc.so.6(opendir+0x11)[0x7f5dfe271421]
 /usr/bin/tor(tor_listdir+0x32)[0x55ec9b7a32e2]
 /usr/bin/tor(+0x179080)[0x55ec9b792080]
 /usr/bin/tor(config_get_lines_include+0x38)[0x55ec9b792258]
 /usr/bin/tor(options_init_from_string+0x1df)[0x55ec9b716d0f]
 /usr/bin/tor(options_init_from_torrc+0x1f1)[0x55ec9b717221]
 /usr/bin/tor(+0x4f399)[0x55ec9b668399]
 /usr/lib64/libevent-2.1.so.6(+0x23749)[0x7f5dff649749]
 /usr/lib64/libevent-2.1.so.6(event_base_loop+0x57f)[0x7f5dff64a5ef]
 /usr/bin/tor(do_main_loop+0x24d)[0x55ec9b66693d]
 /usr/bin/tor(tor_main+0x1c3d)[0x55ec9b66a32d]
 /usr/bin/tor(main+0x28)[0x55ec9b661d18]
 /lib64/libc.so.6(__libc_start_main+0xfc)[0x7f5dfe1d972c]
 /usr/bin/tor(_start+0x29)[0x55ec9b661d69]

 }}}

--
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] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by gk):

 I am wondering, though, why this is happening again (assuming it is really
 something like #10761) because it seemed to me the underlying issues got
 fixed and the fixes are available in esr45/esr52.

--
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] #22601 [Internal Services/Tor Sysadmin Team]: Please set up Apache on corsicum

[Tor Bug Tracker & Wiki]

#22601: Please set up Apache on corsicum
-+
 Reporter:  karsten  |  Owner:  tpa
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by karsten):

 Thanks!

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

Re: [tor-bugs] #16010 [Applications/Tor Browser]: Get a working content process sandbox for Tor Browser on Windows

[Tor Bug Tracker & Wiki]

#16010: Get a working content process sandbox for Tor Browser on Windows
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  ff52-esr, tbb-e10s, tbb-gitian,  |  Actual Points:
  tbb-security, TorBrowserTeam201706,|
  GeorgKoppen201706  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by gk):

 Replying to [comment:37 cypherpunks]:
 > Georg, which way did you decide to go?

 Not sure yet. I ripped out all the problematic parts and got it compiled
 and running without exploding in my face. I'll post a build for others to
 test tomorrow probably. I hope to find cases where that build is exploding
 while normal Firefox works fine to fill then the missing gaps with
 something smart. :)

 > GCC's attempts seem to be finished with
 https://gcc.gnu.org/wiki/WindowsGCCImprovementsGSoC2008

 Well, thanks for this page but looking at the SEH Suppport section it
 seems there was still a bunch of stuff to do back at that time.

--
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] #16010 [Applications/Tor Browser]: Get a working content process sandbox for Tor Browser on Windows

[Tor Bug Tracker & Wiki]

#16010: Get a working content process sandbox for Tor Browser on Windows
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Major| Resolution:
 Keywords:  ff52-esr, tbb-e10s, tbb-gitian,  |  Actual Points:
  tbb-security, TorBrowserTeam201706,|
  GeorgKoppen201706  |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by cypherpunks):

 Georg, which way did you decide to go?
 GCC's attempts seem to be finished with
 https://gcc.gnu.org/wiki/WindowsGCCImprovementsGSoC2008

--
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] #22566 [Applications/TorBirdy]: Let user to hide "TorBirdy Enabled" message.

[Tor Bug Tracker & Wiki]

#22566: Let user to hide "TorBirdy Enabled" message.
---+-
 Reporter:  cypherpunks|  Owner:  sukhbir
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/TorBirdy  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by cypherpunks):

 By different modes, like for Tor Browser (#17103)?

--
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] #21593 [Webpages/Website]: drop tor2web from the website lists

[Tor Bug Tracker & Wiki]

#21593: drop tor2web from the website lists
--+
 Reporter:  arma  |  Owner:  atagar
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by hiro):

 * status:  new => needs_revision


Comment:

 Tor2web has already been dropped from the website projects list months
 ago. Should we consider adding it back?

--
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] #21527 [Webpages/Website]: Please add iwakeh to the Core Tor People page

[Tor Bug Tracker & Wiki]

#21527: Please add iwakeh to the Core Tor People page
--+
 Reporter:  karsten   |  Owner:  hiro
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by hiro):

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


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

Re: [tor-bugs] #22334 [Webpages/Blog]: Missing top-right links in blog

[Tor Bug Tracker & Wiki]

#22334: Missing top-right links in blog
---+--
 Reporter:  teor   |  Owner:  hiro
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ux-team|  Actual Points:
Parent ID:  #22013 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by linda):

 Replying to [comment:1 arma]:
 > Worthwhile to do, but not critical for getting things working. We might
 even leave this one for when we have a uniform style across websites. But
 it would be sad to leave it for a year if it takes a year to have that
 uniform style.

 I agree that it's not critical to get things working, and it's better to
 wait until there is a uniform style across websites. Considering that
 those links were not there before, I think it's okay to leave as is, even
 for a year.

 I think the bigger question here is: do we want the blog as a separate
 entity from the website (it seemed to be so previously, since it was
 styled differently, and didn't link to the other torproject.org pages) or
 it to be "integrated" into the main website (the backend can be different,
 but the styling is consistent throughout all the websites, and it to be
 linked from tpo.org/link to tpo.org).

 I agree that Teor makes a good point that people who come to the blog
 should be able to download, install, and check out other pages of
 torproject.org. And for this reason, I am a fan of styling the blog
 consistently with the website and linking from tpo/to tpo (by including it
 in the header, and the header being the same on the tor blog too)--when
 the new website launches.

 Thoughts?

--
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] #22334 [Webpages/Blog]: Missing top-right links in blog

[Tor Bug Tracker & Wiki]

#22334: Missing top-right links in blog
---+--
 Reporter:  teor   |  Owner:  hiro
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ux-team|  Actual Points:
Parent ID:  #22013 | Points:
 Reviewer: |Sponsor:
---+--

Comment (by linda):

 Replying to [comment:2 hiro]:
 > Those links weren't there in the old blog. Unless I am missing
 something? As far as I understand this template we are using is a bit old
 and has a few issues, maybe it is worth having some ux person review it.

 Hiro is correct in saying that those links were not in the old blog.

--
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] #22334 [Webpages/Blog]: Missing top-right links in blog

[Tor Bug Tracker & Wiki]

#22334: Missing top-right links in blog
---+--
 Reporter:  teor   |  Owner:  hiro
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Webpages/Blog  |Version:
 Severity:  Normal | Resolution:
 Keywords:  ux-team|  Actual Points:
Parent ID:  #22013 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by hiro):

 * keywords:   => ux-team


--
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] #20017 [Applications/Tor Browser]: Browser Window Rendered Incorrectly with External Display on Mac OS

[Tor Bug Tracker & Wiki]

#20017: Browser Window Rendered Incorrectly with External Display on Mac OS
--+
 Reporter:  hdub  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  worksforme
 Keywords:  tbb-usability |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by cypherpunks):

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


Comment:

 Not reproducible in 7.0.1 on macOS 10.12.5

--
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] #21982 [Applications/Quality Assurance and Testing]: Fix Tor Browser testsuite tests on ESR52

[Tor Bug Tracker & Wiki]

#21982: Fix Tor Browser testsuite tests on ESR52
-+-
 Reporter:  boklm|  Owner:  boklm
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Quality Assurance and   |Version:
  Testing|
 Severity:  Normal   | Resolution:
 Keywords:  tbb-7.0-must, TorBrowserTeam201706   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by boklm):

 * cc: tbb-team (added)


Comment:

 The `svg-disable` test should be fixed with commit
 6cf19ba0a0cd15bcc0892d21b1af79abd2c09ed0.
 The `settings` test should be fixed with commit
 296ef8c570778ac5a048703bf4ed06b9f53cd629.

--
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] #22566 [Applications/TorBirdy]: Let user to hide "TorBirdy Enabled" message.

[Tor Bug Tracker & Wiki]

#22566: Let user to hide "TorBirdy Enabled" message.
---+-
 Reporter:  cypherpunks|  Owner:  sukhbir
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Applications/TorBirdy  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by sukhbir):

 Sounds like a good idea in theory but I need to think about how we can do
 it without removing it for all users. Let me know if you have any ideas.

--
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] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 > I could not reproduce the problem following the steps in #10761.

 Because it's race condition, in ideal world (where users with bug lives)
 dll unloaded just after last FreeLibrary() called, in non-ideal world
 (where users without bug lives) code with thunk from freed library still
 in place and PR_Free() successfully finished.

--
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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 Replying to [comment:20 iwakeh]:
 > Oh, only the interface was added.
 > What could getAnnotations, getUnrecognizedLines return when called on an
 UnparseableDescriptor?

 Right now they don't return anything, that is, they return an empty list
 or `null`.

 But in theory we could return whatever annotations or unrecognized lines
 we found until running into a `DescriptorParseException`.  I have an idea
 how to build this with ''relatively'' little code changes, but I'll hold
 off until I hear whether that's even a good idea.

 Another solution that I don't like as much is that we introduce a new
 interface `ParsedDescriptor` that extends `Descriptor` and that other
 (parsed) descriptors extend.  That new interface could then contain these
 two methods, so they're not available in `UnparseableDescriptor`.  The
 part that I don't like there is that we'd have to deprecate the current
 methods in `Descriptor`, and applications depending on them would have to
 downcast their `Descriptor` instances to `ParsedDescriptor` instances just
 to get the annotations (or unrecognized lines).  Slightly eww.

 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] #21727 [Applications/Tor Browser]: Investigate network ID feature in ESR 52

[Tor Bug Tracker & Wiki]

#21727: Investigate network ID feature in ESR 52
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-7.0-must,  |  Actual Points:
  TorBrowserTeam201706   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 Tor Browser should intercept system calls and spoof IPs and MACs for
 firefox.exe processes to prevent such wonderful "features" from being used
 as a part of exploit.

--
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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 Replying to [comment:19 iwakeh]:
 > Replying to [comment:18 karsten]:
 > > [snip]
 > >
 > > The issue with `DescriptorCollector` returning `void` is that we
 cannot return any exceptions caught while fetching descriptor files from
 the remote CollecTor host to the caller.  This could be anything from
 fetching the `index.json` file or an actual descriptor file to differences
 between expected and actual file size or even indexing the local target
 directory.
 > >
 > > What we ''can'' do is log these exceptions/issues, so that the
 operator gets aware of them.  But we can't hand over exceptions to the
 application.  At least not easily (see `ExceptionListener`).
 >
 > Well, throwing an Exception is a way to communicate problems to the
 caller.  Anyway, there are not that many distinguishable error situations;
 e.g. w/o index.json there is no descriptor downloading -> Exception.

 A missing `index.json` might indeed qualify for throwing an `Exception`,
 because `DescriptorIndexCollector` cannot recover from that.  But there
 are other exception cases, like an issue with downloading a specific file,
 that `DescriptorIndexCollector` can work around by trying the next file.
 And if we want to provide best effort results, we'll have to recover from
 as many issues as possible.  In such a case, where would we throw an
 `Exception`?

--
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] #22593 [Webpages/Website]: Minify HTML, CSS and JavaScript resources on all websites of the torproject.org to save a bit of bandwidth

[Tor Bug Tracker & Wiki]

#22593: Minify HTML, CSS and JavaScript resources on all websites of the
torproject.org to save a bit of bandwidth
--+---
 Reporter:  cypherpunks   |  Owner:  linda
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by cypherpunks):

 For www.torproject.org HTML:

 {{{Original size: 15,052. Minified size: 10,178. Savings: 4,874
 (32.38%).}}}

--
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] #21999 [Applications/Tor Browser]: The "request English language web pages"-prompt is not working in 7.0a3

[Tor Bug Tracker & Wiki]

#21999: The "request English language web pages"-prompt is not working in 7.0a3
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff52-esr, tbb-e10s, tbb-7.0-must,|  Actual Points:
  TorBrowserTeam201706R, tbb-7.0-issues, tbb-|
  regression |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by mcs):

 Replying to [comment:9 arthuredelstein]:
 > Here's a patch for review:
 > https://github.com/arthuredelstein/torbutton/commit/21999

 The code looks okay but Kathy and I have a couple of questions:
 * Why is the delay before showing the prompt only imposed for about:tor?
 * The old code only showed the prompt when the user accessed an HTTP page.
 The new code will show it at startup on about:tor, which seems like a less
 friendly "first run" experience (mostly because the prompt will cover up a
 lot of the about:tor content). Are we okay with this change in behavior?

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

Re: [tor-bugs] #22512 [Metrics/metrics-lib]: Add enums for keywords used in exit lists, Torperf measurement results, bridge pool assignments, and soon sanitized web logs

[Tor Bug Tracker & Wiki]

#22512: Add enums for keywords used in exit lists, Torperf measurement results,
bridge pool assignments, and soon sanitized web logs
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Old description:

> We recently introduced the `Key` enum with keywords contained in relay
> descriptors, sanitized bridge descriptors, and sanitized bridge pool
> assignments.  We did not include keywords in exit lists and Torperf
> measurement results, and in retrospect we should have excluded sanitized
> bridge pool assignments there.
>
> The reason why each data source should have its own enum is that naming
> conventions might vary in terms of upper/lower case and word separators.
> For example, Tor descriptors use `lower-case-keywords`, exit lists
> contain `CamelCase`, and Torperf/OnionPerf use
> `ALL_UPPER_CASE_WITH_UNDERSCORES`.  There could be conflicts for keywords
> like `source` vs. `SOURCE`.

New description:

 Todo derived from the discussion in comments 1 to 4:

 Add keywords for all descriptors to `Key` enum.
 Use a one letter prefix for keywords from non-Tor data sources.
 First step: determine the best letter for each non-Tor source.


 Original summary: We recently introduced the `Key` enum with keywords
 contained in relay descriptors, sanitized bridge descriptors, and
 sanitized bridge pool assignments.  We did not include keywords in exit
 lists and Torperf measurement results, ~~and in retrospect we should have
 excluded sanitized bridge pool assignments there.~~

 ~~The reason why each data source should have its own enum is that naming
 conventions might vary in terms of upper/lower case and word separators.
 For example, Tor descriptors use `lower-case-keywords`, exit lists contain
 `CamelCase`, and Torperf/OnionPerf use `ALL_UPPER_CASE_WITH_UNDERSCORES`.
 There could be conflicts for keywords like `source` vs. `SOURCE`.~~

--

Comment (by iwakeh):

 True!  I added the new todos to the summary for easier reference.

--
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] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by gk):

 Replying to [comment:42 cypherpunks]:
 > > worksforme
 > Then you need to disable changing for about:preferences#privacy or
 something yet, who knows what config can to brick user's
 privacy/expirience again if browser unsupport mingw build env for real.

 It's not clear whether my theory in comment:39 is actually true. I could
 not reproduce the problem following the steps in #10761.

--
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] #18290 [Applications/Tor Browser]: Update Windows toolchain to work with Firefox 45 ESR

[Tor Bug Tracker & Wiki]

#18290: Update Windows toolchain to work with Firefox 45 ESR
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-gitian, ff45-esr,|  Actual Points:
  TorBrowserTeam201604, GeorgKoppen201604|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * parent:  #18226 =>


Comment:

 Replying to [comment:8 bugzilla]:
 > You've already had adventures with that in #10761 and are going to have
 again...

 True

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

[tor-bugs] #22604 [Applications/GetTor]: GetTor better channels

[Tor Bug Tracker & Wiki]

#22604: GetTor better channels
-+--
 Reporter:  dracofrog|  Owner:  ilv
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/GetTor  |Version:
 Severity:  Normal   |   Keywords:  GetTor , Torrent
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 > GetTor is a service that provides alternative methods to download the
 Tor Browser, especially for people living in places with high levels of
 censorship, where access to Tor Project's website is restricted.
 If you have suggestions for more/better channels
 Torrent
 Puablic magnet

--
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] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by cypherpunks):

 > worksforme
 Then you need to disable changing for about:preferences#privacy or
 something yet, who knows what config can to brick user's
 privacy/expirience again if browser unsupport mingw build env for real.

--
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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Oh, only the interface was added.
 What could getAnnotations, getUnrecognizedLines return when called on an
 UnparseableDescriptor?

--
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] #22576 [Obfuscation/Obfsproxy]: obfs4 through proxy is not working anymore with Tor Browser 7.0 on Windows

[Tor Bug Tracker & Wiki]

#22576: obfs4 through proxy is not working anymore with Tor Browser 7.0 on 
Windows
---+-
 Reporter:  albesp77   |  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Obfsproxy  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-7.0-issues |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by gk):

 So, testing on Windows with a default Squid installation and 7.0/7.0.1
 works for me. Seems I at least can't reproduce your problem. :(

--
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] #19423 [Applications/Tor Browser]: Tor Quit working!

[Tor Bug Tracker & Wiki]

#19423: Tor Quit working!
--+--
 Reporter:  dj1953|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  user disappeared
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_information => closed
 * resolution:   => user disappeared


--
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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Replying to [comment:18 karsten]:
 > [snip]
 >
 > The issue with `DescriptorCollector` returning `void` is that we cannot
 return any exceptions caught while fetching descriptor files from the
 remote CollecTor host to the caller.  This could be anything from fetching
 the `index.json` file or an actual descriptor file to differences between
 expected and actual file size or even indexing the local target directory.
 >
 > What we ''can'' do is log these exceptions/issues, so that the operator
 gets aware of them.  But we can't hand over exceptions to the application.
 At least not easily (see `ExceptionListener`).

 Well, throwing an Exception is a way to communicate problems to the
 caller.  Anyway, there are not that many distinguishable error situations;
 e.g. w/o index.json there is no descriptor downloading -> Exception.

 >
 > But if we can't pass exceptions while collecting descriptors to the
 application, why should we try hard to do this while reading descriptors?
 My point is that we can similarly log these warnings and don't have to
 start creating `InvalidDescriptor` just to let the application know about
 these exceptions.
 >
 > Regardless, we can pass parse exceptions encapsulated in
 `UnparseableDescriptor` to the application.  That's limited to
 `DescriptorReader` and `DescriptorParser`, because `DescriptorCollector`
 doesn't parse and return descriptors.

 I chose the name `InvalidDescriptor` in the beginning just to have a name;
 'unparsable' is a better prefix.  In general this type should be there to
 communicate that there is a descriptor that couldn't be parsed and provide
 all information accessible w/o proper parsing.  The exception itself is
 not (yet) of much use.

 >
 > Does this make more sense?

 I think our ideas/concepts converge :-)

 >
 > > > I also now understand your "ParseExceptionsLog" idea better.
 Basically, we would create a new structure for logging that is less
 dependent on classes and more related to operation.  Not opposed to that
 idea.  I could imagine that we'd want to look more at the other log
 statements and see what other channels would be useful.  How about we
 leave that for after 2.0.0 is released?
 > >
 > > Yes, that's fine or later.
 >
 > Okay!

 Added a comment to #16225 as reminder.

 >
 > > > Can you look at the branch?  I think it makes sense to look now.
 Thanks!
 > >
 > > I think UnparseableDescriptor should extend Descriptor otherwise there
 is no access to the raw bytes etc. from the API.
 > >
 > > * getDescriptorFile, getRawDescriptorBytes: should work in Un.Desc. as
 in other Descr.
 > > * getAnnotations, getUnrecognizedLines:  This behavior needs to be
 defined and documented in small tests.  (Annotations might be corrupt,
 unrecognized lines might not be identifiable etc.)
 >
 > Ugh, totally.  That's an oversight.  Fixed in a new commit in the same
 branch.
 >

 Taking a look at the update next.

 > > Other than these this looks ok as a 1.9.0 release solution.
 >
 > Awesome!  I'm also optimistic that this will work and that we won't run
 into too many yet unforseen issues.  I'll test this branch (with the
 `extends Descriptor` fix) in Onionoo and a few other applications.
 >
 > Thanks!

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

Re: [tor-bugs] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:  worksforme
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

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


Comment:

 Replying to [comment:40 WalrusInAnus]:
 > I thought we were finished (in part due to the other guy's nonsense
 comments here) and have since deleted the old profile and started anew.
 Sorry.

 No worries. If similar things come up again we'll know where to look I
 guess. :)

--
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] #16225 [Metrics/metrics-lib]: Unify exception/error handling in metrics-lib

[Tor Bug Tracker & Wiki]

#16225: Unify exception/error handling in metrics-lib
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_information
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Also consider different Loggers that enable sorting of log-statements via
 configuration. (see #22141#comment:15)

--
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] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+---
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by WalrusInAnus):

 I thought we were finished (in part due to the other guy's nonsense
 comments here) and have since deleted the old profile and started anew.
 Sorry.

--
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] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+---
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by gk):

 Replying to [comment:37 WalrusInAnus]:
 > Allright, done.

 Thanks. So, looking at your preferences file and on our previous issues it
 seems you might have been running into something we had fixed in
 #13610/#10761. Could you go to `about:preferences#privacy` in your broken
 Tor Browser and make sure to select the "Never remember history" option
 and do a restart. Do the crashes still occur afterwards?

--
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] #19640 [Metrics/metrics-lib]: review and improve interface hierarchy

[Tor Bug Tracker & Wiki]

#19640: review and improve interface hierarchy
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Thanks for the input!
 I'm trying to consider as many topics as possible while working on this
 with the aim to only introduce minimal changes that provide the most
 benefits.

--
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] #22553 [Applications/Tor Browser]: TOR 7 does not start on OS X 10.9.5

[Tor Bug Tracker & Wiki]

#22553: TOR 7 does not start on OS X 10.9.5
--+
 Reporter:  StefanK   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by StefanK):

 FYI, I just ran the in-app upgrade to 7.0.1 without problems.

--
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] #19423 [Applications/Tor Browser]: Tor Quit working!

[Tor Bug Tracker & Wiki]

#19423: Tor Quit working!
--+---
 Reporter:  dj1953|  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by cypherpunks):

 > Exception Code: c06d007f
 
https://trac.torproject.org/projects/tor/search?q=c06d007f=1=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] #22512 [Metrics/metrics-lib]: Add enums for keywords used in exit lists, Torperf measurement results, bridge pool assignments, and soon sanitized web logs

[Tor Bug Tracker & Wiki]

#22512: Add enums for keywords used in exit lists, Torperf measurement results,
bridge pool assignments, and soon sanitized web logs
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Works for me.  In any case, prefixing Tor keywords can be done really
 easily, and it only affects the implementation, not the interface.  If we
 ever decide to also prefix Tor keywords, we can just do it.

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

Re: [tor-bugs] #22603 [Applications/Tor Browser]: tor browser crashing on start up windows 10

[Tor Bug Tracker & Wiki]

#22603: tor browser crashing on start up windows 10
--+---
 Reporter:  No1   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by gk):

 * status:  new => needs_information


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

Re: [tor-bugs] #22603 [Applications/Tor Browser]: tor browser crashing on start up windows 10

[Tor Bug Tracker & Wiki]

#22603: tor browser crashing on start up windows 10
--+--
 Reporter:  No1   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Does it work if you install a clean new version into a different location
 (you get it from our website torproject.org)? Do you have Trusteer or a
 similar Antivirus/Firewall tool running?

--
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] #22603 [Applications/Tor Browser]: tor browser crashing on start up windows 10

[Tor Bug Tracker & Wiki]

#22603: tor browser crashing on start up windows 10
--+--
 Reporter:  No1   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 #19423

--
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] #19640 [Metrics/metrics-lib]: review and improve interface hierarchy

[Tor Bug Tracker & Wiki]

#19640: review and improve interface hierarchy
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 Hmm.  The use cases you describe make sense for adding such marker
 interfaces sound plausible.  But it also seems easy to introduce these
 interfaces and potentially difficult to deprecate and remove them if we
 don't want them anymore.  Should we wait with adding them until we need
 them?

--
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] #22603 [Applications/Tor Browser]: tor browser crashing on start up windows 10

[Tor Bug Tracker & Wiki]

#22603: tor browser crashing on start up windows 10
--+--
 Reporter:  No1   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Just don't use TorBrowser for Windows. Mingw were never ready to handle
 closed source proprietary operating system.

--
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] #22603 [Applications/Tor Browser]: tor browser crashing on start up windows 10

[Tor Bug Tracker & Wiki]

#22603: tor browser crashing on start up windows 10
--+--
 Reporter:  No1   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 i updated to 7.0.1, and since then tor crashes on start up due to firefox
 crash log attached

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

Re: [tor-bugs] #22512 [Metrics/metrics-lib]: Add enums for keywords used in exit lists, Torperf measurement results, bridge pool assignments, and soon sanitized web logs

[Tor Bug Tracker & Wiki]

#22512: Add enums for keywords used in exit lists, Torperf measurement results,
bridge pool assignments, and soon sanitized web logs
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Single letter is fine.
 As most Tor keywords are defined already and I assume there are more Tor
 related ones than non-Tor, I'd prefix non-Tor descriptors.  This would
 also accommodate non-Tor keywords from different data sources that
 overlap.

--
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] #19640 [Metrics/metrics-lib]: review and improve interface hierarchy

[Tor Bug Tracker & Wiki]

#19640: review and improve interface hierarchy
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Metrics-lib parses Tor protocol related descriptors and descriptors from
 other sources.  Shouldn't this distinction be reflected in the interface
 hierarchy?
 Have `Descriptor` on top and introduce an `ExternalDescriptor` interface
 for non-Tor protocol related data sources? Maybe, even have
 `TorDescriptor` too?
 {{{
   Descriptor
 /   \
 TorDescriptor ExternalDescriptor
 }}}


 This would provide more freedom when for example a switch to an external
 parsing framework (like ANTLR) is made for the Tor related descriptors.
 In addition, non-Tor descriptors could be modeled more easily to the soon
 to come Metrics-data standards and even have their own parsing/generator.

--
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] #22553 [Applications/Tor Browser]: TOR 7 does not start on OS X 10.9.5

[Tor Bug Tracker & Wiki]

#22553: TOR 7 does not start on OS X 10.9.5
--+
 Reporter:  StefanK   |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:  worksforme
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by gk):

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


Comment:

 No, that's fine, thanks for your help.

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

Re: [tor-bugs] #22512 [Metrics/metrics-lib]: Add enums for keywords used in exit lists, Torperf measurement results, bridge pool assignments, and soon sanitized web logs

[Tor Bug Tracker & Wiki]

#22512: Add enums for keywords used in exit lists, Torperf measurement results,
bridge pool assignments, and soon sanitized web logs
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by karsten):

 Ah, good point.  How about we add a single-letter source prefix as in
 `T_NETWORK_STATUS_VERSION("network-status-version")` where `T_` would
 stand for "'''T'''or descriptor"?

--
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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 Replying to [comment:17 iwakeh]:
 > Replying to [comment:16 karsten]:
 > > `DescriptorIndexCollector` indeed does not parse any descriptors, and
 neither did `DescriptorCollectorImpl`.  But I didn't refer to
 `DescriptorParseException` here.  We wouldn't be able to include other
 exceptions than `DescriptorParseException`, like `IOException`, in an
 output by `DescriptorIndexCollector`, because there's no output.  And that
 was the plan for `DescriptorReader`, where we were planning to include
 IOException in a returned `InvalidDescriptor`.  (The code may make this
 more obvious.)
 >
 > Hmm, maybe I forgot about something, but IOE rather belongs to a file
 than to a descriptor unless the two coincide.

 Sorry for not being clear.  Let me try to rephrase.

 The issue with `DescriptorCollector` returning `void` is that we cannot
 return any exceptions caught while fetching descriptor files from the
 remote CollecTor host to the caller.  This could be anything from fetching
 the `index.json` file or an actual descriptor file to differences between
 expected and actual file size or even indexing the local target directory.

 What we ''can'' do is log these exceptions/issues, so that the operator
 gets aware of them.  But we can't hand over exceptions to the application.
 At least not easily (see `ExceptionListener`).

 But if we can't pass exceptions while collecting descriptors to the
 application, why should we try hard to do this while reading descriptors?
 My point is that we can similarly log these warnings and don't have to
 start creating `InvalidDescriptor` just to let the application know about
 these exceptions.

 Regardless, we can pass parse exceptions encapsulated in
 `UnparseableDescriptor` to the application.  That's limited to
 `DescriptorReader` and `DescriptorParser`, because `DescriptorCollector`
 doesn't parse and return descriptors.

 Does this make more sense?

 > > I also now understand your "ParseExceptionsLog" idea better.
 Basically, we would create a new structure for logging that is less
 dependent on classes and more related to operation.  Not opposed to that
 idea.  I could imagine that we'd want to look more at the other log
 statements and see what other channels would be useful.  How about we
 leave that for after 2.0.0 is released?
 >
 > Yes, that's fine or later.

 Okay!

 > > Can you look at the branch?  I think it makes sense to look now.
 Thanks!
 >
 > I think UnparseableDescriptor should extend Descriptor otherwise there
 is no access to the raw bytes etc. from the API.
 >
 > * getDescriptorFile, getRawDescriptorBytes: should work in Un.Desc. as
 in other Descr.
 > * getAnnotations, getUnrecognizedLines:  This behavior needs to be
 defined and documented in small tests.  (Annotations might be corrupt,
 unrecognized lines might not be identifiable etc.)

 Ugh, totally.  That's an oversight.  Fixed in a new commit in the same
 branch.

 > Other than these this looks ok as a 1.9.0 release solution.

 Awesome!  I'm also optimistic that this will work and that we won't run
 into too many yet unforseen issues.  I'll test this branch (with the
 `extends Descriptor` fix) in Onionoo and a few other applications.

 Thanks!

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

Re: [tor-bugs] #22581 [Applications/Tor Browser]: Tor browser is crashing on exit on Windows

[Tor Bug Tracker & Wiki]

#22581: Tor browser is crashing on exit on Windows
--+---
 Reporter:  WalrusInAnus  |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-crash |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by cypherpunks):

 Just don't use TorBrowser for Windows. Firefox for Windows were never used
 for real after to be built with MinGW.

--
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] #22512 [Metrics/metrics-lib]: Add enums for keywords used in exit lists, Torperf measurement results, bridge pool assignments, and soon sanitized web logs

[Tor Bug Tracker & Wiki]

#22512: Add enums for keywords used in exit lists, Torperf measurement results,
bridge pool assignments, and soon sanitized web logs
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by iwakeh):

 Right, all descriptor parsing should make use of the `Key` keywords.

 Some things to consider:
 There is no inheritance between enums.  So, the ease of use in all
 descriptor parsing code would be lost with different Key-enums.  When
 using only the general `Enum` the `.keyword` and other features of
 `Key` are lost.
 This yields toward the "adding more Key enums approach" instead of
 separate Enums.

 There are no naming conventions yet (only implicitly).  The possible
 naming problems suppose certain rules which were not introduced directly.
 A working set of naming convention rules could be started with the aim of
 only using one `Key` enum.  If there are similar `Key` names as in the
 example above using 'source' a prefix could be added.  It should be ok to
 not have a strict translation rule from the actual keyword to the enum
 name; only keep it heuristically close.

--
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] #22553 [Applications/Tor Browser]: TOR 7 does not start on OS X 10.9.5

[Tor Bug Tracker & Wiki]

#22553: TOR 7 does not start on OS X 10.9.5
--+---
 Reporter:  StefanK   |  Owner:  tbb-team
 Type:  defect| Status:  needs_information
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by StefanK):

 1) Yes, TorBrowser 7 is working now

 2) Regarding reproducing the issue, this would mean completely erasing all
 traces of TorBrowser from OS X, installing 6.5.2 and then doing an in-app
 update to 7.0. This procedure was not covered in the above troubleshooting
 steps, and I'd rather not do that unless it is absolutely 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] #22575 [Internal Services/Service - lists]: password reset for mailing lists doesn't send e-mails

[Tor Bug Tracker & Wiki]

#22575: password reset for mailing lists doesn't send e-mails
---+-
 Reporter:  iwakeh |  Owner:  qbi
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by iwakeh):

 Hmm, is this a feature?  global-south and metrics-bugs mail passwd
 reminders, but metrics-team doesn't.

--
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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Replying to [comment:16 karsten]:
 > `DescriptorIndexCollector` indeed does not parse any descriptors, and
 neither did `DescriptorCollectorImpl`.  But I didn't refer to
 `DescriptorParseException` here.  We wouldn't be able to include other
 exceptions than `DescriptorParseException`, like `IOException`, in an
 output by `DescriptorIndexCollector`, because there's no output.  And that
 was the plan for `DescriptorReader`, where we were planning to include
 IOException in a returned `InvalidDescriptor`.  (The code may make this
 more obvious.)

 Hmm, maybe I forgot about something, but IOE rather belongs to a file than
 to a descriptor unless the two coincide.

 >
 > I also now understand your "ParseExceptionsLog" idea better.  Basically,
 we would create a new structure for logging that is less dependent on
 classes and more related to operation.  Not opposed to that idea.  I could
 imagine that we'd want to look more at the other log statements and see
 what other channels would be useful.  How about we leave that for after
 2.0.0 is released?

 Yes, that's fine or later.

 >
 > Can you look at the branch?  I think it makes sense to look now.
 Thanks!

 I think UnparseableDescriptor should extend Descriptor otherwise there is
 no access to the raw bytes etc. from the API.

 * getDescriptorFile, getRawDescriptorBytes: should work in Un.Desc. as in
 other Descr.
 * getAnnotations, getUnrecognizedLines:  This behavior needs to be defined
 and documented in small tests.  (Annotations might be corrupt,
 unrecognized lines might not be identifiable etc.)

 Other than these this looks ok as a 1.9.0 release solution.

--
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] #22601 [Internal Services/Tor Sysadmin Team]: Please set up Apache on corsicum

[Tor Bug Tracker & Wiki]

#22601: Please set up Apache on corsicum
-+
 Reporter:  karsten  |  Owner:  tpa
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by weasel):

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


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

Re: [tor-bugs] #17861 [Metrics/metrics-lib]: Consider adding a new interface RelayNetworkStatusMicrodescConsensus

[Tor Bug Tracker & Wiki]

#17861: Consider adding a new interface RelayNetworkStatusMicrodescConsensus
-+---
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Low  |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * status:  new => accepted
 * owner:  karsten => iwakeh


Comment:

 Taking this on together with #19640.

--
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] #17342 [Webpages/Website]: Update hidden service website page with Unix socket info

[Tor Bug Tracker & Wiki]

#17342: Update hidden service website page with Unix socket info
--+--
 Reporter:  dgoulet   |  Owner:  hiro
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by hiro):

 * owner:  cypherpunks => hiro
 * severity:   => Normal


--
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] #22602 [Metrics/CollecTor]: CollecTor's relaydescs module freezes while downloading from directory authorities

[Tor Bug Tracker & Wiki]

#22602: CollecTor's relaydescs module freezes while downloading from directory
authorities
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by karsten):

 Oh well.  I didn't look yet.  Yet one more reason to finally fix 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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by karsten):

 `DescriptorIndexCollector` indeed does not parse any descriptors, and
 neither did `DescriptorCollectorImpl`.  But I didn't refer to
 `DescriptorParseException` here.  We wouldn't be able to include other
 exceptions than `DescriptorParseException`, like `IOException`, in an
 output by `DescriptorIndexCollector`, because there's no output.  And that
 was the plan for `DescriptorReader`, where we were planning to include
 IOException in a returned `InvalidDescriptor`.  (The code may make this
 more obvious.)

 I also now understand your "ParseExceptionsLog" idea better.  Basically,
 we would create a new structure for logging that is less dependent on
 classes and more related to operation.  Not opposed to that idea.  I could
 imagine that we'd want to look more at the other log statements and see
 what other channels would be useful.  How about we leave that for after
 2.0.0 is released?

 Can you look at the branch?  I think it makes sense to look now.  Thanks!

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

Re: [tor-bugs] #22602 [Metrics/CollecTor]: CollecTor's relaydescs module freezes while downloading from directory authorities

[Tor Bug Tracker & Wiki]

#22602: CollecTor's relaydescs module freezes while downloading from directory
authorities
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 Analysis in #20323.

--
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] #22602 [Metrics/CollecTor]: CollecTor's relaydescs module freezes while downloading from directory authorities

[Tor Bug Tracker & Wiki]

#22602: CollecTor's relaydescs module freezes while downloading from directory
authorities
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by iwakeh):

 I assume this is the `HttpURLConnection` problem we already have in
 several tickets (#20516, #20515, 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] #22141 [Metrics/metrics-lib]: Deprecate `DescriptorFile` and add relevant information to `Descriptor`

[Tor Bug Tracker & Wiki]

#22141: Deprecate `DescriptorFile` and add relevant information to `Descriptor`
-+---
 Reporter:  karsten  |  Owner:  karsten
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 1.9.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 Replying to [comment:13 karsten]:
 > I'm afraid I found two flaws in the design above and the suggestion on
 #22196:
 >
 >  1. We're using the `Iterable` and `InvalidDescriptor` as
 one possible returned element as channel for all kinds of exceptions
 thrown while reading descriptor files.  But we don't have such a channel
 in `DescriptorCollector#collectDescriptors` which returns, well, `void`.
 That means that the design above doesn't solve anything of
 [https://trac.torproject.org/projects/tor/ticket/16225#comment:7 this
 issue raised on the related ticket #16225].  And ideally we'd handle
 exceptions in the same way in all descriptor sources.

 `DescriptorCollectorImpl` is deprecated:
 {{{
 * @deprecated Replaced by {@link DescriptorIndexCollector} which uses the
  * remote instance's index.json file as a more robust alternative to
 parsing
  * the remote instance's directory listings.
 }}}

 Using the `DescriptorIndexCollector` implementation no descriptors are
 parsed during download.
 What did I overlook?

 >  1. The idea of replacing the parse history with a `minLastModified`
 timestamp doesn't handle I/O problems very well.  For example, in the
 current implementation, if there's a network problem with downloading a
 potentially large file from CollecTor, we would not include that in the
 parse history and retry collecting and reading it next time.  But with
 only a timestamp we would simply skip that descriptor file, which is
 pretty bad.
 >
 > New plan:
 >  - We rename `InvalidDescriptor` to `UnparseableDescriptor` and let it
 return the `DescriptorParseException` that made it unparseable in our
 view.  This instance ''might'' be useful to the application, at least by
 containing the raw descriptor `byte[]` or descriptor `File` reference.
 And if the application produced the input descriptor itself, like
 CollecTor, knowing about it being unparseable is more important than for a
 consumer, like Onionoo!

 I assumed that InvalidDescriptor would provide the bytes and other
 descriptor meta-data, the renaming makes sense.

 >  - We leave the parse history in place and postpone the idea of
 stateless, overloaded methods.  Sad.

 Not so sad, actually.  From an API point of view hiding away the history
 bookkeeping reduces complexity.

 >  - We add a method `removeFromHistoryFile(File)` that can be called by
 the application if it wants to reprocess a descriptor file containing an
 `UnparseableDescriptor`.  This would not be necessary for I/O exceptions,
 because those descriptor files would not go into the parse history and
 retried in the next execution anyway.
 >  - We log any exceptions on `warn` level that we caught while collecting
 or reading or parsing descriptors.  The application can't ''do'' anything
 to handle these issues anyway, except for telling the operator that
 something went wrong.  `DescriptorParseException`s thrown while parsing
 invalid/unparseable descriptors are exempt from this and will only be
 logged on info level.

 I think INFO logging to the regular log could bloat logs unnecessarily;
 more below.

 >  - We ''could'' introduce an `ExceptionListener` for exceptions are than
 `DescriptorParseException`, or the "ParseExceptionsLog" that you mentioned
 (even though I'm not entirely certain what that would be).  I don't think
 it's necessary though, because we wouldn't it use that ourselves, and we
 don't know whether it would be used by anyone.

 I think an exception listener is not really necessary.  The 'logging
 channel' suggestion was meant as introducing another Logger as for example
 is used in Onionoo for statistics:
 `LoggerFactory.getLogger("statistics")...`.
 Such a `LoggerFactory.getLogger("ParseExceptionsLog")` for all parsing
 problems would 'channel' these log statements and the final receiver (be
 it log or /dev/null) can be changed via runtime configuration.
 Does that make sense?


 >
 > Before I write more code (or longer comments!), what do you think? :)

 I didn't look at the branch below, yet.  Should I now?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list

Re: [tor-bugs] #22597 [Internal Services/Tor Sysadmin Team]: Please make an LDAP account for Chelsea

[Tor Bug Tracker & Wiki]

#22597: Please make an LDAP account for Chelsea
-+-
 Reporter:  isis |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by weasel):

 Chelsea might want to have a key that doesn't expire in less than 4 weeks
 time.

--
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] #22601 [Internal Services/Tor Sysadmin Team]: Please set up Apache on corsicum

[Tor Bug Tracker & Wiki]

#22601: Please set up Apache on corsicum
-+-
 Reporter:  karsten  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by karsten):

 Okay, in that case let's use collector2.

--
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] #22596 [Internal Services/Tor Sysadmin Team]: please update iwakeh's gpg (sub)key

[Tor Bug Tracker & Wiki]

#22596: please update iwakeh's gpg (sub)key
-+
 Reporter:  iwakeh   |  Owner:  tpa
 Type:  task | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by weasel):

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


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

[tor-bugs] #22602 [Metrics/CollecTor]: CollecTor's relaydescs module freezes while downloading from directory authorities

[Tor Bug Tracker & Wiki]

#22602: CollecTor's relaydescs module freezes while downloading from directory
authorities
---+--
 Reporter:  karsten|  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  High   |  Milestone:
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+--
 This morning, 2017-06-14 ~07:00, I noticed that the latest consensus
 retrieved by CollecTor was valid after 2017-06-13 17:00.

 The last log lines from the relaydescs module were:

 {{{
 2017-06-13 17:05:00,001 INFO o.t.c.c.CollecTorMain:66 Starting relaydescs
 module of CollecTor.
 2017-06-13 17:05:26,184 INFO o.t.c.r.CachedRelayDescriptorReader:255
 Finished importing relay descriptors from local Tor data directories:
 cached-consensus: 2017-06-13 17:00:00
 cached-descriptors: parsed 0, skipped 24560 server descriptors
 cached-descriptors.new: parsed 608, skipped 8585 server descriptors
 cached-extrainfo: parsed 0, skipped 24543 extra-info descriptors
 cached-extrainfo.new: parsed 607, skipped 8239 extra-info descriptors
 v3-status-votes: parsed 8, skipped 0 votes
 }}}

 All other modules continued as usual.

 Here's a stack trace obtained using `jcmd`:

 {{{
 "CollecTor-Scheduled-Thread-8" daemon prio=10 tid=0x7fedd8006800
 nid=0x6411 runnable [0x7fee023fd000]
java.lang.Thread.State: RUNNABLE
 at java.net.SocketInputStream.socketRead0(Native Method)
 at java.net.SocketInputStream.read(SocketInputStream.java:153)
 at java.net.SocketInputStream.read(SocketInputStream.java:122)
 at java.io.BufferedInputStream.fill(BufferedInputStream.java:235)
 at java.io.BufferedInputStream.read1(BufferedInputStream.java:275)
 at java.io.BufferedInputStream.read(BufferedInputStream.java:334)
 - locked <0x00078fd3b3d8> (a java.io.BufferedInputStream)
 at
 sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:707)
 at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:650)
 at
 
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1371)
 - locked <0x00078fd3b418> (a
 sun.net.www.protocol.http.HttpURLConnection)
 at
 java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:468)
 at
 
org.torproject.collector.relaydescs.RelayDescriptorDownloader.downloadResourceFromAuthority(RelayDescriptorDownloader.java:869)
 at
 
org.torproject.collector.relaydescs.RelayDescriptorDownloader.downloadDescriptors(RelayDescriptorDownloader.java:817)
 at
 
org.torproject.collector.relaydescs.ArchiveWriter.startProcessing(ArchiveWriter.java:176)
 at
 org.torproject.collector.cron.CollecTorMain.run(CollecTorMain.java:67)
 at
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:473)
 at
 java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
 at
 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
 at
 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
 at
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
 at
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
 at java.lang.Thread.run(Thread.java:745)
 }}}

 I stopped and restarted CollecTor and am now working on filling the gap of
 relay descriptors published in these ~16 hours by syncing from the backup
 instance.

 I guess the fix is to start using a timeout somewhere.  It's just curious
 that we didn't run into this case before.  We didn't change anything there
 recently, did we?

--
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] #22601 [Internal Services/Tor Sysadmin Team]: Please set up Apache on corsicum

[Tor Bug Tracker & Wiki]

#22601: Please set up Apache on corsicum
-+-
 Reporter:  karsten  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by weasel):

 corsicum is the hostname.  it's not the service name so it shouldn't be in
 an URL.  collector2 would work.

--
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] #22593 [Webpages/Website]: Minify HTML, CSS and JavaScript resources on all websites of the torproject.org to save a bit of bandwidth

[Tor Bug Tracker & Wiki]

#22593: Minify HTML, CSS and JavaScript resources on all websites of the
torproject.org to save a bit of bandwidth
--+---
 Reporter:  cypherpunks   |  Owner:  linda
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by weasel):

 * owner:  tpa => linda
 * component:  Internal Services/Tor Sysadmin Team => Webpages/Website


--
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] #22596 [Internal Services/Tor Sysadmin Team]: please update iwakeh's gpg (sub)key

[Tor Bug Tracker & Wiki]

#22596: please update iwakeh's gpg (sub)key
-+-
 Reporter:  iwakeh   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by karsten):

 Not sure if this speeds up the request, but I can confirm that iwakeh
 controls the key above.

--
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] #22576 [Obfuscation/Obfsproxy]: obfs4 through proxy is not working anymore with Tor Browser 7.0 on Windows

[Tor Bug Tracker & Wiki]

#22576: obfs4 through proxy is not working anymore with Tor Browser 7.0 on 
Windows
---+-
 Reporter:  albesp77   |  Owner:
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Obfuscation/Obfsproxy  |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-7.0-issues |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by albesp77):

 my squid.conf that works with old obfs4proxy and not with new one:

 acl localnet src 10.0.0.0/8
 acl localnet src 172.16.0.0/12
 acl localnet src 192.168.0.0/16
 acl localnet src fc00::/7
 acl localnet src fe80::/10
 acl SSL_ports port 443
 acl Safe_ports port 80
 acl Safe_ports port 21
 acl Safe_ports port 443
 acl Safe_ports port 70
 acl Safe_ports port 210
 acl Safe_ports port 1025-65535
 acl Safe_ports port 280
 acl Safe_ports port 488
 acl Safe_ports port 591
 acl Safe_ports port 777
 acl CONNECT method CONNECT
 http_access deny !Safe_ports
 http_access deny CONNECT !SSL_ports
 http_access allow localhost manager
 http_access deny manager
 http_access allow localnet
 http_access allow localhost
 http_access deny all
 always_direct allow all
 ssl_bump splice all
 ssl_bump bump all
 ssl_bump peek all
 ssl_bump splice all
 http_port 3128
 https_port 3130 transparent ssl-bump generate-host-certificates=on
 dynamic_cert_mem_cache_size=4MB cert=/usr/local/squid/ssl_cert/myCA.pem
 sslcrtd_program /usr/local/squid/libexec/ssl_crtd -s
 /usr/local/squid/var/lib/ssl_db -M 4MB
 sslcrtd_children 5

 if you need me for test write here test detail, thanks!

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

[tor-bugs] #22601 [Internal Services/Tor Sysadmin Team]: Please set up Apache on corsicum

[Tor Bug Tracker & Wiki]

#22601: Please set up Apache on corsicum
-+-
 Reporter:  karsten  |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 Please set up Apache on corsicum and make it available under
 https://corsicum.torproject.org/.

 (I briefly thought about also adding a DNS entry like collector-
 backup.torproject.org or collector2.torproject.org, but we can as well
 just use corsicum.torproject.org.  In fact, that's probably the better
 option, because we might want to add a third host in the future.  But not
 yet.)

 Thanks!

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