Re: [tor-bugs] #26429 [Applications/Tor Browser]: Add native OnionShare support

2018-06-22 Thread Tor Bug Tracker & Wiki
#26429: Add native OnionShare support
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  reopened
 Priority:  Low   |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Thank you for trying to adding a new backdoor. As a FBI coworker we will
 appreciate it so PLEASE DO :)

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

Re: [tor-bugs] #26429 [Applications/Tor Browser]: Add native OnionShare support

2018-06-22 Thread Tor Bug Tracker & Wiki
#26429: Add native OnionShare support
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  reopened
 Priority:  Low   |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Before:
 $ scandir /torbrowser/profile | findstr ".onion"
 0 result

 After:
 $ scandir /torbrowser/profile | findstr ".onion"
 10 result

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24249 [Core Tor/Tor]: Create automated mechanism for C/Rust types to stay in sync

2018-06-22 Thread Tor Bug Tracker & Wiki
#24249: Create automated mechanism for C/Rust types to stay in sync
--+---
 Reporter:  chelseakomlo  |  Owner:  chelseakomlo
 Type:  enhancement   | Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust  |  Actual Points:
Parent ID:| Points:
 Reviewer:  isis  |Sponsor:
--+---

Comment (by chelseakomlo):

 Ok, here is the overall difference between using bindgen (C to Rust) or a
 custom tool (Rust to C).

 == Bindgen (C to Rust):

 Takes C data types and generates FFI bindings for them. https://rust-lang-
 nursery.github.io/rust-bindgen

 As shown in their documentation, a struct in C such as:
 {{{
 typedef struct Person {
 int height;
 char *name;
 } Person;
 }}}

 Becomes in Rust:
 {{{
 #[repr(C)]
 #[derive(Debug, Copy)]
 pub struct Person {
 pub height: ::std::os::raw::c_int,
 pub name: *mut ::std::os::raw::c_char,
 }
 }}}

 and a constant in C

 {{{
 #define PERSON_NAME "HELLO";
 }}}

 becomes in Rust:
 {{{
 pub const PERSON_NAME: &'static [u8; 6usize] = b"HELLO\x00";
 }}}

 If we were to use bindgen, we could generate types, but we would still
 need to write wrapper "glue" to translate specific libc types into Rust
 types (such as a *mut c_char into a String, smartlists into vectors, etc).

 Advantages of using bindgen:
 - Using a library we don't have to maintain
 - Ability to autogenerate multiple types (functions, structs, enums, etc).

 Disadvantages of using bindgen:
 - Hand-writing FFI type translation code
 - More FFI code which is unsafe and (for now) often requires copies

 == Custom library (Rust to C):
 (something like `http://github.com/chelseakomlo/types-parser`)

 Takes Rust data types and generates C equivilant types.

 For example, a struct in Rust such as:
 {{{
 struct Person {
 height: i32,
 name: String,
 }
 }}}

 could be autogenerated to the following struct in C:
 {{{
 typedef struct Person {
 int height;
 char *name;
 } Person;
 }}}

 and a constant in Rust:

 {{{
 const FIRST_CONTSTANT: &'static str = "first_constant";
 }}}

 becomes in C:
 {{{
 #define FIRST_CONTSTANT first_constant
 }}}

 Advantages of using a custom library:
 - Compile types into Rust and C without further translation/error handling
 code

 Disadvantages of using a custom library:
 - Maintain our own library
 - Effort to scale out features. Currently supporting only constants is
 simple, but adding new data types will be effort. (for example, structs
 with smartlists as fields won't be the easiest to compile, I think)

 == Overall Thoughts:

 While I'm not crazy about maintaining our own library, I do prefer the
 option of being able to cleanly keep Rust and C types separate without the
 need to hand write FFI type-conversion glue. However, both approaches
 certainly have drawbacks, and overall this effort should be minimal as we
 are striving to keep the Rust/C FFI interface small to begin with.

 Considering currently we mainly need to keep constants and enums in sync,
 both options are relatively equal. The complexity for both increases for
 more complex of data types to keep in sync.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26463 [- Select a component]: IndexedDB doesn't work in TorBrowser

2018-06-22 Thread Tor Bug Tracker & Wiki
#26463: IndexedDB doesn't work in TorBrowser
--+
 Reporter:  luka-magnotta |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 Replying to [ticket:26463 luka-magnotta]:
 > So, I've read #16528 and #1633, but I'm still unclear if the current
 state of IndexedDB being broken is intended or not.
 >
 > Just to be clear: TB 7.5.5 (FF 52.8.1), IndexedDB doesn't work at all.
 It exhibits symptoms similar to vanilla FF in Private Mode -- the API
 appears to exist, but the first call to "open" fails with
 InvalidStateError.

 Tor Browser runs all windows in private browsing mode by default.

 So IndexedDB probably needs to get fixed in Firefox before it will be
 fixed in TBB. Even then, TBB will need to make sure that it respects
 domain isolation.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26462 [Applications/Tor Browser]: Build of firefox 60.1.0 fails on linux32

2018-06-22 Thread Tor Bug Tracker & Wiki
#26462: Build of firefox 60.1.0 fails on linux32
-+-
 Reporter:  boklm|  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, tbb-rbm,   |  Actual Points:
  TorBrowserTeam201806R, GeorgKoppen201806   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by boklm):

 Replying to [comment:2 gk]:
 > Replying to [comment:1 boklm]:
 > > GeKo suggested disabling stylo in the linux32 build, as a workaround
 until we have more time to fix the underlying problem. So I am now trying
 a build with stylo disabled.
 >
 > That's not enough due to libxul linking errors. Apart from that I think
 I have a better idea: let's just omit the 32bit debug info for Firefox for
 now. It seems to me not that important anyway, given that we have 64bit
 debug symbols for Linux and it allows to keep our build configuration at
 least as far as end users are concerned and as far as we have shipped
 bundles in our nightlies over the past couple of weeks.
 >
 > `bug_26462` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_26462=71b71dbabf48db4b1a986b979f01d9bf6c79c30d)
 in my public `tor-browser-build` repo has a patch for review which works
 for me.

 There is a typo in the commit message: nightlis instead of nightlies.

 Otherwise the patch looks 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] #26318 [Applications/Tor Browser]: TBA - Consider different installation methods

2018-06-22 Thread Tor Bug Tracker & Wiki
#26318: TBA - Consider different installation methods
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by dmr):

 F-Droid //client// (specifically Bazaar) is a great "offline" app store.

 I haven't follow the progress of the project in a while, but it does allow
 for these sorts of things:
 * peer-to-peer app distribution over wifi
 * peer-to-peer app distribution over bluetooth
 * peer-to-peer app distribution over NFC, Android Beam
 * peer-to-peer app verification
 * `.onion` repos
 * sharing repo identities in person
 Not the //client//, but also part of the F-Droid ecosystem:
 * trusted repos created with `Repomaker`, a web-based UI (not yet ready
 for production)

 While arguably we can't get everyone to use F-Droid, I just wanted to
 point out that they have designed it much with these use cases and
 problems in mind.
 I believe we should focus some resources on educating users about these
 peer-to-peer options, so that they can leverage existing trust
 relationships within communities.

 References:
 * [[https://f-droid.org/en/tutorials/swap/|Tutorials - How to Send and
 Receive Apps Offline]]
 * [[https://f-droid.org/en/tutorials/add-repo/|Tutorials - How to Add a
 Repo to F-Droid]] - **specifically see `Option 2: Scan a QR Code from
 Another Device`**
 * [[https://f-droid.org/en/docs/FAQ_-_Client/#how-do-i-send-a-repo-
 configuration-using-nfc|FAQ - How do I send a Repo configuration using
 NFC?]]
 * [[https://f-droid.org/en/docs/FAQ_-_Client/#how-can-i-send-the-f-droid-
 app-using-nfc-or-android-beam|FAQ - How can I send the F-Droid app using
 NFC or Android Beam?]]
 * [[https://f-droid.org/en/2018/02/02/linux-conf-au-fdroid-
 presentation.html|2018 F-Droid presentation talking about collateral
 freedom, among other things]]
 * [[https://f-droid.org/en/2017/07/03/cuba.html|2017 blog post on F-Droid
 app sharing in Cuba]]
 * [[https://dev.guardianproject.info/projects/bazaar/wiki/|Bazaar project
 wiki]]
 * [[https://f-droid.org/en/repomaker/|Repomaker (not yet ready for
 production)]]
 * [[https://guardianproject.info/2017/06/29/repomaker-usability-trainers-
 worldwide-june-2017/|2017 Repomaker usability study]]

 It's worth noting that The Guardian Project has
 
[[https://guardianproject.info/fdroid/repo/?fingerprint=B7C2EEFD8DAC7806AF67DFCD92EB18126BC08312A7F2D6F3862E46013C7A6135|F-Droid
 repos on multiple distribution channels/platforms]]:
 * direct HTTPS
 * `.onion`
 * AWS S3 (so provides the collateral censorship-resistance properties
 //akin to// domain fronting)

 On a different note, there is also the `App Updater` / update detector
 framework that may be of use for non-F-Droid devices (iiuc):
 * [[https://f-droid.org/en/2017/06/01/announcing-new-libraries-f-droid-
 update-channels.html|Introductory blog post]]
 * [[https://gitlab.com/fdroid/update-channels|Gitlab repo]]
 * [[https://gitlab.com/fdroid/update-
 channels/blob/master/appupdater/README.markdown|README.markdown]]
 ([[https://gitlab.com/fdroid/update-
 channels/raw/master/appupdater/README.markdown|raw, no JS required]])
 It's not necessarily relevant for the //first// download/install, but it
 may be helpful nonetheless in the broader scope of things.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26462 [Applications/Tor Browser]: Build of firefox 60.1.0 fails on linux32

2018-06-22 Thread Tor Bug Tracker & Wiki
#26462: Build of firefox 60.1.0 fails on linux32
-+-
 Reporter:  boklm|  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, tbb-rbm,   |  Actual Points:
  TorBrowserTeam201806R, GeorgKoppen201806   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by gk):

 FWIW: https://bugzilla.mozilla.org/show_bug.cgi?id=1401093 has quite some
 useful considerations, for instance glandium's comment:
 {{{
 Well, linux distros tend to not cross-build so they would build 32-bits
 binaries on 32-bits OSes. What I do on Debian is add -Wl,--reduce-memory-
 overheads -Wl,--no-keep-memory to LDFLAGS. Maybe we could do that
 automatically.
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26462 [Applications/Tor Browser]: Build of firefox 60.1.0 fails on linux32

2018-06-22 Thread Tor Bug Tracker & Wiki
#26462: Build of firefox 60.1.0 fails on linux32
-+-
 Reporter:  boklm|  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, tbb-rbm,   |  Actual Points:
  TorBrowserTeam201806R, GeorgKoppen201806   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

 * keywords:  TorBrowserTeam201806 => ff60-esr, tbb-rbm,
 TorBrowserTeam201806R, GeorgKoppen201806
 * status:  new => needs_review


Comment:

 Replying to [comment:1 boklm]:
 > GeKo suggested disabling stylo in the linux32 build, as a workaround
 until we have more time to fix the underlying problem. So I am now trying
 a build with stylo disabled.

 That's not enough due to libxul linking errors. Apart from that I think I
 have a better idea: let's just omit the 32bit debug info for Firefox for
 now. It seems to me not that important anyway, given that we have 64bit
 debug symbols for Linux and it allows to keep our build configuration at
 least as far as end users are concerned and as far as we have shipped
 bundles in our nightlies over the past couple of weeks.

 `bug_26462` (https://gitweb.torproject.org/user/gk/tor-browser-
 build.git/commit/?h=bug_26462=71b71dbabf48db4b1a986b979f01d9bf6c79c30d)
 in my public `tor-browser-build` repo has a patch for review which works
 for 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] #26318 [Applications/Tor Browser]: TBA - Consider different installation methods

2018-06-22 Thread Tor Bug Tracker & Wiki
#26318: TBA - Consider different installation methods
--+--
 Reporter:  sysrqb|  Owner:  tbb-team
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dmr):

 * cc: dmr (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] #26242 [Applications/Tor Browser]: Implement update strategy for TBA

2018-06-22 Thread Tor Bug Tracker & Wiki
#26242: Implement update strategy for TBA
--+--
 Reporter:  igt0  |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  tbb-mobile|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dmr):

 * cc: dmr (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] #26319 [Applications/Tor Browser]: Don't package up the whole Tor Browser in the `mach package` step

2018-06-22 Thread Tor Bug Tracker & Wiki
#26319: Don't package up the whole Tor Browser in the `mach package` step
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:
 |  needs_review
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201806,  |  Actual Points:
  tbb-rbm|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by sukhbir):

 * status:  new => needs_review


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

Re: [tor-bugs] #26225 [Core Tor/Stem]: Jenkins test failure: test_get_microdescriptors - test may be unreliable

2018-06-22 Thread Tor Bug Tracker & Wiki
#26225: Jenkins test failure: test_get_microdescriptors - test may be unreliable
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  needs_review
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords:  testing|  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:
---+--
Changes (by dmr):

 * status:  assigned => needs_review


Comment:

 I tried for a while to reproduce this, but wasn't able to.
 However, some of the test output tripped me up to the potential cause.

 So I've pushed a set of changes that I //think// will make this test more
 reliable.
 [[https://github.com/torproject/stem/pull/3|GitHub pull request]] (branch
 head `6ddc67f62689e5b34a1a969a1d022c3c653599b5`)

 I dug into the original implementation of `get_microdescriptors()` and the
 evolution of its test case, just to try to understand if something more
 was going on here. As far as I can reason about this without reproducing
 the failure, these are appropriate changes to make. Please feel free to
 take all or a subset!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26319 [Applications/Tor Browser]: Don't package up the whole Tor Browser in the `mach package` step

2018-06-22 Thread Tor Bug Tracker & Wiki
#26319: Don't package up the whole Tor Browser in the `mach package` step
-+-
 Reporter:  gk   |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  ff60-esr, TorBrowserTeam201806,  |  Actual Points:
  tbb-rbm|
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by sukhbir):

 For review:

 https://github.com/azadi/tor-browser-build-1/commits/bug-26319

 From the commit message:

 {{{
 Bug 26319: Don't package up the whole Tor Browser in the `mach package`
 step

 This commit sets `mach build stage-package` instead of `mach package` in
 the Firefox build; this helps us to use the useful properties of `mach
 package` but avoids creating the final DMG or EXE during the Firefox
 build which we don't want as we do that later when building Tor Browser.

 We no longer need to patch `installer.py` (bug 26205) but we still need
 the patch for the uninstaller otherwise the Firefox build fails trying
 to find the required NSIS files.
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26225 [Core Tor/Stem]: Jenkins test failure: test_get_microdescriptors - test may be unreliable

2018-06-22 Thread Tor Bug Tracker & Wiki
#26225: Jenkins test failure: test_get_microdescriptors - test may be unreliable
---+--
 Reporter:  dmr|  Owner:  dmr
 Type:  defect | Status:  assigned
 Priority:  Medium |  Milestone:
Component:  Core Tor/Stem  |Version:
 Severity:  Normal | Resolution:
 Keywords:  testing|  Actual Points:
Parent ID: | Points:
 Reviewer:  atagar |Sponsor:
---+--
Changes (by dmr):

 * status:  new => assigned
 * reviewer:   => atagar
 * owner:  atagar => dmr
 * cc: atagar (added)


Comment:

 Can't assign and switch status in the same step, so here's an intermediate
 edit.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25583 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Wrong host in Booklooker.de.xml

2018-06-22 Thread Tor Bug Tracker & Wiki
#25583: Wrong host in Booklooker.de.xml
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:  invalid
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by legind):

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


Comment:

 GitHub is the canonical place for ruleset issues:
 https://github.com/EFForg/https-everywhere/issues/15866

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26430 [Applications/Tor Browser]: New torbutton icons

2018-06-22 Thread Tor Bug Tracker & Wiki
#26430: New torbutton icons
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201806R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by arthuredelstein):

 * keywords:   => TorBrowserTeam201806R
 * status:  new => needs_review


Comment:

 Here's a patch for review:

 https://github.com/arthuredelstein/torbutton/commit/26430

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26464 [- Select a component]: Static cross-compiling for Windows is broken

2018-06-22 Thread Tor Bug Tracker & Wiki
#26464: Static cross-compiling for Windows is broken
--+--
 Reporter:  Hello71   |  Owner:  Hello71
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by Hello71):

 https://cgit.alxu.ca/tor.git/commit/?h=bug26464

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26376 [Core Tor/Tor]: add cross compiling docs

2018-06-22 Thread Tor Bug Tracker & Wiki
#26376: add cross compiling docs
--+--
 Reporter:  Hello71   |  Owner:  Hello71
 Type:  enhancement   | Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:  Tor: unspecified
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:  catalyst  |Sponsor:
--+--
Changes (by Hello71):

 * status:  assigned => needs_review


Comment:

 Updated to add MXE instructions. It works fairly well after fixing #26464.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26464 [- Select a component]: Static cross-compiling for Windows is broken

2018-06-22 Thread Tor Bug Tracker & Wiki
#26464: Static cross-compiling for Windows is broken
--+--
 Reporter:  Hello71   |  Owner:  Hello71
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by Hello71):

 * status:  assigned => needs_review


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

[tor-bugs] #26464 [- Select a component]: Static cross-compiling for Windows is broken

2018-06-22 Thread Tor Bug Tracker & Wiki
#26464: Static cross-compiling for Windows is broken
--+--
 Reporter:  Hello71   |  Owner:  Hello71
 Type:  defect| Status:  assigned
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 two issues:

 1. TOR_OPENSSL_LIBS doesn't include $TOR_LIB_GDI $TOR_LIB_WS32.

 2. openssl checking doesn't include -lz.

 IMO, both should be fixed by using pkg-config. however, I don't feel like
 that much pain, so I just made this hacky patch:

 {{{
 diff --git a/configure.ac b/configure.ac
 index 30f8e63ec..15f4058da 100644
 --- a/configure.ac
 +++ b/configure.ac
 @@ -672,15 +672,18 @@ if test "$bwin32" = "true"; then
# think it's actually necessary.
TOR_LIB_GDI=-lgdi32
TOR_LIB_USERENV=-luserenv
 +  TOR_LIB_ZLIB=-lz
  else
TOR_LIB_WS32=
TOR_LIB_GDI=
TOR_LIB_USERENV=
 +  TOR_LIB_ZLIB=
  fi
  AC_SUBST(TOR_LIB_WS32)
  AC_SUBST(TOR_LIB_GDI)
  AC_SUBST(TOR_LIB_IPHLPAPI)
  AC_SUBST(TOR_LIB_USERENV)
 +AC_SUBST(TOR_LIB_ZLIB)

  tor_libevent_pkg_redhat="libevent"
  tor_libevent_pkg_debian="libevent-dev"
 @@ -812,7 +815,7 @@ AC_ARG_WITH(ssl-dir,
])

  AC_MSG_NOTICE([Now, we'll look for OpenSSL >= 1.0.1])
 -TOR_SEARCH_LIBRARY(openssl, $tryssldir, [-lssl -lcrypto $TOR_LIB_GDI
 $TOR_LIB_WS32],
 +TOR_SEARCH_LIBRARY(openssl, $tryssldir, [-lssl -lcrypto $TOR_LIB_GDI
 $TOR_LIB_WS32 $TOR_LIB_ZLIB],
  [#include 
   char *getenv(const char *);],
  [struct ssl_cipher_st;
 @@ -833,10 +836,10 @@ if test "$enable_static_openssl" = "yes"; then
 if test "$tor_cv_library_openssl_dir" = "(system)"; then
   AC_MSG_ERROR("You must specify an explicit --with-openssl-dir=x
 option when using --enable-static-openssl")
 else
 - TOR_OPENSSL_LIBS="$TOR_LIBDIR_openssl/libssl.a
 $TOR_LIBDIR_openssl/libcrypto.a"
 + TOR_OPENSSL_LIBS="$TOR_LIBDIR_openssl/libssl.a
 $TOR_LIBDIR_openssl/libcrypto.a $TOR_LIB_GDI $TOR_LIB_WS32 $TOR_LIB_ZLIB"
 fi
  else
 - TOR_OPENSSL_LIBS="-lssl -lcrypto"
 + TOR_OPENSSL_LIBS="-lssl -lcrypto $TOR_LIB_GDI $TOR_LIB_WS32
 $TOR_LIB_ZLIB"
  fi
  AC_SUBST(TOR_OPENSSL_LIBS)
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26463 [- Select a component]: IndexedDB doesn't work in TorBrowser

2018-06-22 Thread Tor Bug Tracker & Wiki
#26463: IndexedDB doesn't work in TorBrowser
--+
 Reporter:  luka-magnotta |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  - Select a component  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 So, I've read #16528 and #1633, but I'm still unclear if the current state
 of IndexedDB being broken is intended or not.

 Just to be clear: TB 7.5.5 (FF 52.8.1), IndexedDB doesn't work at all. It
 exhibits symptoms similar to vanilla FF in Private Mode -- the API appears
 to exist, but the first call to "open" fails with InvalidStateError. TB
 has a 'dom.indexedDB.enabled` config boolean. It's set to enabled, yet it
 doesn't help at all.

 On firefox side of things, there's
 https://bugzilla.mozilla.org/show_bug.cgi?id=781982 - they break IndexedDB
 in private mode *on purpose* and plan to fix this sometime in the future.
 There's also a bug/workaround - IndexedDB in FF private mode is still
 accessible from WebWorkers. Similar fix/workaround IS not applicable in TB
 - again, on purpose, from #16333.

 So, I'm quite unsure what the status here is, but it would be great to fix
 and enable IndexedDB once and for all, as more and more sites rely on 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] #21863 [Applications/Tor Browser]: Ensure proxy safety on Android

2018-06-22 Thread Tor Bug Tracker & Wiki
#21863: Ensure proxy safety on Android
-+-
 Reporter:  gk   |  Owner:  sysrqb
 Type:  defect   | Status:
 |  accepted
 Priority:  Very High|  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-mobile, tbb-7.0-must, tbb-   |  Actual Points:
  proxy-bypass, TorBrowserTeam201806 |
Parent ID:  #5709| Points:
 Reviewer:   |Sponsor:
 |  Sponsor4
-+-

Comment (by sysrqb):

 In addition, I went down the rabbit hole: "What does Android *do* when you
 ask it to establish a connection using a proxy". The result of this long
 and windy path is "it seems safe", but only when the Java/Dalvik/ART VM
 uses the default AOSP configuration.

 I'll attempt succinctly explaining proxy safety on Android here, but we
 should seriously consider using Necko for all networking calls in the
 future (which means exposing necko via jni). I believe GeckoView is
 already considering this - but how hard could it be? :)

 As an example, let's look at [[https://dxr.mozilla.org/mozilla-
 
esr60/source/mobile/android/base/java/org/mozilla/gecko/updater/UpdateService.java#388|Fennec's
 Updater download]] logic. Fennec uses the wrapper
 `org.mozilla.gecko.util.ProxySelector.openConnectionWithProxy(java.net.URI)`
 most places. This provides [[https://dxr.mozilla.org/mozilla-
 
esr60/source/mobile/android/geckoview/src/main/java/org/mozilla/gecko/util/ProxySelector.java#31|a
 central location]] where Fennec decides if a connection should be
 establishing via a proxy or if the connection should be direct. When
 `openConnectionWithProxy()` is called, Fennec asks the Dalvik/Art system
 for the currently configured proxies. From the list of returned proxies,
 Fennec chooses the first one. (Unfortunately, it seems like Fennec doesn't
 configure a proxy, it must be configured somewhere else).

 `openConnectionWithProxy()` calls
 `java.net.URL::openConnection(java.net.Proxy)`. This is the entrance into
 the Android SDK.
 
[[https://developer.android.com/reference/java/net/URL.html#openConnection(java.net.Proxy)|openConnection()]]
 establishes the
 
[[https://android.googlesource.com/platform/libcore/+/master/ojluni/src/main/java/java/net/URL.java#1038|initial
 connection]] by passing the request onto another library. The protocol
 
[[https://android.googlesource.com/platform/libcore/+/master/ojluni/src/main/java/java/net/URL.java#226|handler]]
 is dynamically found when the URL object is
 
[[https://android.googlesource.com/platform/libcore/+/master/ojluni/src/main/java/java/net/URL.java#604|instantiated]]
 (and statically cached after that). It retrieves a list of protocol
 handlers from the
 
[[https://android.googlesource.com/platform/libcore/+/master/ojluni/src/main/java/java/net/URL.java#1190|system
 properties]]. This list may be
 
[[https://developer.android.com/reference/java/lang/System.html#getProperties()|empty]].
 If the list is empty, or the system doesn't have a handler for the
 specific protocol, then it checks a set of
 
[[https://android.googlesource.com/platform/libcore/+/master/ojluni/src/main/java/java/net/URL.java#1225|default
 handlers]]. For the sake of simplicity, let's assume we're requesting a
 connection using the `http` protocol. That protocol defaults to using
 
[[https://android.googlesource.com/platform/libcore/+/master/ojluni/src/main/java/java/net/URL.java#1286|com.android.okhttp.HttpHandler]].
 At this point, we go into the `okhttp` library with a call into its
 
[[https://android.googlesource.com/platform/libcore/+/master/ojluni/src/main/java/java/net/URL.java#1055|URLStreamHandler:openConnection()]]
 method. This brings us
 
[[https://android.googlesource.com/platform/external/okhttp/+/master/android/main/java/com/squareup/okhttp/HttpHandler.java#68|here]].

 The `HttpHandler` instantiates a helper `OkHttpClient` client which is
 responsible for the connection. The proxy is
 
[[https://android.googlesource.com/platform/external/okhttp/+/master/android/main/java/com/squareup/okhttp/HttpHandler.java#93|explicitly]]
 
[[https://android.googlesource.com/platform/external/okhttp/+/master/android/main/java/com/squareup/okhttp/HttpHandler.java#68|set]],
 as well. From here, the newly instantiated connection is returned down the
 stack. The requested connect is established when the caller requests the
 [[https://android.googlesource.com/platform/external/okhttp/+/master
 /okhttp-
 

Re: [tor-bugs] #26327 [Core Tor/Tor]: Add Vagrant configurations for multiple different systems to contrib

2018-06-22 Thread Tor Bug Tracker & Wiki
#26327: Add Vagrant configurations for multiple different systems to contrib
+--
 Reporter:  rl1987  |  Owner:  (none)
 Type:  enhancement | Status:  new
 Priority:  Low |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:  Tor:
|  unspecified
 Severity:  Minor   | Resolution:
 Keywords:  vagrant dev-tools compilation easy  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--

Comment (by chelseakomlo):

 Ok, I'm going to close this ticket as a wontfix.

 If someone is interested in further working on this, please feel free to
 add it to
 https://trac.torproject.org/projects/tor/wiki/community/relay_infrastructure,
 we will use this page as a way for people to discover useful
 infrastructure projects like this.

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

Re: [tor-bugs] #26327 [Core Tor/Tor]: Add Vagrant configurations for multiple different systems to contrib

2018-06-22 Thread Tor Bug Tracker & Wiki
#26327: Add Vagrant configurations for multiple different systems to contrib
+--
 Reporter:  rl1987  |  Owner:  (none)
 Type:  enhancement | Status:  closed
 Priority:  Low |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:  Tor:
|  unspecified
 Severity:  Minor   | Resolution:  wontfix
 Keywords:  vagrant dev-tools compilation easy  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by chelseakomlo):

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


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26455 [Core Tor/Tor]: use correct CARGO_HOME in test_rust.sh

2018-06-22 Thread Tor Bug Tracker & Wiki
#26455: use correct CARGO_HOME in test_rust.sh
--+
 Reporter:  catalyst  |  Owner:  catalyst
 Type:  defect| Status:
  |  needs_review
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust, tor-ci, tor-test, fast-fix  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by catalyst):

 Replying to [comment:2 chelseakomlo]:
 > Good catch. We also set CARGO_HOME in `Makefile.in` so this should
 likely be updated as well?
 Maybe not in a backported patch? I think the `cargo build` invocations
 happen to work by accident right now because they `cd` into the directory
 that contains the (autoconf-generated) `.cargo` directory in the build
 tree.

 I think it's probably better to clean up the other build instances of this
 problem on a separate ticket, because it's fortuitously working right now.

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

Re: [tor-bugs] #26462 [Applications/Tor Browser]: Build of firefox 60.1.0 fails on linux32

2018-06-22 Thread Tor Bug Tracker & Wiki
#26462: Build of firefox 60.1.0 fails on linux32
--+--
 Reporter:  boklm |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201806  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by boklm):

 GeKo suggested disabling stylo in the linux32 build, as a workaround until
 we have more time to fix the underlying problem. So I am now trying a
 build with stylo disabled.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26430 [Applications/Tor Browser]: New torbutton icons

2018-06-22 Thread Tor Bug Tracker & Wiki
#26430: New torbutton icons
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Replying to [comment:3 antonela]:
 > trac doesn't trust me to upload .svg files
 Or upload it to https://catbox.moe then web archive it with
 https://web.archive.org/save/*

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26462 [Applications/Tor Browser]: Build of firefox 60.1.0 fails on linux32

2018-06-22 Thread Tor Bug Tracker & Wiki
#26462: Build of firefox 60.1.0 fails on linux32
--+
 Reporter:  boklm |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very High |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
  |  TorBrowserTeam201806
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 My build of tor-browser `tbb-8.0a9-build1` fails on linux32 with the
 following error:
 {{{
 22:10.69 libdom_canvas.a.desc
 23:08.63Compiling geckoservo v0.0.1 (file:///var/tmp/build/firefox-
 c6cbbca92205/servo/ports/geckolib)
 24:15.11Compiling gkrust-shared v0.1.0 (file:///var/tmp/build/firefox-
 c6cbbca92205/toolkit/library/rust/shared)
 24:15.57Compiling gkrust v0.1.0 (file:///var/tmp/build/firefox-
 c6cbbca92205/toolkit/library/rust)
 26:11.74 error: failed to build archive: Cannot allocate memory
 26:11.74
 26:11.74 error: aborting due to previous error
 26:11.74
 26:11.77 error: Could not compile `gkrust`.
 26:11.77
 26:11.77 To learn more, run the command again with --verbose.
 26:11.77 make[4]: *** [force-cargo-library-build] Error 101
 26:11.77 make[3]: *** [toolkit/library/rust/target] Error 2
 26:11.77 make[2]: *** [compile] Error 2
 26:11.77 make[1]: *** [default] Error 2
 26:11.77 make: *** [build] Error 2
 }}}

 It might be related to #26323.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26430 [Applications/Tor Browser]: New torbutton icons

2018-06-22 Thread Tor Bug Tracker & Wiki
#26430: New torbutton icons
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by antonela):

 I just attached a .txt which is the .svg file (trac doesn't trust me to
 upload .svg files)
 You just need to change the file extension.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26430 [Applications/Tor Browser]: New torbutton icons

2018-06-22 Thread Tor Bug Tracker & Wiki
#26430: New torbutton icons
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

 * Attachment "Icon-Tor-Update.txt" 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] #26430 [Applications/Tor Browser]: New torbutton icons

2018-06-22 Thread Tor Bug Tracker & Wiki
#26430: New torbutton icons
--+--
 Reporter:  arthuredelstein   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by antonela):

 * Attachment "Tor Button Update.zip" 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] #26461 [Applications/Tor Browser]: Generating incrementals fails if the release/signed or alpha/signed directory doesn't exist

2018-06-22 Thread Tor Bug Tracker & Wiki
#26461: Generating incrementals fails if the release/signed or alpha/signed
directory doesn't exist
--+--
 Reporter:  boklm |  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  TorBrowserTeam201806R |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by boklm):

 * keywords:  TorBrowserTeam201806 => TorBrowserTeam201806R
 * status:  new => needs_review


Comment:

 This is a patch for review in branch `bug_26461`:
 https://gitweb.torproject.org/user/boklm/tor-browser-
 build.git/commit/?h=bug_26461=45f1b0a0c0e6e4ebe5dc330b2c1ac052838b060f

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26461 [Applications/Tor Browser]: Generating incrementals fails if the release/signed or alpha/signed directory doesn't exist

2018-06-22 Thread Tor Bug Tracker & Wiki
#26461: Generating incrementals fails if the release/signed or alpha/signed
directory doesn't exist
--+
 Reporter:  boklm |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
  |  TorBrowserTeam201806
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Running `make incrementals-alpha` or `make incrementals-release` fails if
 directory `alpha/signed` or `release/signed` does not exist yet.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26186 [Applications/Tor Browser]: Replace usage of `intl.locale.matchOS` in tor-browser's build script

2018-06-22 Thread Tor Bug Tracker & Wiki
#26186: Replace usage of `intl.locale.matchOS` in tor-browser's build script
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  needs_review
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ff60-esr  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by sukhbir):

 * status:  new => needs_review


Comment:

 For review:

 https://github.com/azadi/tor-browser-build-1/tree/bug-26186

 This one is just a one-line change so I thought to get it out of the way.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #507 [Core Tor/Tor]: tor-gencert linked against event/pthread

2018-06-22 Thread Tor Bug Tracker & Wiki
#507: tor-gencert linked against event/pthread
-+-
 Reporter:  weasel   |  Owner:  rl1987
 Type:  defect   | Status:  closed
 Priority:  Very Low |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 |  0.2.0.5-alpha
 Severity:  Normal   | Resolution:  fixed
 Keywords:  automake tor-client tor-common   |  Actual Points:
  refactor modules   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by rl1987):

 * status:  accepted => closed
 * resolution:  None => fixed


Comment:

 It seems that after recent refactoring it no longer links libpthread and
 libevent:

 {{{
 $ objdump -macho -dylibs-used src/tools/tor-gencert
 src/tools/tor-gencert:
 /usr/lib/libz.1.dylib (compatibility version 1.0.0, current
 version 1.2.11)
 /usr/local/lib/libssl.1.1.dylib (compatibility version 1.1.0,
 current version 1.1.0)
 /usr/local/lib/libcrypto.1.1.dylib (compatibility version 1.1.0,
 current version 1.1.0)
 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
 version 1252.200.5)
 }}}

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

Re: [tor-bugs] #21349 [Core Tor/Tor]: Split up very long functions in entrynodes.c

2018-06-22 Thread Tor Bug Tracker & Wiki
#21349: Split up very long functions in entrynodes.c
+--
 Reporter:  nickm   |  Owner:  rl1987
 Type:  defect  | Status:
|  needs_review
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Minor   | Resolution:
 Keywords:  refactor technical-debt tor-client  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by rl1987):

 * status:  accepted => needs_review


Comment:

 https://github.com/torproject/tor/pull/173

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26455 [Core Tor/Tor]: use correct CARGO_HOME in test_rust.sh

2018-06-22 Thread Tor Bug Tracker & Wiki
#26455: use correct CARGO_HOME in test_rust.sh
--+
 Reporter:  catalyst  |  Owner:  catalyst
 Type:  defect| Status:
  |  needs_review
 Priority:  Medium|  Milestone:  Tor:
  |  0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust, tor-ci, tor-test, fast-fix  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by chelseakomlo):

 Good catch. We also set CARGO_HOME in `Makefile.in` so this should likely
 be updated 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] #26459 [Core Tor/Tor]: netinet/tcp.h autoconf test is missing u_int32_t on cygwin

2018-06-22 Thread Tor Bug Tracker & Wiki
#26459: netinet/tcp.h autoconf test is missing u_int32_t on cygwin
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.1-alpha
 Severity:  Minor | Resolution:  wontfix
 Keywords:|  Actual Points:
Parent ID:  #26356| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

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


Comment:

 pastly confirmed on #tor-dev that KIST only works on Linux (and Linux
 Subsystem for Windows).
 Even if we eventually implement it on Cygwin, macOS, or BSD, we'll need a
 different configure test.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19506 [Core Tor/Tor]: Tool to inspect id signing certs

2018-06-22 Thread Tor Bug Tracker & Wiki
#19506: Tool to inspect id signing certs
-+-
 Reporter:  weasel   |  Owner:  rl1987
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  0.3.5.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.4-rc
 Severity:  Normal   | Resolution:
 Keywords:  ed25519 tor-relay monitor tooling|  Actual Points:
  admin-tools|
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * milestone:  Tor: unspecified => Tor: 0.3.5.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] #26451 [HTTPS Everywhere/EFF-HTTPS Everywhere]: HTTPS-Everywhere freezes the browser when entering URLS like ./a.

2018-06-22 Thread Tor Bug Tracker & Wiki
#26451: HTTPS-Everywhere freezes the browser when entering URLS like ./a.
-+-
 Reporter:  gk   |  Owner:  legind
 Type:  defect   | Status:  closed
 Priority:  High |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Major| Resolution:  fixed
 Keywords:  TorBrowserTeam201806R|  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-

Comment (by cypherpunks):

 Impressive response time tho

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18080 [Applications/Tor Browser]: CORS header 'Access-Control-Allow-Origin' missing

2018-06-22 Thread Tor Bug Tracker & Wiki
#18080: CORS header 'Access-Control-Allow-Origin' missing
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-usability-website |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 Replying to [comment:18 cypherpunks]:
 > HTTPSE:
 > {{{
 > 2018.6.13
 >   * Fix CORS issues in Firefox. This bug was previously breaking
 embedded
 > videos or css on many websites. Chrome browser was not affected by
 this
 > bug
 > }}}
 The fix requires  a version of Firefox higher or equal to 59, so the fix
 will only work when the next Tor Browser alpha is released which will be
 based on FF60-esr, so yeah, it's also coming in a couple of days unless .
 . . (You can try out Tor Browser nightly to see if the fix is popping)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26459 [Core Tor/Tor]: netinet/tcp.h autoconf test is missing u_int32_t on cygwin

2018-06-22 Thread Tor Bug Tracker & Wiki
#26459: netinet/tcp.h autoconf test is missing u_int32_t on cygwin
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.1-alpha
 Severity:  Minor | Resolution:
 Keywords:|  Actual Points:
Parent ID:  #26356| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * version:   => Tor: 0.3.3.1-alpha


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26356 [Core Tor/Tor]: Tor 0.3.3.6 fails to compile under cygwin (x86_64)

2018-06-22 Thread Tor Bug Tracker & Wiki
#26356: Tor 0.3.3.6 fails to compile under cygwin (x86_64)
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.1-alpha
 Severity:  Normal| Resolution:
 Keywords:  regression, 033-backport  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * version:   => Tor: 0.3.3.1-alpha


Comment:

 It looks like #26460 causes most of the configure tests to fail.
 We should fix #26460, then try compiling on cygwin again.

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

[tor-bugs] #26460 [Core Tor/Tor]: All autoconf tests that include studio.h fail with a missing ssp.h on cygwin

2018-06-22 Thread Tor Bug Tracker & Wiki
#26460: All autoconf tests that include studio.h fail with a missing ssp.h on
cygwin
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.3.1-alpha
 Severity:  Normal|   Keywords:  regression, 033-backport
Actual Points:|  Parent ID:  #26356
   Points:|   Reviewer:
  Sponsor:|
--+--
 It looks like ssp doesn't actually work on cygwin.
 We should fix the ssp test so it includes studio.h and fails.

 {{{
 configure:10546: checking whether the compiler accepts -fstack-protector-
 all
 configure:10565: gcc -c -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
 -pedantic -Werror -fstack-protector-all  -I${top_srcdir}/src/common
 conftest.c >&5
 configure:10565: $? = 0
 configure:10584: gcc -o conftest.exe -g -O2 -U_FORTIFY_SOURCE
 -D_FORTIFY_SOURCE=2 -pedantic -Werror -fstack-protector-all
 -I${top_srcdir}/src/common  conftest.c  >&5
 configure:10584: $? = 0
 configure:10596: result: yes
 configure:10622: checking whether the compiler accepts -Wstack-protector
 configure:10641: gcc -c -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
 -fstack-protector-all -pedantic -Werror -Wstack-protector
 -I${top_srcdir}/src/common conftest.c >&5
 configure:10641: $? = 0
 configure:10672: result: yes
 configure:10685: checking whether the compiler accepts --param ssp-buffer-
 size=1
 configure:10704: gcc -c -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
 -fstack-protector-all -Wstack-protector -pedantic -Werror --param ssp-
 buffer-size=1  -I${top_srcdir}/src/common conftest.c >&5
 configure:10704: $? = 0
 configure:10735: result: yes
 configure:10749: checking whether the compiler accepts -fPIE
 configure:10768: gcc -c -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
 -fstack-protector-all -Wstack-protector --param ssp-buffer-size=1
 -pedantic -Werror -fPIE  -I${top_srcdir}/src/common conftest.c >&5
 configure:10768: $? = 0
 configure:10799: result: yes
 configure:10811: checking whether the linker accepts -pie
 configure:10854: gcc -o conftest.exe -g -O2 -U_FORTIFY_SOURCE
 -D_FORTIFY_SOURCE=2 -fstack-protector-all -Wstack-protector --param ssp-
 buffer-size=1 -fPIE -pedantic -Werror  -I${top_srcdir}/src/common -pie
 conftest.c  -lz  -levent -lssl -lcrypto  >&5
 In file included from /usr/include/stdio.h:800,
  from conftest.c:78:
 /usr/local/lib/gcc/x86_64-unknown-cygwin/8.1.0/include/ssp/stdio.h:38:10:
 fatal error: ssp.h: No such file or directory
  #include 
   ^~~
 compilation terminated.
 configure:10854: $? = 1
 configure: program exited with status 1
 configure: failed program was:
 | /* confdefs.h */
 | #define PACKAGE_NAME "tor"
 | #define PACKAGE_TARNAME "tor"
 | #define PACKAGE_VERSION "0.3.3.7"

 (similar macros)

 | #define STDC_HEADERS 1
 | #define HAVE_SYS_TYPES_H 1

 (similar macros)

 | /* end confdefs.h.  */
 | #include 
 | int
 | main ()
 | {
 | fputs("", stdout)
 |   ;
 |   return 0;
 | }
 configure:10868: result: no
 }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26356 [Core Tor/Tor]: Tor 0.3.3.6 fails to compile under cygwin (x86_64)

2018-06-22 Thread Tor Bug Tracker & Wiki
#26356: Tor 0.3.3.6 fails to compile under cygwin (x86_64)
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.4.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  regression, 033-backport  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by teor):

 * keywords:   => regression, 033-backport
 * status:  needs_information => new
 * milestone:  Tor: 0.3.3.x-final => Tor: 0.3.4.x-final


Comment:

 I'm opening child tickets for the issues in the log.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26459 [Core Tor/Tor]: netinet/tcp.h autoconf test is missing u_int32_t on cygwin

2018-06-22 Thread Tor Bug Tracker & Wiki
#26459: netinet/tcp.h autoconf test is missing u_int32_t on cygwin
--+--
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Low   |  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Minor |   Keywords:
Actual Points:|  Parent ID:  #26356
   Points:|   Reviewer:
  Sponsor:|
--+--
 I think we need to add sys/types.h on Cygwin, and maybe BSD/macOS as well.
 But if this configure test is only for KIST, and KIST only works on Linux,
 maybe we don't need to fix this issue.

 {{{
 configure:9774: checking for struct tcp_info.tcpi_unacked
 configure:9774: gcc -c -g -O2   -I${top_srcdir}/src/common conftest.c >&5
 In file included from conftest.c:77:
 /usr/include/netinet/tcp.h:42:9: error: unknown type name 'u_int32_t'
  typedef u_int32_t tcp_seq;
  ^

 (similar errors)

 configure:9774: $? = 1
 configure: failed program was:
 | /* confdefs.h */
 | #define PACKAGE_NAME "tor"
 | #define PACKAGE_TARNAME "tor"
 | #define PACKAGE_VERSION "0.3.3.7"

 (similar macros)

 | #define STDC_HEADERS 1
 | #define HAVE_SYS_TYPES_H 1

 (similar macros)

 | /* end confdefs.h.  */
 | #include 
 |
 | int
 | main ()
 | {
 | static struct tcp_info ac_aggr;
 | if (ac_aggr.tcpi_unacked)
 | return 0;
 |   ;
 |   return 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] #507 [Core Tor/Tor]: tor-gencert linked against event/pthread

2018-06-22 Thread Tor Bug Tracker & Wiki
#507: tor-gencert linked against event/pthread
-+-
 Reporter:  weasel   |  Owner:  rl1987
 Type:  defect   | Status:
 |  accepted
 Priority:  Very Low |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 |  0.2.0.5-alpha
 Severity:  Normal   | Resolution:  None
 Keywords:  automake tor-client tor-common   |  Actual Points:
  refactor modules   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by rl1987):

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


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21349 [Core Tor/Tor]: Split up very long functions in entrynodes.c

2018-06-22 Thread Tor Bug Tracker & Wiki
#21349: Split up very long functions in entrynodes.c
+--
 Reporter:  nickm   |  Owner:  rl1987
 Type:  defect  | Status:  accepted
 Priority:  Medium  |  Milestone:  Tor:
|  unspecified
Component:  Core Tor/Tor|Version:
 Severity:  Minor   | Resolution:
 Keywords:  refactor technical-debt tor-client  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+--
Changes (by rl1987):

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


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

Re: [tor-bugs] #19506 [Core Tor/Tor]: Tool to inspect id signing certs

2018-06-22 Thread Tor Bug Tracker & Wiki
#19506: Tool to inspect id signing certs
-+-
 Reporter:  weasel   |  Owner:  rl1987
 Type:  enhancement  | Status:
 |  needs_review
 Priority:  High |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:  Tor:
 |  0.2.8.4-rc
 Severity:  Normal   | Resolution:
 Keywords:  ed25519 tor-relay monitor tooling|  Actual Points:
  admin-tools|
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by rl1987):

 * status:  reopened => needs_review


Comment:

 After rebasing and some fixups, I got it working.

 https://github.com/torproject/tor/pull/172

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26356 [Core Tor/Tor]: Tor 0.3.3.6 fails to compile under cygwin (x86_64)

2018-06-22 Thread Tor Bug Tracker & Wiki
#26356: Tor 0.3.3.6 fails to compile under cygwin (x86_64)
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by rolex0815):

 I had a try today with 0.3.3.7.
 Same Probleme as above.

 Last Version running under cygwin is:

 Tor 0.3.2.9 (git-9e8b762fcecfece6) running on CYGWIN_NT-10.0 with Libevent
 2.0.22-stable, OpenSSL 1.0.2o, Zlib 1.2.11, Liblzma 5.2.4, and Libzstd
 N/A.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26356 [Core Tor/Tor]: Tor 0.3.3.6 fails to compile under cygwin (x86_64)

2018-06-22 Thread Tor Bug Tracker & Wiki
#26356: Tor 0.3.3.6 fails to compile under cygwin (x86_64)
--+
 Reporter:  gk|  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by rolex0815):

 * Attachment "config.log" 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] #18080 [Applications/Tor Browser]: CORS header 'Access-Control-Allow-Origin' missing

2018-06-22 Thread Tor Bug Tracker & Wiki
#18080: CORS header 'Access-Control-Allow-Origin' missing
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-usability-website |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 HTTPSE:
 {{{
 2018.6.13
   * Fix CORS issues in Firefox. This bug was previously breaking embedded
 videos or css on many websites. Chrome browser was not affected by
 this
 bug
 }}}

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

Re: [tor-bugs] #25583 [HTTPS Everywhere/EFF-HTTPS Everywhere]: Wrong host in Booklooker.de.xml

2018-06-22 Thread Tor Bug Tracker & Wiki
#25583: Wrong host in Booklooker.de.xml
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * owner:  (none) => legind
 * status:  new => assigned
 * component:  HTTPS Everywhere => HTTPS Everywhere/EFF-HTTPS Everywhere


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20279 [HTTPS Everywhere/EFF-HTTPS Everywhere]: wizards.com archives do not behave as expected

2018-06-22 Thread Tor Bug Tracker & Wiki
#20279: wizards.com archives do not behave as expected
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * status:  new => assigned
 * owner:  (none) => legind
 * component:  HTTPS Everywhere => HTTPS Everywhere/EFF-HTTPS Everywhere


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #25297 [HTTPS Everywhere/EFF-HTTPS Everywhere]: httpse-ruleset-bug with Facebook Pixel Helper 0.7.14

2018-06-22 Thread Tor Bug Tracker & Wiki
#25297: httpse-ruleset-bug with Facebook Pixel Helper 0.7.14
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * owner:  (none) => legind
 * status:  new => assigned
 * component:  HTTPS Everywhere => HTTPS Everywhere/EFF-HTTPS Everywhere


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #20099 [HTTPS Everywhere/EFF-HTTPS Everywhere]: cmu.edu filter silently breaks some forms

2018-06-22 Thread Tor Bug Tracker & Wiki
#20099: cmu.edu filter silently breaks some forms
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:
 Keywords:  httpse-ruleset-bug   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * owner:  (none) => legind
 * status:  new => assigned
 * component:  HTTPS Everywhere => HTTPS Everywhere/EFF-HTTPS Everywhere


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23000 [HTTPS Everywhere/HTTPS Everywhere: Chrome]: HTTPS Everywhere does not work in current versions of SlimJet

2018-06-22 Thread Tor Bug Tracker & Wiki
#23000: HTTPS Everywhere does not work in current versions of SlimJet
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:
 |  assigned
 Priority:  Immediate|  Milestone:
Component:  HTTPS Everywhere/HTTPS Everywhere:   |Version:
  Chrome |
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * status:  new => assigned
 * owner:  (none) => legind
 * component:  HTTPS Everywhere => HTTPS Everywhere/HTTPS Everywhere: Chrome


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #19713 [HTTPS Everywhere/EFF-HTTPS Everywhere]: pixiv's "ugoira" animations don't load with https everywhere

2018-06-22 Thread Tor Bug Tracker & Wiki
#19713: pixiv's "ugoira" animations don't load with https everywhere
-+-
 Reporter:  cypherpunks  |  Owner:  legind
 Type:  defect   | Status:
 |  assigned
 Priority:  Medium   |  Milestone:
Component:  HTTPS Everywhere/EFF-HTTPS   |Version:
  Everywhere |
 Severity:  Normal   | Resolution:
 Keywords:  httpse-ruleset-bug   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * status:  new => assigned
 * owner:  (none) => legind
 * component:  HTTPS Everywhere => HTTPS Everywhere/EFF-HTTPS Everywhere


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18552 [Applications/Tor Browser]: timing oracle for rendezvouz circuits

2018-06-22 Thread Tor Bug Tracker & Wiki
#18552: timing oracle for rendezvouz circuits
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Very Low  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Trivial   | Resolution:
 Keywords:  tbb-linkability   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

 * keywords:  timing performance => tbb-linkability


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

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

2018-06-22 Thread Tor Bug Tracker & Wiki
#22581: Tor browser is crashing on exit on Windows
-+-
 Reporter:  WalrusInAnus |  Owner:  tbb-
 |  team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-crash, tbb-7.0-issues, tbb-  |  Actual Points:
  regression, GeorgKoppen201803, |
  TorBrowserTeam201803   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Should be fixed in the alpha with the backport of the fix for bug 1389967.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26454 [Internal Services/Tor Sysadmin Team]: Please create email alias/forwarding and LDAP for Shane

2018-06-22 Thread Tor Bug Tracker & Wiki
#26454: Please create email alias/forwarding and LDAP for Shane
-+-
 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:
-+-
Changes (by hiro):

 * owner:  (none) => tpa
 * component:  Internal Services/Services Admin Team => Internal
 Services/Tor Sysadmin Team


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

Re: [tor-bugs] #12927 [Applications/Tor Browser]: Include Hebrew translations into TorBrowserBundle

2018-06-22 Thread Tor Bug Tracker & Wiki
#12927: Include Hebrew translations into TorBrowserBundle
-+--
 Reporter:  fr33domlover |  Owner:  tbb-team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  l10n, translation, localization  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by cypherpunks):

 Replying to [comment:4 gk]:
 > Fixed by #20826.
 By #20628.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #26341 [Applications/Tor Browser]: Enable setting torbutton.use_nontor_proxy with an environment variable

2018-06-22 Thread Tor Bug Tracker & Wiki
#26341: Enable setting torbutton.use_nontor_proxy with an environment variable
--+---
 Reporter:  eyedeekay |  Owner:  tbb-team
 Type:  enhancement   | Status:  needs_information
 Priority:  Low   |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Trivial   | Resolution:
 Keywords:  tbb-torbutton |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by eyedeekay):

 OK, so I have taken steps to make sure that I do not misleadingly
 represent this browser configuration based on the Tor Browser as a real
 Tor Browser. Foremost, I've replaced the welcome page completely to
 indicate that it's an i2p browser, with a clear warning "i2p does not do
 domain isolation" with a brief explanation that you will have the same
 identity for all your activity in this browser(page is here:
 https://github.com/eyedeekay/i2p-browser-for-cheaters/blob/master/i2p-
 diffs.html). It may change, but that message will still be conveyed. This
 will be presented 100% of the time when a user starts our i2p browser.
 Besides that, we pass a different wm_class to firefox. I even created a
 re-branding plugin(https://github.com/eyedeekay/ui2pbrowser_branding)
 (just a fork of iceweasel's) that I'd love to be able to use, and am
 investigating paths to using, however there are complications on the path
 to doing this which will take time to overcome. It is something I will
 continue to work on. I hope that this helps to make my patch more
 acceptable.

 As for isolation, for now the approach is warn visibly about the shared
 identity across browser tabs and visibly delineate the differences between
 this and the standard TBB. My motivation for choosing the Tor Browser is
 hardening against metadata leakage and and lowered ability to deduce
 system characteristics using browser features. Even without domain
 isolation, TBB still seems to be the best choice.

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