[tor-bugs] #23049 [Applications/Tor Browser]: Tor Fails to open

[Tor Bug Tracker & Wiki]

#23049: Tor Fails to open
--+--
 Reporter:  jmaldonado12  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 I had Tor browser up and running fine. After shutting down my computer and
 turning it on at a later time, tor stopped working. Whenever I tried
 opening it i get the message: Tor exited during startup. This might be due
 to an error in your torrc file, a bug in Tor or another program on your
 system, or faulty hardware. Until you fix the underlying problem and
 restart Tor, Tor Browser will not start.
 I completely uninstalled the application and reinstalling it only to get
 the same message every time i try to open the browser.
 I was downloading version 7.0.2

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23048 [Webpages/Website]: Update Debian and Ubuntu instructions for systemd

[Tor Bug Tracker & Wiki]

#23048: Update Debian and Ubuntu instructions for systemd
--+-
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+-
 Relay operators are confused by the old instructions:

 https://lists.torproject.org/pipermail/tor-relays/2017-July/012658.html

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

Re: [tor-bugs] #19509 [Applications/Tor Browser]: Authenticating to tor (stays permanent)

[Tor Bug Tracker & Wiki]

#19509: Authenticating to tor (stays permanent)
--+---
 Reporter:  chexo.shivam  |  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 Dbryrtfbcbhgf):

 * status:  new => needs_information
 * priority:  Immediate => Medium
 * severity:  Critical => 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] #17639 [Core Tor/Tor]: provide an option to display the expiry date of a given ed25519 signing key

[Tor Bug Tracker & Wiki]

#17639: provide an option to display the expiry date of a given ed25519 signing 
key
+--
 Reporter:  cypherpunks |  Owner:  isis
 Type:  enhancement | Status:
|  needs_revision
 Priority:  High|  Milestone:  Tor:
|  0.3.2.x-final
Component:  Core Tor/Tor|Version:  Tor:
|  0.2.7.2-alpha
 Severity:  Normal  | Resolution:
 Keywords:  tor-ed25519-proto, review-group-21  |  Actual Points:
Parent ID:  | Points:  1
 Reviewer:  nickm   |Sponsor:
+--

Comment (by isis):

 Replying to [comment:26 nickm]:
 > I vote for something like
 > {{{
 > signing-cert-expiry: 2017-07-25 08:30:15 UTC
 > }}}
 > for the output format, and document that you need to grep for the
 signing-cert-expiry.
 >
 > I guess that's probably enough, plus the manpage.  What do you think?

 Sounds good! This fits in well with the `char *description` for certs, so
 we should be able to expand this output format easily in the future for
 other/new types of certs.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23044 [Applications/Tor Browser]: Don't allow GIO supported protocols by default (was: Replace stdole2.tlb with our own during build time)

[Tor Bug Tracker & Wiki]

#23044: Don't allow GIO supported protocols by default
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Blocker   | Resolution:  fixed
 Keywords:  tbb-proxy-bypass  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  new => closed
 * priority:  Medium => Immediate
 * keywords:  tbb-gitian => tbb-proxy-bypass
 * resolution:   => fixed
 * severity:  Normal => Blocker


Old description:

> The mingw-w64 repo contains the binary `stdole2.tlb` which is needed for
> building Tor Browser (see: 17e09279acf8b7f44d731c9a65541a474af4f1b5). It
> turns out we can do better than relying on that binary blob and create
> that typelib during build time.

New description:

 Firefox allows passing URLs along to the OS (by a whitelist) which is
 dangerous. We should avoid that.

--

Comment:

 Fixes pushed to `tor-browser-52.2.0esr-7.5-1` (commit
 a96f898e0da42de751a5e1367a9899cc96fadb1f) and `tor-
 browser-52.2.0esr-7.0-1` (commit
 720f9061496321aa978d2f022113c40e9aeb4847). They will show up in the next
 releases, 7.0.3 and 7.5a3.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23045 [Applications/Tor Browser]: Replace *.tlb with our own during build time (was: Replace oleacc.tlb with our own during build time)

[Tor Bug Tracker & Wiki]

#23045: Replace *.tlb with our own during build time
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-gitian|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Description changed by gk:

Old description:

> mingw-w64 contains `oleacc.tlb` (see
> 7c90d5921bd2cb678eec09d05b10ce6fd13463bc) which is a binary blob needed
> for compiling Tor Browser. We can do better and get rid of the one in the
> repo and build it ourselves.

New description:

 mingw-w64 contains `oleacc.tlb` (see
 7c90d5921bd2cb678eec09d05b10ce6fd13463bc) and `stdole2.tlb` (see
 17e09279acf8b7f44d731c9a65541a474af4f1b5) which are binary blobs needed
 for compiling Tor Browser. We can do better, though, and get rid of the
 ones in the repo and build them ourselves.

--

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22865 [Obfuscation/meek]: Explicitly set Content-Length to zero when there is no data to send

[Tor Bug Tracker & Wiki]

#22865: Explicitly set Content-Length to zero when there is no data to send
--+
 Reporter:  twim  |  Owner:  dcf
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by twim):

 This is just awesome, thanks for your extensive digging into net/http
 internals!
 It turns out to be much more complicated - hiding complexity isn't easy.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22883 [Core Tor/Tor]: Bridge unavailable during differential consensus update

[Tor Bug Tracker & Wiki]

#22883: Bridge unavailable during differential consensus update
-+-
 Reporter:  torvlnt33r   |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.4-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  regression, cpu, usage, review-  |  Actual Points:  1
  group-21   |
Parent ID:   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by nickm):

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


Comment:

 Squashed and merged to 0.3.1 and forward. Let's see if anything explodes.
 ;)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22883 [Core Tor/Tor]: Bridge unavailable during differential consensus update

[Tor Bug Tracker & Wiki]

#22883: Bridge unavailable during differential consensus update
-+-
 Reporter:  torvlnt33r   |  Owner:  nickm
 Type:  defect   | Status:
 |  merge_ready
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.4-alpha
 Severity:  Normal   | Resolution:
 Keywords:  regression, cpu, usage, review-  |  Actual Points:  1
  group-21   |
Parent ID:   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => merge_ready


Comment:

 lgtm;!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22883 [Core Tor/Tor]: Bridge unavailable during differential consensus update

[Tor Bug Tracker & Wiki]

#22883: Bridge unavailable during differential consensus update
-+-
 Reporter:  torvlnt33r   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.4-alpha
 Severity:  Normal   | Resolution:
 Keywords:  regression, cpu, usage, review-  |  Actual Points:  1
  group-21   |
Parent ID:   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by nickm):

 * status:  needs_revision => needs_review


Comment:

 ok, thanks!  I've pushed some updates, if you have time to take a quick
 look.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23047 [Internal Services/Tor Sysadmin Team]: Please add iwakeh to the onionoo, metrics, and exonerator groups

[Tor Bug Tracker & Wiki]

#23047: Please add iwakeh to the onionoo, metrics, and exonerator groups
-+-
 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:   |
-+-
 {{{
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA256

 Please add iwakeh to the onionoo, metrics, and exonerator groups, so
 that they can log in to the respective hosts providing these services.
 Thanks!
 -BEGIN PGP SIGNATURE-
 Comment: GPGTools - http://gpgtools.org

 iQEcBAEBCAAGBQJZeiloAAoJEO85p7J7H00B7GUH/iy0J9LUS7Z3XRViC5ATZufo
 5bYHa+AcTIqyWqb8nuHJDBr/NPwkIpmuT4BI6eCUFiS5xJB4jvfvALxbtPoVdcRK
 Bo6ivxKK8YbrLiCSJ7lB2X2/HsK+77tOYwyV0egUmLZmE678QcuINIcWXph70zlC
 zsjVBJTWJNqYpSoyPVMQCbzM432cJpxtz+HS3QSWMPImeH7f7XzZF67LkLKT1nS6
 AuIBAGnJ+3ImL9VBK8gHFKxrdDWZ9nJ0Plh/tRzG5vI+JRcR8pb4Oq8ILuWd1qrP
 qEhUbcDmiRXhUmVq1lHbRQibkTh9ZsKAY4zW96LmYnpaISIJ6/GknPylpKcWyxw=
 =7KqA
 -END PGP SIGNATURE-
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22827 [Core Tor/Tor]: Formalise CollecTor spec for sanitised bridge descriptors and put in torspec

[Tor Bug Tracker & Wiki]

#22827: Formalise CollecTor spec for sanitised bridge descriptors and put in
torspec
-+-
 Reporter:  isis |  Owner:  karsten
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-docs, tor-bridges  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by iwakeh):

 Replying to [comment:12 karsten]:
 > Replying to [comment:11 iwakeh]:
 > > Looks fine!
 > >
 > > Maybe keep the comment section small by removing all resolved
 comments,
 >
 > Ah, yes. In fact, I thought we'd remove the entire WIP section and the
 build instructions before publishing.

 The instructions could be turned into a comment in the xml, if the xslt-
 processing doesn't complain.

 >
 > > like c00, c00a, c01,c01a (actually the entire xslt discussion), c07,
 c07a.
 >
 > Yep, they can all go away.
 >
 > > c03 could be replaced by a remark that ANTLR is too much overhead
 for the moment.
 >
 > Yep, good idea.
 >
 > > Regarding c02, c02a:  There is no list of references in the new html.
 If that resolves the issue, it could also be removed.
 >
 > Works for me.
 >
 > > Minor format issue/nitpick:
 > > I don't find the choice of `[:n]` very intuitive as operator (and also
 applying it from the right.  Maybe just use a function notation, e.g.,
 `Bn`.  For example:
 > > `KeyedHash = SHA256(Ipv4Address | Fingerprint | Secret)[:3]` could
 become
 > > `KeyedHash = B3(SHA256(Ipv4Address | Fingerprint | Secret))`.
 >
 > This notation is being used in other Tor specification documents. That's
 why I'd rather not touch it without suggesting a more formal and hopefully
 at the same time more intuitive notation for the remaining specification
 parts. Do you mind if we keep this unchanged for now?

 I don't insist on the change.

 >
 > > Shouldn't the additional xslt and awk files used for generating html
 be also added to git?
 >
 > Yes. I just wasn't sure whether this will be the final place for putting
 the specification file, so I only checked in the source file. But they can
 certainly go into the repo.
 >
 > How do we proceed (assuming we can resolve the remaining parts above)?
 How would we include the generated HTML in the Tor Metrics website? Do we
 edit the XSLT template for that, or do we write a shell script for this
 that rips out the pieces of the generated HTML file that we want, or what?

 We found a place for the page (cf. team meeting).
 I think it would be best to adapt the XSLT.  That would complete the task
 in one processing step.
 Maybe, first define the target page (incl. colors etc.) and then give it a
 try with XSLT?
 shell scripting should be last resort.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22983 [Metrics/metrics-lib]: add a descriptor interface and implementation for web-logs

[Tor Bug Tracker & Wiki]

#22983: add a descriptor interface and implementation for web-logs
-+---
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 2.1.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---

Comment (by iwakeh):

 The new ticket for LogLine implementation is #23046.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23046 [Metrics/metrics-lib]: Add sub-interface LogDescriptor.LogLine (and the extension to WebServerAccessLogLine)

[Tor Bug Tracker & Wiki]

#23046: Add sub-interface LogDescriptor.LogLine (and the extension to
WebServerAccessLogLine)
-+--
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   |   Keywords:
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+--
 Add sub-interface LogDescriptor.LogLine (and the extension to
 WebServerAccessLogLine), the first interface will simply provide one
 method that returns a line from the log.

 LogDescriptor will need to be extended to provide all LogLines, which
 includes sub-interface specific parsing and retrieving the unrecognized
 lines up to a limit (100 for a start).

 Sub-interface WebServerAccessLogLine, which extends LogLine, is more
 specific for access-logs and provides methods for all fields that contain
 useful data after the sanitation process, i.e., it doesn't provide all
 Apache log fields.
 (cf. discussion in #22983)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23041 [Webpages/Website]: Add new press clips to website

[Tor Bug Tracker & Wiki]

#23041: Add new press clips to website
--+-
 Reporter:  steph |  Owner:
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-

Comment (by hiro):

 I do not understand the date format. Could you please clarify 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] #23040 [Webpages/Website]: job post for tor browser mobile (android)

[Tor Bug Tracker & Wiki]

#23040: job post for tor browser mobile (android)
--+
 Reporter:  isabela   |  Owner:
 Type:  defect| Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by hiro):

 * status:  new => needs_revision


Comment:

 This is going live now. Please close if you think everything is fine w/
 the page.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23042 [Internal Services/Service - lists]: emails to the wtf@ email list are bouncing

[Tor Bug Tracker & Wiki]

#23042: emails to the wtf@ email list are bouncing
---+
 Reporter:  t0mmy  |  Owner:  qbi
 Type:  defect | Status:  closed
 Priority:  High   |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:  fixed
 Keywords:  wtf|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by t0mmy):

 * 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] #22895 [Core Tor/Tor]: Unused variables in donna's SSE2 header

[Tor Bug Tracker & Wiki]

#22895: Unused variables in donna's SSE2 header
-+-
 Reporter:  cypherpunks  |  Owner:
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  027-backport, 028-backport,  |  Actual Points:
  029-backport, 030-backport, 031-backport,  |
  compile, warning, 32bit, ed25519, review-  |
  group-21   |
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:
-+-

Comment (by nickm):

 The branch to backport is `bug22895_027`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22895 [Core Tor/Tor]: Unused variables in donna's SSE2 header

[Tor Bug Tracker & Wiki]

#22895: Unused variables in donna's SSE2 header
-+-
 Reporter:  cypherpunks  |  Owner:
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  027-backport, 028-backport,  |  Actual Points:
  029-backport, 030-backport, 031-backport,  |
  compile, warning, 32bit, ed25519, review-  |
  group-21   |
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.3.1.x-final


Comment:

 In that case, I think it's fine to take this in 0.3.2, and consider for a
 possible backport. 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] #22895 [Core Tor/Tor]: Unused variables in donna's SSE2 header

[Tor Bug Tracker & Wiki]

#22895: Unused variables in donna's SSE2 header
-+-
 Reporter:  cypherpunks  |  Owner:
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.7.2-alpha
 Severity:  Normal   | Resolution:
 Keywords:  027-backport, 028-backport,  |  Actual Points:
  029-backport, 030-backport, 031-backport,  |
  compile, warning, 32bit, ed25519, review-  |
  group-21   |
Parent ID:   | Points:
 Reviewer:  asn  |Sponsor:
-+-
Changes (by asn):

 * status:  needs_review => merge_ready


Comment:

 Thanks for the help Nick. I managed to compile Tor in 32-bit mode:

 {{{
 $ file src/or/tor
 src/or/tor: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV),
 dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.32,
 BuildID[sha1]=72f975f78f2ef98852368ebbe3a6205ddf0ea944, not stripped
 }}}

 I still have not managed to trigger this error unfortunately, even tho I
 compiled tor with `$ CFLAGS="-m32" ./configure --enable-gcc-warnings
 --disable-asciidoc --enable-expensive-hardening` and I checked that
 `src/ext/ed25519/donna/libed25519_donna.a` was built...

 Not sure what to do here. Anyone has tips on how to repro this?

 Otherwise, I just say we merge the patch since it just removes unused
 variables anyway (I checked all of 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] #22883 [Core Tor/Tor]: Bridge unavailable during differential consensus update

[Tor Bug Tracker & Wiki]

#22883: Bridge unavailable during differential consensus update
-+-
 Reporter:  torvlnt33r   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_revision
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.4-alpha
 Severity:  Normal   | Resolution:
 Keywords:  regression, cpu, usage, review-  |  Actual Points:  1
  group-21   |
Parent ID:   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by dgoulet):

 * status:  needs_review => needs_revision


Comment:

 I've gone over, afaict, it's good. Small typo and doc issues. Putting it
 back in needs_revision because there are typos that need to be fixed.
 After that, imo it can be merged. I'll run that on my relay as soon as it
 is upstream.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22990 [Metrics/metrics-lib]: Add a heartbeat log message indicating progress and estimated time left

[Tor Bug Tracker & Wiki]

#22990: Add a heartbeat log message indicating progress and estimated time left
-+--
 Reporter:  karsten  |  Owner:  iwakeh
 Type:  enhancement  | Status:  accepted
 Priority:  Medium   |  Milestone:
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * owner:  metrics-team => iwakeh
 * status:  new => accepted


Comment:

 Why not continue now as I started thinking about 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] #22827 [Core Tor/Tor]: Formalise CollecTor spec for sanitised bridge descriptors and put in torspec

[Tor Bug Tracker & Wiki]

#22827: Formalise CollecTor spec for sanitised bridge descriptors and put in
torspec
-+-
 Reporter:  isis |  Owner:  karsten
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-docs, tor-bridges  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by karsten):

 Replying to [comment:11 iwakeh]:
 > Looks fine!
 >
 > Maybe keep the comment section small by removing all resolved comments,

 Ah, yes. In fact, I thought we'd remove the entire WIP section and the
 build instructions before publishing.

 > like c00, c00a, c01,c01a (actually the entire xslt discussion), c07,
 c07a.

 Yep, they can all go away.

 > c03 could be replaced by a remark that ANTLR is too much overhead
 for the moment.

 Yep, good idea.

 > Regarding c02, c02a:  There is no list of references in the new html.
 If that resolves the issue, it could also be removed.

 Works for me.

 > Minor format issue/nitpick:
 > I don't find the choice of `[:n]` very intuitive as operator (and also
 applying it from the right.  Maybe just use a function notation, e.g.,
 `Bn`.  For example:
 > `KeyedHash = SHA256(Ipv4Address | Fingerprint | Secret)[:3]` could
 become
 > `KeyedHash = B3(SHA256(Ipv4Address | Fingerprint | Secret))`.

 This notation is being used in other Tor specification documents. That's
 why I'd rather not touch it without suggesting a more formal and hopefully
 at the same time more intuitive notation for the remaining specification
 parts. Do you mind if we keep this unchanged for now?

 > Shouldn't the additional xslt and awk files used for generating html be
 also added to git?

 Yes. I just wasn't sure whether this will be the final place for putting
 the specification file, so I only checked in the source file. But they can
 certainly go into the repo.

 How do we proceed (assuming we can resolve the remaining parts above)? How
 would we include the generated HTML in the Tor Metrics website? Do we edit
 the XSLT template for that, or do we write a shell script for this that
 rips out the pieces of the generated HTML file that we want, or what?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22288 [Metrics/Metrics website]: Use newly recognized OnionPerf keys

[Tor Bug Tracker & Wiki]

#22288: Use newly recognized OnionPerf keys
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  closed
 Priority:  High |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by karsten):

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


Comment:

 Thanks for looking! Rebased and pushed to master. Will deploy later today
 or tomorrow. Closing.

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

Re: [tor-bugs] #19479 [Applications/Tor Browser]: Document.timeline.currentTime leaks ms-resolution clock in Firefox >=48

[Tor Bug Tracker & Wiki]

#19479: Document.timeline.currentTime leaks ms-resolution clock in Firefox >=48
--+--
 Reporter:  arthuredelstein   |  Owner:  rah
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff59-esr, tbb-fingerprinting  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Replying to [comment:7 rah]:
 > I'm wondering whether there is a simple switch to activate this
 functionality in the tor-browser branch?  Or is it a matter of the code
 not being there yet?

 I think you should have access to `document.timeline` if you switched `dom
 .animations-api.core.enabled` to `true`. At least for me it was available
 to content then 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] #22990 [Metrics/metrics-lib]: Add a heartbeat log message indicating progress and estimated time left

[Tor Bug Tracker & Wiki]

#22990: Add a heartbeat log message indicating progress and estimated time left
-+--
 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):

 Keeping it simple by omitting the time estimate sounds fine to me. We
 could always add that later if we think it would be useful.

 Regarding using a separate log, I'd probably keep that simple, too, and
 just use the same log. But I don't feel strongly about this.

 Okay, I might grab this ticket and hack on this the next time I'm
 processing larger amounts of data. But if you want to hack on this first,
 feel free to grab it, and I'll review the patch.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22883 [Core Tor/Tor]: Bridge unavailable during differential consensus update

[Tor Bug Tracker & Wiki]

#22883: Bridge unavailable during differential consensus update
-+-
 Reporter:  torvlnt33r   |  Owner:  nickm
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.1.4-alpha
 Severity:  Normal   | Resolution:
 Keywords:  regression, cpu, usage, review-  |  Actual Points:  1
  group-21   |
Parent ID:   | Points:  1
 Reviewer:  dgoulet  |Sponsor:
-+-
Changes (by nickm):

 * status:  merge_ready => needs_review
 * reviewer:  ahf => dgoulet


Comment:

 Okay. I'm putting this back in needs-review in hopes dgoulet will have
 time for an extra review, since threading bugs are scary. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22990 [Metrics/metrics-lib]: Add a heartbeat log message indicating progress and estimated time left

[Tor Bug Tracker & Wiki]

#22990: Add a heartbeat log message indicating progress and estimated time left
-+--
 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):

 Yes, a heartbeat would be useful.

 Why not keep it simple by only noting the total versus processed count
 (units in bytes and files or whatever is appropriate) and omitting the
 time estimate?
 From a few heartbeat message it is easy to infer/guesstimate the time
 needed or a potential slowdown for the current operation.

 The heartbeats could be written to their own log for further processing
 (using some logback config features).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22811 [Metrics/ExoneraTor]: Upgrade libraries to new Debian stable

[Tor Bug Tracker & Wiki]

#22811: Upgrade libraries to new Debian stable
+--
 Reporter:  karsten |  Owner:  metrics-team
 Type:  enhancement | Status:  merge_ready
 Priority:  Medium  |  Milestone:
Component:  Metrics/ExoneraTor  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 Looks fine!
 (Same changes should be applied to metrics-web.  Is there a ticket?)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22827 [Core Tor/Tor]: Formalise CollecTor spec for sanitised bridge descriptors and put in torspec

[Tor Bug Tracker & Wiki]

#22827: Formalise CollecTor spec for sanitised bridge descriptors and put in
torspec
-+-
 Reporter:  isis |  Owner:  karsten
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-spec, tor-docs, tor-bridges  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by iwakeh):

 Looks fine!

 Maybe keep the comment section small by removing all resolved comments,
 like c00, c00a, c01,c01a (actually the entire xslt discussion), c07, c07a.
 c03 could be replaced by a remark that ANTLR is too much overhead for
 the moment.
 Regarding c02, c02a:  There is no list of references in the new html.  If
 that resolves the issue, it could also be removed.

 Minor format issue/nitpick:
 I don't find the choice of `[:n]` very intuitive as operator (and also
 applying it from the right.  Maybe just use a function notation, e.g.,
 `Bn`.  For example:
 `KeyedHash = SHA256(Ipv4Address | Fingerprint | Secret)[:3]` could become
 `KeyedHash = B3(SHA256(Ipv4Address | Fingerprint | Secret))`.

 Shouldn't the additional xslt and awk files used for generating html be
 also added to git?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20247 [Core Tor/Tor]: seccomp2 crash after closing and opening ipv6 DirPort + OrPort

[Tor Bug Tracker & Wiki]

#20247: seccomp2 crash after closing and opening ipv6 DirPort + OrPort
-+-
 Reporter:  toralf   |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.2.9.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.8
 Severity:  Normal   | Resolution:  fixed
 Keywords:  easy, crash, 028-backport, ipv6, |  Actual Points:
  review-group-21|
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: 0.3.2.x-final => Tor: 0.2.9.x-final


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

Re: [tor-bugs] #20247 [Core Tor/Tor]: seccomp2 crash after closing and opening ipv6 DirPort + OrPort

[Tor Bug Tracker & Wiki]

#20247: seccomp2 crash after closing and opening ipv6 DirPort + OrPort
-+-
 Reporter:  toralf   |  Owner:  nickm
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.8
 Severity:  Normal   | Resolution:  fixed
 Keywords:  easy, crash, 028-backport, ipv6, |  Actual Points:
  review-group-21|
Parent ID:   | Points:  1
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

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


Comment:

 Merged!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22288 [Metrics/Metrics website]: Use newly recognized OnionPerf keys

[Tor Bug Tracker & Wiki]

#22288: Use newly recognized OnionPerf keys
-+--
 Reporter:  karsten  |  Owner:  metrics-team
 Type:  enhancement  | Status:  merge_ready
 Priority:  High |  Milestone:
Component:  Metrics/Metrics website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by iwakeh):

 * status:  needs_review => merge_ready


Comment:

 Changes build fine and look ok.
 Merge-ready.

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

Re: [tor-bugs] #22912 [Metrics/metrics-lib]: tpf parsing drops trailing newline

[Tor Bug Tracker & Wiki]

#22912: tpf parsing drops trailing newline
-+---
 Reporter:  iwakeh   |  Owner:  iwakeh
 Type:  defect   | Status:  needs_review
 Priority:  High |  Milestone:  metrics-lib 2.1.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * milestone:   => metrics-lib 2.1.0


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

Re: [tor-bugs] #22983 [Metrics/metrics-lib]: add a descriptor interface and implementation for web-logs

[Tor Bug Tracker & Wiki]

#22983: add a descriptor interface and implementation for web-logs
-+---
 Reporter:  iwakeh   |  Owner:  metrics-team
 Type:  enhancement  | Status:  needs_review
 Priority:  Medium   |  Milestone:  metrics-lib 2.1.0
Component:  Metrics/metrics-lib  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+---
Changes (by iwakeh):

 * milestone:   => metrics-lib 2.1.0


Comment:

 Prerequisite for CollecTor 1.3.0

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

[tor-bugs] [Tor Bug Tracker & Wiki] Batch modify: #20287, #21759, #21139

[Tor Bug Tracker & Wiki]

Batch modification to #20287, #21759, #21139 by iwakeh:
milestone to CollecTor 1.4.0

Comment:
Move to next milestone to limit 1.3.0 to the webstats functionality.

--
Tickets URL: 

Tor Bug Tracker & Wiki 
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] #21760 [Metrics/CollecTor]: Onionperf deployment - CollecTor side

[Tor Bug Tracker & Wiki]

#21760: Onionperf deployment - CollecTor side
---+-
 Reporter:  iwakeh |  Owner:  iwakeh
 Type:  enhancement| Status:  closed
 Priority:  Medium |  Milestone:  CollecTor 1.3.0
Component:  Metrics/CollecTor  |Version:
 Severity:  Normal | Resolution:  implemented
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-
Changes (by iwakeh):

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


Comment:

 As the switch to onionperf is done (cf.
 https://collector.torproject.org/recent/torperf/) and all remaining tasks
 (like sync and persistence etc.) have their own tickets, closing as
 implemented.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23045 [Applications/Tor Browser]: Replace oleacc.tlb with our own during build time

[Tor Bug Tracker & Wiki]

#23045: Replace oleacc.tlb with our own during build time
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-gitian
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 mingw-w64 contains `oleacc.tlb` (see
 7c90d5921bd2cb678eec09d05b10ce6fd13463bc) which is a binary blob needed
 for compiling Tor Browser. We can do better and get rid of the one in the
 repo and build it ourselves.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23044 [Applications/Tor Browser]: Replace stdole2.tlb with our own during build time

[Tor Bug Tracker & Wiki]

#23044: Replace stdole2.tlb with our own during build time
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:  tbb-gitian
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 The mingw-w64 repo contains the binary `stdole2.tlb` which is needed for
 building Tor Browser (see: 17e09279acf8b7f44d731c9a65541a474af4f1b5). It
 turns out we can do better than relying on that binary blob and create
 that typelib during build 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] #13398 [Applications/Tor Browser]: at startup, browser gleans user FULL NAME (real name, given name) from O/S

[Tor Bug Tracker & Wiki]

#13398: at startup, browser gleans user FULL NAME (real name, given name) from 
O/S
--+
 Reporter:  zinc  |  Owner:  pospeselr
 Type:  defect| Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201707R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by gk):

 Replying to [comment:12 mcs]:
 > Replying to [comment:11 pospeselr]:
 > > I can go through another round, fix these issues, and upload a new
 patch if you like (while disabling sublime's 'trim trailing white-space'
 option).
 >
 > If you can quickly produce a new patch, please proceed. But maybe it
 makes sense to wait for feedback from another member of our team. gk,
 please let pospeselr know if you want a revised patch right away.

 I think proposing a new patch addressing your review comments is a good
 idea.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23042 [Internal Services/Service - lists]: emails to the wtf@ email list are bouncing

[Tor Bug Tracker & Wiki]

#23042: emails to the wtf@ email list are bouncing
---+-
 Reporter:  t0mmy  |  Owner:  qbi
 Type:  defect | Status:  new
 Priority:  High   |  Milestone:
Component:  Internal Services/Service - lists  |Version:
 Severity:  Normal | Resolution:
 Keywords:  wtf|  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by karsten):

 Oh, I believe this is my typo when I attempted to copy wtf on a thread
 with t0mmy. 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] #17569 [Applications/Tor Browser]: Add uBlock Origin to the Tor Browser

[Tor Bug Tracker & Wiki]

#17569: Add uBlock Origin to the Tor Browser
+--
 Reporter:  kernelcorn  |  Owner:  tbb-team
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-usability tbb-security  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by cypherpunks):

 Replying to [comment:23 cypherpunks]:
 > contains spyware.
 > constant connection to raw.githubusercontents.com

 For dynamic assets and a few pictures as can be seen in the sourcecode
 
https://github.com/gorhill/uBlock/search?utf8=%E2%9C%93=githubusercontent=

 Hardly spyware.

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