Re: [tor-bugs] #29127 [Internal Services/Tor Sysadmin Team]: Please create email alias and LDAP for Cecylia (was: Please create email alias and LDAP for new dev)

[Tor Bug Tracker & Wiki]

#29127: Please create email alias and LDAP for Cecylia
-+-
 Reporter:  ewyatt   |  Owner:  tpa
 Type:  task | Status:  new
 Priority:  High |  Milestone:
Component:  Internal Services/Tor Sysadmin Team  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by arma):

 I see signatures now.

 Yes please!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201901  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by omg):

 * keywords:  TorBrowserTeam20901 => TorBrowserTeam201901


Comment:

 https://bugzilla.mozilla.org/show_bug.cgi?id=1516735

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sysrqb):

 * cc: dcf (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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sysrqb):

 * cc: dcf (removed)


Comment:

 {{{
  0:31.51 make[4]: Entering directory '/home/user/tor-browser/obj-x86
 -linux-android/parser/expat/lib'
  0:31.51 /home/user/android-toolchain/android-ndk/toolchains/llvm/prebuilt
 /linux-x86_64/bin/clang -std=gnu99 --target=i686-linux-android -o
 xmlparse.o -c -I/home/user/tor-browser/obj-x86-linux-
 android/dist/system_wrappers -include /home/user/tor-
 browser/config/gcc_hidden.h -DNDEBUG=1 -DTRIMMED=1 -DHAVE_EXPAT_CONFIG_H
 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API
 -DIMPL_LIBXUL -I/home/user/tor-browser/parser/expat/lib -I/home/user/tor-
 browser/obj-x86-linux-android/parser/expat/lib -I/home/user/tor-
 browser/obj-x86-linux-android/dist/include -I/home/user/tor-
 browser/obj-x86-linux-android/dist/include/nspr -I/home/user/tor-
 browser/obj-x86-linux-android/dist/include/nss -fPIC -include /home/user
 /tor-browser/obj-x86-linux-android/mozilla-config.h -DMOZILLA_CLIENT
 -Qunused-arguments -isystem /home/user/android-toolchain/android-
 ndk/platforms/android-16/arch-x86/usr/include -isystem /home/user/android-
 toolchain/android-ndk/platforms/android-16/arch-x86/usr/include -gcc-
 toolchain /home/user/android-toolchain/android-
 ndk/toolchains/x86-4.9/prebuilt/linux-x86_64 -D__ANDROID_API__=16
 -Qunused-arguments -Wall -Wempty-body -Wignored-qualifiers -Wpointer-arith
 -Wsign-compare -Wtype-limits -Wunreachable-code -Wunreachable-code-return
 -Wclass-varargs -Wloop-analysis -Wstring-conversion -Wno-error=deprecated-
 declarations -Wno-error=array-bounds -Wformat -Wformat-security -Wno-gnu-
 zero-variadic-macro-arguments -fno-short-enums -fno-exceptions -fno-
 strict-aliasing -ffunction-sections -fdata-sections -fno-math-errno -pipe
 -g -Oz -fomit-frame-pointer  -MD -MP -MF .deps/xmlparse.o.pp   /home/user
 /tor-browser/parser/expat/lib/xmlparse.c

  0:31.94 /home/user/tor-browser/parser/expat/lib/xmlparse.c:844:3:
 warning: implicit declaration of function 'arc4random_buf' is invalid in
 C99 [-Wimplicit-function-declaration]
  0:31.94   arc4random_buf(&entropy, sizeof(entropy));
  0:31.94   ^
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * cc: dcf (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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sysrqb):

 Replying to [comment:4 omg]:
 > https://bugzilla.mozilla.org/show_bug.cgi?id=1516642

 Heh, nifty. Nice find, thanks. I guess that confirms (most of) my
 assumptions.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by omg):

 https://bugzilla.mozilla.org/show_bug.cgi?id=1516642

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20343 [Core Tor/Chutney]: Write a setup.py for chutney

[Tor Bug Tracker & Wiki]

#20343: Write a setup.py for chutney
--+
 Reporter:  dawuud|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  install   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by exarkun):

 Practically speaking, it looks like it would be a good idea to re-arrange
 the repository structure a good deal before writing a setup.py.
 distutils/setuptools could probably be bent to deal with the current
 structure but it will be a lot easier if chutney changes to look more like
 a typical Python project.

 Are folks okay with that?  I don't know why it is arranged as it currently
 is.  I would assume just non-familiarity with Python conventions on the
 part of the author (and/or non-existence of those conventions at whatever
 time Chutney was written).

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29077 [Obfuscation/meek]: uTLS for meek-client camouflage

[Tor Bug Tracker & Wiki]

#29077: uTLS for meek-client camouflage
--+--
 Reporter:  dcf   |  Owner:  dcf
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:  moat utls |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dcf):

 * status:  new => needs_review


Comment:

 Here is a new candidate: meek branch [https://gitweb.torproject.org
 /pluggable-
 transports/meek.git/log/?h=utls_2&id=6c2cad6ce0e1d0d23ec88edb7942362de2552b0e
 utls_2]

 This is a rewrite using the obfs4proxy-inspired technique (comment:4),
 with a few implementation differences. Instead of `dialTLS` being attached
 to the `RoundTripper` wrapper with a distinguised error code, use a
 standalone `dialUTLS` function. Store the state for the dynamically
 created `Transport` in a closure rather than in the parent struct. Raise
 an error if the ALPN changes.

 You control which fingerprint to use with a SOCKS arg, like
 `utls=HelloChrome_Auto`. With the SOCKS arg, it uses the stdlib net/http
 as before. Using `utls=` with `--helper` is an error.

 Currently this breaks proxy support, because previously we were using the
 built-in proxy support of net/http, and we can't do that anymore with
 uTLS; we'll have to make our own proxy connections. I'll restore proxy
 support separately.

 I've removed HelloRandomized and HelloGolang from the table of allowed TLS
 fingerprints. HelloRandomized because
 [https://lists.torproject.org/pipermail/tor-dev/2019-January/013639.html
 it can negotiate different ALPN], and HelloGolang because that's ideally
 equivalent to omitting the `utls=` arg. I'm open to having it recognize
 `utls=HelloGolang` as an alias for omitting the `utls=` arg, because
 compatibility with meek_lite is the most important thing here.

 When creating the internal `http.Transport`, I think I'd like to make it
 have the same default settings as `http.DefaultTransport` with respect to
 timeouts, idle connections, etc. So I'm thinking of cloning the public
 fields of `http.DefaultTransport` using the reflection trick from
 comment:11:ticket:12208. Unfortunately `http2.Transport`
 [https://github.com/golang/go/issues/16581 doesn't expose configuration
 options] in the same way. Maybe it doesn't matter much? My main concern
 here is not having infinite timeouts.

 I tested the TLS fingerprint with a few different configurations.
 ||=configuration =||=fingerprint =||=  seen (all time)=||
 ||no camouflage ||[https://tlsfingerprint.io/id/c4b0fe116abff001
 c4b0fe116abff001]
 
[https://web.archive.org/web/20190125221734/https://tlsfingerprint.io/id/c4b0fe116abff001
 archive] ||  0.01%||
 ||`--helper` (Tor Browser 8.0.4 / Firefox 60.4.0esr)
 ||[https://tlsfingerprint.io/id/bb94e801f7aee52b bb94e801f7aee52b]
 
[https://web.archive.org/web/20190125221851/https://tlsfingerprint.io/id/bb94e801f7aee52b
 archive] ||  0.58%||
 ||`utls=HelloChrome_70` ||[https://tlsfingerprint.io/id/bc4c7e42f4961cd7
 bc4c7e42f4961cd7]
 
[https://web.archive.org/web/20190125222100/https://tlsfingerprint.io/id/bc4c7e42f4961cd7
 archive] ||  3.54%||
 ||`utls=HelloFirefox_63` ||[https://tlsfingerprint.io/id/6bfedc5d5c740d58
 6bfedc5d5c740d58]
 
[https://web.archive.org/web/20190125222153/https://tlsfingerprint.io/id/6bfedc5d5c740d58
 archive] ||  1.66%||

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #13221 [Core Tor/Tor]: Misleading error messages about bind_ipv4_only and bind_ipv6_only?

[Tor Bug Tracker & Wiki]

#13221: Misleading error messages about bind_ipv4_only and bind_ipv6_only?
-+-
 Reporter:  arma |  Owner:  (none)
 Type:  defect   | Status:
 |  needs_review
 Priority:  Low  |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  041-proposed, tor-client, easy,  |  Actual Points:
  logging, message, usability|
Parent ID:   | Points:  .1
 Reviewer:   |Sponsor:
-+-
Changes (by kjak):

 * status:  new => needs_review
 * keywords:  tor-client, easy, logging, message, usability => 041-proposed,
 tor-client, easy, logging, message, usability


Comment:

 Here is a PR to fix this: https://github.com/torproject/tor/pull/669

 I didn't change the overall wording of the error message because
 personally I think it's fine (aside from the IP version mixup).  I think
 it's short and clear and means "You told me to only bind to an IPv4
 address but I couldn't interpret the address as IPv4."

 I took the liberty of also cleaning up the error-checking logic to make it
 a little more precise about what is being checked.  I hope that's OK.

 (I'm also adding the keyword 041-proposed, which my other recent tickets
 got.  Is it OK for me to do that or is adding a keyword like that reserved
 for core team members?)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by sysrqb):

 Quick update. I'm testing with this nowish (seems somewhat promising):

 {{{
 diff --git a/parser/expat/lib/xmlparse.c b/parser/expat/lib/xmlparse.c
 index 209f20e094dc..056974e1479d 100644
 --- a/parser/expat/lib/xmlparse.c
 +++ b/parser/expat/lib/xmlparse.c
 @@ -839,7 +839,7 @@ generate_hash_secret_salt(XML_Parser parser)
  {
unsigned long entropy;
(void)parser;
 -#if defined(HAVE_ARC4RANDOM_BUF) || defined(__CloudABI__)
 +#if (defined(HAVE_ARC4RANDOM_BUF) || defined(__CloudABI__)) &&
 !defined(ANDROID)
(void)gather_time_entropy;
arc4random_buf(&entropy, sizeof(entropy));
return ENTROPY_DEBUG("arc4random_buf", entropy);
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26241 [Obfuscation/meek]: Check meek TLS fingerprint on ESR 60

[Tor Bug Tracker & Wiki]

#26241: Check meek TLS fingerprint on ESR 60
--+-
 Reporter:  dcf   |  Owner:  dcf
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:  implemented
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by dcf):

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


Comment:

 Better late than never, I checked Tor Browser 8.0.4 against Firefox
 60.4.0esr and got a match.
 ||=Tor Browser 8.0.4 =||https://tlsfingerprint.io/id/bb94e801f7aee52b
 
([https://web.archive.org/web/20190125202704/https://tlsfingerprint.io/id/bb94e801f7aee52b
 archive]) [[attachment:TorBrowser8.0.4.pcap|pcap]] ||
 ||=Firefox 60.4.0esr =||https://tlsfingerprint.io/id/bb94e801f7aee52b
 
([https://web.archive.org/web/20190125202704/https://tlsfingerprint.io/id/bb94e801f7aee52b
 archive]) [[attachment:Firefox_60.4.0esr.pcap|pcap]] ||

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26241 [Obfuscation/meek]: Check meek TLS fingerprint on ESR 60

[Tor Bug Tracker & Wiki]

#26241: Check meek TLS fingerprint on ESR 60
--+-
 Reporter:  dcf   |  Owner:  dcf
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by dcf):

 * Attachment "Firefox_60.4.0esr.pcap" added.

 Firefox 60.4.0esr visiting https://example.com/

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

Re: [tor-bugs] #26241 [Obfuscation/meek]: Check meek TLS fingerprint on ESR 60

[Tor Bug Tracker & Wiki]

#26241: Check meek TLS fingerprint on ESR 60
--+-
 Reporter:  dcf   |  Owner:  dcf
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by dcf):

 * Attachment "Firefox_60.4.0esr.pcap" removed.

 Firefox 60.4.0esr visiting https://example.com/

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

Re: [tor-bugs] #26241 [Obfuscation/meek]: Check meek TLS fingerprint on ESR 60

[Tor Bug Tracker & Wiki]

#26241: Check meek TLS fingerprint on ESR 60
--+-
 Reporter:  dcf   |  Owner:  dcf
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by dcf):

 * Attachment "Firefox_60.4.0esr.pcap" added.

 Firefox 60.4.0esr visiting https://example.com/

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

Re: [tor-bugs] #26241 [Obfuscation/meek]: Check meek TLS fingerprint on ESR 60

[Tor Bug Tracker & Wiki]

#26241: Check meek TLS fingerprint on ESR 60
--+-
 Reporter:  dcf   |  Owner:  dcf
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by dcf):

 * Attachment "TorBrowser8.0.4.pcap" added.

 Tor Browser 8.0.4 with meek-azure.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24131 [Webpages/Website]: torproject.org work

[Tor Bug Tracker & Wiki]

#24131: torproject.org work
--+--
 Reporter:  isabela   |  Owner:  hiro
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:  website redesign
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team,  |  Actual Points:
Parent ID:  #21222| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 Okay, we chatted a bit about that and here are some notes

 19:29 <+GeKo> for the "download in another locale" page
 19:30 <+GeKo> we should just have 32bit and 64 bit as options
 19:30 <+GeKo> (if there are those two)
 19:30 <+GeKo> and 64bit first

 (and I actually mean no "32/64-bit (sig) / 64-bit (sig)" options but
 "64-bit (sig) / 32-bit (sig)" ones)

 19:32 <+GeKo> i wonder whether we should show which version we are
 offering for download, though
 19:33 <+GeKo> but maybe i am the only one that gets nervous by clicking on
 a thing
 19:33 <+GeKo> and suddenly some binary is supposed to get downloaded
 19:33 <+GeKo> without knowing whether that's the version i should have or
 what the current version actually is
 19:33 <+GeKo> but i think i don't have strong feelings here

 Most importantly, though:

 19:34 <+GeKo> good stuff!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20343 [Core Tor/Chutney]: Write a setup.py for chutney

[Tor Bug Tracker & Wiki]

#20343: Write a setup.py for chutney
--+
 Reporter:  dawuud|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Chutney  |Version:
 Severity:  Normal| Resolution:
 Keywords:  install   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by exarkun):

 > Do we need chutney to be versioned to have a setup.py? (#20344)

 Versioning is great but I don't think it is a requirement for this ticket.
 Versioning would probably be a requirement for issuing a _release_ and
 having a setup.py would also be helpful in producing a release.  But
 setup.py will also let folks install this via a git URL or a hand-build
 source archive.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  defect  | Status:  closed
 Priority:  Immediate   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-rbm, TorBrowserTeam201901R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

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


Comment:

 Thanks, closing. pospeselr: let me know if you are not happy with the
 fixups.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26698 [Core Tor/Tor]: Authorities should put a hash of the bandwidth file in their votes

[Tor Bug Tracker & Wiki]

#26698: Authorities should put a hash of the bandwidth file in their votes
-+-
 Reporter:  teor |  Owner:  (none)
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  Low  |  Milestone:  Tor:
 |  0.4.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-crypto tor-dirauth tor-bwauth|  Actual Points:
  041-proposed   |
Parent ID:  #27047   | Points:  0.5
 Reviewer:  nickm|Sponsor:
-+-
Changes (by juga):

 * status:  needs_revision => needs_review


Comment:

 ok, more fixups

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  defect  | Status:  needs_review
 Priority:  Immediate   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201901R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by mcs):

 r=mcs
 Both of the fixup commits look good to me. I did not try to build with
 them, but I know that is happening as part of the 8.5a7 release process.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 sysrqb notes that he encountered that yesterday when using the 8.0 branch.
 Given that our nightly with 8.5 this morning still succeeded this seems
 likely to be introduced by upstream in the point release.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam20901   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by gk):

 For some reason our Android build for 8.5a7 is suddenly broken. Any
 pointers how to fix this and where this comes from are appreciated. That's
 pretty weird. The nightly from today built fine it seems. Maybe it's just
 a "local" issue?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29182 [Applications/Tor Browser]: Release candidate build breaks on Android with "error: hidden symbol 'arc4random_buf' is not defined locally"

[Tor Bug Tracker & Wiki]

#29182: Release candidate build breaks on Android with  "error: hidden symbol
'arc4random_buf' is not defined locally"
--+
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Immediate |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
  |  TorBrowserTeam20901
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 {{{
 23:03.28 /var/tmp/dist/android-toolchain/android-ndk/toolchains/arm-linux-
 androideabi-4.9/prebuilt/linux-x86_64/lib/gcc/arm-linux-androideabi/4.9.x
 /../../../../arm-linux-androideabi/bin/ld: error: hidden symbol
 'arc4random_buf' is not defined locally
 23:03.28 /var/tmp/dist/android-toolchain/android-ndk/toolchains/arm-linux-
 androideabi-4.9/prebuilt/linux-x86_64/lib/gcc/arm-linux-androideabi/4.9.x
 /../../../../arm-linux-androideabi/bin/ld: error: hidden symbol
 'arc4random_buf' is not defined locally
 23:03.28 clang++: error: linker command failed with exit code 1 (use -v to
 see invocation)
 23:03.28 /var/tmp/build/firefox-6dde994c6580/config/rules.mk:707: recipe
 for target 'libxul.so' failed
 23:03.28 make[4]: *** [libxul.so] Error 1
 }}}

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

Re: [tor-bugs] #29181 [Applications/Tor Browser]: Make it possible to force rebuild of debootstrap-image

[Tor Bug Tracker & Wiki]

#29181: Make it possible to force rebuild of debootstrap-image
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  task| Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  TorBrowserTeam201901R, tbb-rbm  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by boklm):

 * keywords:  TorBrowserTeam201901, tbb-rbm => TorBrowserTeam201901R, tbb-
   rbm
 * status:  new => needs_review


Comment:

 There is a patch for review in branch `bug_29181_v2`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_29181_v2&id=592acedeb13ec0d08087b4cd2fb414b04431fb13

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29166 [Metrics/Statistics]: Run modules from Java only

[Tor Bug Tracker & Wiki]

#29166: Run modules from Java only
+--
 Reporter:  karsten |  Owner:  karsten
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  irl |Sponsor:
+--

Comment (by notirl):

 {{{
 this.connection = DriverManager.getConnection(jdbcString);
 }}}

 Should this not still be explicitly `this.jdbcString`? It's still a class
 member and not a local variable.


 

 Some of the paths have been defined with `/` in them, which breaks
 compatibility with non-Unix operating systems. (Windows uses `\` and RISC
 OS uses `:` as examples.) I think we don't care but it's worth being aware
 of it.

 We should have a policy and be explicit about our use of, or avoidance of,
 java.nio.file.Paths.


 

 In general this looks OK, probably is best to not deploy it just before
 Brussels though. I can give it a more thorough review after Brussels.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29181 [Applications/Tor Browser]: Make it possible to force rebuild of debootstrap-image

[Tor Bug Tracker & Wiki]

#29181: Make it possible to force rebuild of debootstrap-image
-+-
 Reporter:  boklm|  Owner:  tbb-team
 Type:  task | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  TorBrowserTeam201901,
 Severity:  Normal   |  tbb-rbm
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 The filename of container images created by `projects/debootstrap-image`
 does not include `var/build_id` or any version number, so it doesn't get
 rebuilt automatically when the build instructions change.

 However in some cases such as #29158 we want to force those images to be
 rebuilt.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
+--
 Reporter:  boklm   |  Owner:  tbb-team
 Type:  defect  | Status:  needs_review
 Priority:  Immediate   |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201901R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * cc: mcs, brade, pospeselr (added)
 * keywords:  tbb-rbm, TorBrowserTeam201901 => tbb-rbm,
   TorBrowserTeam201901R
 * status:  new => needs_review


Comment:

 Okay, this took longer than anticipated. There was more to actually fix.
 :( I pushed two fixup commits to `tor-browser-60.5.0esr-8.5-1`
 (https://gitweb.torproject.org/tor-browser.git/commit/?h=tor-
 browser-60.5.0esr-8.5-1&id=b6487d517d9982332f3bfad1f14b6e5ed9f77c53 and
 https://gitweb.torproject.org/tor-browser.git/commit/?h=tor-
 browser-60.5.0esr-8.5-1&id=6dde994c6580634bd3cb9809c2eb0e02499e65b7). Let
 me know whether they look good to you.

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

Re: [tor-bugs] #27503 [Applications/Tor Browser]: Disabling accessibility on Windows breaks screen readers

[Tor Bug Tracker & Wiki]

#27503: Disabling accessibility on Windows breaks screen readers
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression,  |  Actual Points:
  GeorgKoppen201901, TorBrowserTeam201901|
Parent ID:   | Points:
 Reviewer:  boklm|Sponsor:
-+-
Changes (by gk):

 * keywords:
 tbb-8.0-issues, tbb-regression, GeorgKoppen201901,
 TorBrowserTeam201901R
 =>
 tbb-8.0-issues, tbb-regression, GeorgKoppen201901,
 TorBrowserTeam201901


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27503 [Applications/Tor Browser]: Disabling accessibility on Windows breaks screen readers

[Tor Bug Tracker & Wiki]

#27503: Disabling accessibility on Windows breaks screen readers
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression,  |  Actual Points:
  GeorgKoppen201901, TorBrowserTeam201901R   |
Parent ID:   | Points:
 Reviewer:  boklm|Sponsor:
-+-
Changes (by boklm):

 * status:  needs_review => new


Comment:

 Replying to [comment:29 gk]:
 > `bug_27503_v3` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/log/?h=bug_27503_v3) in my `tor-browser-build` repo has the two
 fixes for review. We should have committed the first one when fixing
 #28874 but forgot about it. The second one is actually enabling
 accessibility support. To test everything one needs a rebased branch
 against 60.5.0esr, which e.g. be found in #29104.

 This looks good to me. I merged those two patches to master with commit
 `97effd6d7380f76dd53e666b034113c84692f51a`.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28363 [Core Tor/Tor]: Make a torrc option which prevents Tor from falling asleep

[Tor Bug Tracker & Wiki]

#28363: Make a torrc option which prevents Tor from falling asleep
--+--
 Reporter:  wagon |  Owner:  (none)
 Type:  enhancement   | Status:  assigned
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  040-proposed  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by wagon):

 > What's the first version where you have seen this problem?
 I cannot remember, but I did saw it within last year for last stable Tor
 versions.

 > And are the steps to reproduce it just "wait 60 minutes and use a
 control port to ask what circuits there are?"
 It is an example, but it is easier to see. Check your `netstat` or `ss`,
 and you will see that your Tor client is not connected to any relay, and
 there is no open TCP connections. I assumed it is well known behavior of
 Tor (closing all circuits and disconnecting from Tor network, if no
 application is using it during some period of inactivity). Yes, it wasn't
 related to any dormant mode as it was before 0.4.0.x.

 Now you introduced dormant mode and say that default inactivity period is
 24h, which is many times higher than the original inactivity timeout for
 old versions. That is why I was surprised and asked you about it.

 > if you're seeing a change in recent releases, then it's not dormant mode
 that you're seeing.
 Yes, it is not literally dormant mode, but it imitates it. I didn't see
 any change, I just tell you that this is how Tor before 0.4.0.x behaves
 (according to my current understanding). Later I read man page for 0.4.0.x
 and saw that it should behave differently, i.e. with much higher period of
 inactivity.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29180 [Applications/Tor Browser]: MAR download stalls when about dialog is opened

[Tor Bug Tracker & Wiki]

#29180: MAR download stalls when about dialog is opened
--+--
 Reporter:  mcs   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #25694| Points:
 Reviewer:|Sponsor:
--+--
Changes (by mcs):

 * parent:   => #25694


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #28885 [Applications/Tor Browser]: notify users that update is downloading

[Tor Bug Tracker & Wiki]

#28885: notify users that update is downloading
---+---
 Reporter:  mcs|  Owner:  tbb-team
 Type:  defect | Status:
   |  needs_revision
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  TorBrowserTeam201901, ux-team  |  Actual Points:
Parent ID:  #25694 | Points:
 Reviewer: |Sponsor:
---+---

Comment (by mcs):

 Replying to [comment:8 gk]:
 > I am using a patched 8.5a5 (I essentially applied your patch "by hand"
 to the various pieces in the omni.ja's) to test the update to 8.5a6 on a
 Linux machine.

 Kathy and I were finally able to reproduce this. I opened a new ticket:
 #29180

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29180 [Applications/Tor Browser]: MAR download stalls when about dialog is opened

[Tor Bug Tracker & Wiki]

#29180: MAR download stalls when about dialog is opened
--+--
 Reporter:  mcs   |  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:|
--+--
 In #28885, Georg encountered a bug that causes the browser update to
 stall. Here are the steps that Kathy and I used to reproduce it:
 1. Start a clean copy of Tor Browser 8.5a5 on a 64-bit Linux system.
 2. Set `app.update.auto` to `false` and `app.update.log` to `true`.
 3. Open the about dialog and click "Update to 8.5a6" to begin downloading
 the MAR file.
 4. Quickly close and reopen the about dialog. The download will stall and
 not make any further progress.

 The following was logged to the browser console:
  AUS:SVC UpdateService:downloadUpdate - no support for downloading more
 than one update at a time

 This problem is fallout from the fact that when the about dialog is
 opened, the browser cancels the download and starts a new one. Here is the
 code from the `startDownload()` function inside `browser/base/content
 /aboutDialog-appUpdater.js`:
  ...
  this.aus.pauseDownload();
  let state = this.aus.downloadUpdate(this.update, false);
  ...

 Looking at the code in `toolkit/mozapps/update/nsUpdateService.js`, we see
 that `pauseDownload()` cancels the first download via
 `nsIRequest.cancel()`, which does not take effect immediately. Cleanup of
 the `Downloader` occurs inside an `onStopRequest()` listener and that
 entire process is asynchronous.

 One possible fix is to not pause and restart the download when the about
 dialog is opened. Kathy and I do not yet know if that would introduce
 other 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] #29171 [Obfuscation/meek]: Redeploy meek-server instances with go1.11.5

[Tor Bug Tracker & Wiki]

#29171: Redeploy meek-server instances with go1.11.5
--+-
 Reporter:  dcf   |  Owner:  dcf
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Obfuscation/meek  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+-
Changes (by sysrqb):

 * cc: sysrqb (added)


Comment:

 I'll update this ticket when bridgedb's meek-server instance is updated.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27597 [Applications/Tor Browser]: ASan build option in tor-browser-build is broken

[Tor Bug Tracker & Wiki]

#27597: ASan build option in tor-browser-build is broken
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-8.0-issues, tbb-regression,  |  Actual Points:
  tbb-rbm, TorBrowserTeam201901R |
Parent ID:   | Points:
 Reviewer:  boklm|Sponsor:
-+-
Changes (by gk):

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


Comment:

 Thanks, I applied them to `tor-browser-60.4.0esr-8.5-1` as commit
 2d5a66c40885598133593c641fd8401a0b2f2fac,
 3723fd7b92f17ed857cea9bacb26b77fa4d34efc, and
 b5793205da5fde6035f1bb7c49752fd38a9ed6e9.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25702 [Applications/Tor Browser]: Activity 1.1 Update Tor Browser icon to follow design guidelines.

[Tor Bug Tracker & Wiki]

#25702: Activity 1.1 Update Tor Browser icon to follow design guidelines.
+---
 Reporter:  isabela |  Owner:  antonela
 Type:  defect  | Status:  closed
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  ux-team, TorBrowserTeam201901R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor17
+---

Comment (by antonela):

 \o/

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29175 [Core Tor/Tor]: Tor 0.3.5.x mishandles empty socks5 auth

[Tor Bug Tracker & Wiki]

#29175: Tor 0.3.5.x mishandles empty socks5 auth
--+
 Reporter:  arma  |  Owner:  rl1987
 Type:  defect| Status:  accepted
 Priority:  High  |  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  regression, 035-backport  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Old description:

> There is a regression in Tor 0.3.5.x with handling socks5 handshakes that
> offer username/password auth but then present empty username and
> password.
>
> It came in during commit 9068ac3c (which went into 0.3.5.1-alpha).
>
> The symptom is that when you do your socks5 handshake with an empty
> username and password (e.g. like pidgin does it), you get log lines like
> {{{
> Jan 24 19:40:17.000 [warn] Fetching socks handshake failed. Closing.
> Jan 24 19:40:17.000 [warn] socks5: parsing failed - invalid user/pass
> authentication message.
> }}}
>
> Bug reported by a person on #tor, and also separately by #29050.
>
> I asked Josh Glazebrook, the author of the socks library in #29050, for
> some actual traces of correct behavior / incorrect behavior, and he sent:
>
> {{{
> ocks v2.2.3
> tor v0.3.5.7
> client announces it only supports noauth (00)
> server chooses noauth (00)
>

> send  [00 = noauth]
> recv  [server chose noauth]
> send  [connect
> command - ipinfo.io]
> recv  [success]
>

>

> socks v2.2.2
> tor v0.3.5.7
> client announces it supports noauth (00) and userpass (02)
> server chooses userpass (02)
> connection is unsuccessful - server returns general socks server failure,
> tor logs indicate invalid user/pass.
> Jan 24 14:47:15.000 [warn] Fetching socks handshake failed. Closing.
> Jan 24 14:47:56.000 [warn] socks5: parsing failed - invalid user/pass
> authentication message.
>

> send  [00 = noauth, 02 = userpass]
> recv  [server chose userpass]
> send  [00 = zero length username, 00 = zero length
> password]
> recv  [00 = server indicates auth success]
> send  [connect
> command - ipinfo.io]
> recv  [01- general SOCKS server failure] (in tor's
> log output it's saying auth is invalid at this point)
>

>
> socks v.2.2.2
> tor via torbrowser 8.0.4 (unsure of which tor version, but likely older
> than 0.3.5.7)
> client announces it supports noauth (00) and userpass (02)
> server chooses userpass (02)
> connection is successful
>
> send  [00 = noauth, 02 = userpass]
> recv  [server chose userpass]
> send  [00 = zero length username, 00 = zero length
> password]
> recv  [00 = server indicates auth success]
> send  [connect
> command - ipinfo.io]
> recv  [00 = success]
> }}}
>
> Josh further gives us this hint:
>
> {{{
> It appears there is indeed something that changed between older versions
> of
> Tor and newer versions. Looking at the actual data being exchanged, it's
> exactly the same.
>
> The only odd thing is tor v0.3.5.7 is indicating in the auth reply that
> the
> authentication was a success, and only when the connect command is sent,
> it's returning a "general socks server failure" code, but in the actual
> tor
> log it's logging invalid user/pass.
> }}}
>
> I went spelunking and found this code newly in 0.3.5.x:
>
> {{{
>   if (usernamelen && username) {
> tor_free(req->username);
> req->username = tor_memdup_nulterm(username, usernamelen);
> req->usernamelen = usernamelen;
>
> req->got_auth = 1;
>   }
>
>   if (passwordlen && password) {
> tor_free(req->password);
> req->password = tor_memdup_nulterm(password, passwordlen);
> req->passwordlen = passwordlen;
>
> req->got_auth = 1;
>   }
> }}}
>
> Compare to the code in 0.3.4.x:
> {{{
>   if (usernamelen) {
> req->username = tor_memdup(data+2u, usernamelen);
> req->usernamelen = usernamelen;
>   }
>   if (passlen) {
> req->password = tor_memdup(data+3u+usernamelen, passlen);
> req->passwordlen = passlen;
>   }
>   *drain_out = 2u + usernamelen + 1u + passlen;
>   req->got_auth = 1;
> }}}
>
> So in 0.3.4.x when we got a type 0x02 handshake but empty username and
> empty password, we would still set got_auth to 1. In 0.3.5.x when that
> happens, we leave got_auth at 0.
>
> The result is that the socks5 handshake itself still goes identically,
> but when we get the empty username and password, we '''don't record that
> we received it''', even though we send back a "handshake was successful"
> response. And then when application data shows up after that, we try to
> treat it as a socks5 username and password, because we're still waiting
> for one. That's where things go bad.

New description:

 There is a regression in Tor 0.3.5.x with handling socks5 handsha

Re: [tor-bugs] #29175 [Core Tor/Tor]: Tor 0.3.5.x mishandles empty socks5 auth

[Tor Bug Tracker & Wiki]

#29175: Tor 0.3.5.x mishandles empty socks5 auth
--+
 Reporter:  arma  |  Owner:  rl1987
 Type:  defect| Status:  accepted
 Priority:  High  |  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  regression, 035-backport  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by nickm):

 * keywords:  regression, backport-035 => regression, 035-backport
 * priority:  Medium => High


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27597 [Applications/Tor Browser]: ASan build option in tor-browser-build is broken

[Tor Bug Tracker & Wiki]

#27597: ASan build option in tor-browser-build is broken
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression,  |  Actual Points:
  tbb-rbm, TorBrowserTeam201901R |
Parent ID:   | Points:
 Reviewer:  boklm|Sponsor:
-+-
Changes (by boklm):

 * status:  needs_review => merge_ready


Comment:

 The three patches look good to me.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25702 [Applications/Tor Browser]: Activity 1.1 Update Tor Browser icon to follow design guidelines.

[Tor Bug Tracker & Wiki]

#25702: Activity 1.1 Update Tor Browser icon to follow design guidelines.
+---
 Reporter:  isabela |  Owner:  antonela
 Type:  defect  | Status:  closed
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  ux-team, TorBrowserTeam201901R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor17
+---
Changes (by gk):

 * status:  reopened => 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] #22654 [Applications/Tor Browser]: Firefox icon is shown for Tor Browser on Windows 10 start menu

[Tor Bug Tracker & Wiki]

#22654: Firefox icon is shown for Tor Browser on Windows 10 start menu
+--
 Reporter:  gk  |  Owner:
|  pospeselr
 Type:  defect  | Status:  closed
 Priority:  Medium  |  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:  fixed
 Keywords:  tbb-branding, TorBrowserTeam201901  |  Actual Points:
Parent ID:  #25702  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by gk):

 * keywords:  tbb-branding => tbb-branding, TorBrowserTeam201901


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25702 [Applications/Tor Browser]: Activity 1.1 Update Tor Browser icon to follow design guidelines.

[Tor Bug Tracker & Wiki]

#25702: Activity 1.1 Update Tor Browser icon to follow design guidelines.
+---
 Reporter:  isabela |  Owner:  antonela
 Type:  defect  | Status:  reopened
 Priority:  High|  Milestone:
Component:  Applications/Tor Browser|Version:
 Severity:  Normal  | Resolution:
 Keywords:  ux-team, TorBrowserTeam201901R  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:  Sponsor17
+---
Changes (by gk):

 * status:  closed => reopened
 * 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] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
---+--
 Reporter:  boklm  |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Immediate  |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201901  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by gk):

 I.e.
 {{{
 -
 currentTransferable->SetRequestingPrincipal(mSourceNode->NodePrincipal());
 +  nsCOMPtr node = do_QueryInterface(mSourceNode);
 +  currentTransferable->SetRequestingPrincipal(node->NodePrincipal());
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
---+--
 Reporter:  boklm  |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Immediate  |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201901  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by gk):

 QIing to `nsINode` should fix that. I am currently testing a proposed fix

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

Re: [tor-bugs] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
---+--
 Reporter:  boklm  |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Immediate  |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201901  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by watt):

 und test?
 https://hg.mozilla.org/mozilla-central/rev/0f709682e4a0

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
---+--
 Reporter:  boklm  |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Immediate  |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-rbm, TorBrowserTeam201901  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by gk):

 * priority:  Medium => Immediate


Comment:

 That's fallout from #29082, so we should fix that somehow before starting
 the alpha build.

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

[tor-bugs] #29179 [Applications/Tor Browser]: Tor Browser nightly fails to build on macOS

[Tor Bug Tracker & Wiki]

#29179: Tor Browser nightly fails to build on macOS
-+-
 Reporter:  boklm|  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-rbm,
 Severity:  Normal   |  TorBrowserTeam201901
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 The latest Tor Browser nightly failed to build on macOS in the firefox
 part:
 {{{
 17:55.18 /var/tmp/dist/macosx-toolchain/clang/bin/clang++ -target x86_64
 -apple-darwin11 -B /var/tmp/dist/macosx-toolchain/cctools/bin -isysroot
 /var/tmp/dist/macosx-toolchain/SDK -Werror=format -Werror=format-security
 -fstack-protector-strong -D_FORTIFY_SOURCE=2 -std=gnu++14 -o
 nsDragService.o -c -fvisibility=hidden -fvisibility-inlines-hidden
 -DNDEBUG=1 -DTRIMMED=1 -DOS_POSIX=1 -DOS_MACOSX=1
 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API
 -DIMPL_LIBXUL -I/var/tmp/build/firefox-394ffba812d6/widget/cocoa
 -I/var/tmp/build/firefox-394ffba812d6/obj-macos/widget/cocoa
 -I/var/tmp/build/firefox-394ffba812d6/obj-macos/ipc/ipdl/_ipdlheaders
 -I/var/tmp/build/firefox-394ffba812d6/ipc/chromium/src -I/var/tmp/build
 /firefox-394ffba812d6/ipc/glue -I/var/tmp/build/firefox-
 394ffba812d6/layout/forms -I/var/tmp/build/firefox-
 394ffba812d6/layout/generic -I/var/tmp/build/firefox-
 394ffba812d6/layout/style -I/var/tmp/build/firefox-394ffba812d6/layout/xul
 -I/var/tmp/build/firefox-394ffba812d6/widget -I/var/tmp/build/firefox-
 394ffba812d6/widget/headless -I/var/tmp/build/firefox-394ffba812d6/obj-
 macos/dist/include -I/var/tmp/build/firefox-394ffba812d6/obj-
 macos/dist/include/nspr -I/var/tmp/build/firefox-394ffba812d6/obj-
 macos/dist/include/nss -fPIC -DMOZILLA_CLIENT -include /var/tmp/build
 /firefox-394ffba812d6/obj-macos/mozilla-config.h -Qunused-arguments
 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Qunused-arguments -Wall -Wempty-
 body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-
 compare -Wtype-limits -Wunreachable-code -Wunreachable-code-return
 -Wwrite-strings -Wno-invalid-offsetof -Wclass-varargs -Wloop-analysis -Wc
 ++1z-compat -Wcomma -Wimplicit-fallthrough -Wstring-conversion -Wno-
 inline-new-delete -Wno-error=deprecated-declarations -Wno-error=array-
 bounds -Wformat -Wformat-security -Wno-gnu-zero-variadic-macro-arguments
 -Wno-unknown-warning-option -Wno-return-type-c-linkage -fno-sized-
 deallocation -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fno-exceptions -fno-
 strict-aliasing -stdlib=libc++ -fno-rtti -ffunction-sections -fdata-
 sections -fno-exceptions -fno-math-errno -pthread -pipe -g -O3 -fomit-
 frame-pointer  -MD -MP -MF .deps/nsDragService.o.pp  -x objective-c++
 -fobjc-exceptions   /var/tmp/build/firefox-
 394ffba812d6/widget/cocoa/nsDragService.mm
 17:58.32 make[4]: Entering directory '/var/tmp/build/firefox-394ffba812d6
 /obj-macos/widget/headless'
 17:58.32 mkdir -p '.deps/'
 17:58.33 /var/tmp/dist/macosx-toolchain/clang/bin/clang++ -target x86_64
 -apple-darwin11 -B /var/tmp/dist/macosx-toolchain/cctools/bin -isysroot
 /var/tmp/dist/macosx-toolchain/SDK -Werror=format -Werror=format-security
 -fstack-protector-strong -D_FORTIFY_SOURCE=2 -std=gnu++14 -o
 Unified_cpp_widget_headless0.o -c -fvisibility=hidden -fvisibility-
 inlines-hidden -DNDEBUG=1 -DTRIMMED=1 -DOS_POSIX=1 -DOS_MACOSX=1
 -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API
 -DIMPL_LIBXUL -I/var/tmp/build/firefox-394ffba812d6/widget/headless
 -I/var/tmp/build/firefox-394ffba812d6/obj-macos/widget/headless
 -I/var/tmp/build/firefox-394ffba812d6/widget -I/var/tmp/build/firefox-
 394ffba812d6/widget/headless -I/var/tmp/build/firefox-
 394ffba812d6/widget/cocoa -I/var/tmp/build/firefox-394ffba812d6/obj-
 macos/ipc/ipdl/_ipdlheaders -I/var/tmp/build/firefox-
 394ffba812d6/ipc/chromium/src -I/var/tmp/build/firefox-
 394ffba812d6/ipc/glue -I/var/tmp/build/firefox-394ffba812d6/obj-
 macos/dist/include -I/var/tmp/build/firefox-394ffba812d6/obj-
 macos/dist/include/nspr -I/var/tmp/build/firefox-394ffba812d6/obj-
 macos/dist/include/nss -fPIC -DMOZILLA_CLIENT -include /var/tmp/build
 /firefox-394ffba812d6/obj-macos/mozilla-config.h -Qunused-arguments
 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Qunused-arguments -Wall -Wempty-
 body -Wignored-qualifiers -Woverloaded-virtual -Wpointer-arith -Wsign-
 compare -Wtype-limits -Wunreachable-code -Wunreachable-code-return
 -Wwrite-strings -Wno-invalid-offsetof -Wclass-varargs -Wloop-analysis -Wc
 ++1z-compat -Wcomma -Wimplicit-fallthrough -Wstring-conversion -Wno-
 inline-new-delete -Wno-error=deprecated-declarations -Wno-error=array-
 bounds -Wformat -Wformat-security -Wno-gnu-zero

[tor-bugs] #29178 [Applications/Tor Browser]: Don't build master of goxcrypto, goxnet, uniuri and go-webrtc

[Tor Bug Tracker & Wiki]

#29178: Don't build master of goxcrypto, goxnet, uniuri and go-webrtc
-+-
 Reporter:  boklm|  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  TorBrowserTeam201901,
 Severity:  Normal   |  tbb-rbm
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 During the review of #29143 we discussed in which cases a component in
 nightly builds should use the master commit. The conclusion was that we
 usually want to use master for the things we develop, but not for external
 components.

 goxcrypto, goxnet, uniuri are external components that are currently built
 using master. go-webrtc is not but has a `master` target that looks like
 if it was named master instead of nightly as an error.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #27503 [Applications/Tor Browser]: Disabling accessibility on Windows breaks screen readers

[Tor Bug Tracker & Wiki]

#27503: Disabling accessibility on Windows breaks screen readers
-+-
 Reporter:  gk   |  Owner:  gk
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression,  |  Actual Points:
  GeorgKoppen201901, TorBrowserTeam201901R   |
Parent ID:   | Points:
 Reviewer:  boklm|Sponsor:
-+-

Comment (by cypherpunks33):

 Searching through a) doesn't show anything related, but
 https://bugzilla.mozilla.org/show_bug.cgi?id=1489605

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #29177 [Applications/Tor Browser]: Browsing data in prefs.js

[Tor Bug Tracker & Wiki]

#29177: Browsing data in prefs.js
---+--
 Reporter:  iTM1nqY1   |  Owner:  tbb-team
 Type:  defect | Status:  new
 Priority:  Medium |  Component:  Applications/Tor Browser
  Version: |   Severity:  Normal
 Keywords:  tbb-disk-leak  |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
 Mine has

 user_pref("devtools.debugger.tabs",
 "[\"url1\",\"url2\",\"url3\",null,null,null,null,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

Re: [tor-bugs] #29175 [Core Tor/Tor]: Tor 0.3.5.x mishandles empty socks5 auth

[Tor Bug Tracker & Wiki]

#29175: Tor 0.3.5.x mishandles empty socks5 auth
--+
 Reporter:  arma  |  Owner:  rl1987
 Type:  defect| Status:  accepted
 Priority:  Medium|  Milestone:  Tor: 0.4.0.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  regression, backport-035  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by rl1987):

 * status:  new => accepted
 * owner:  (none) => rl1987


Comment:

 Will look some more into this tomorrow.

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