Re: [tor-bugs] #10573 [Applications/Tor Browser]: `nsILocalFile` should be replaced with `nsIFile` in our extensions

2017-12-17 Thread Tor Bug Tracker & Wiki
#10573: `nsILocalFile` should be replaced with `nsIFile` in our extensions
-+--
 Reporter:  cypherpunks  |  Owner:  tbb-team
 Type:  defect   | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Minor| Resolution:  fixed
 Keywords:  tbb-easy, TorBrowserTeam201712R  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by gk):

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


Comment:

 Thanks. This is commit d3c1b207bb51dcaf477e2d879eb2234282a0 on
 `master` in Torbutton and commit e24ab106dffdf4f0504c2f60005e213ebd47d458
 on `master` in Tor Launcher.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #21847 [Applications/Tor Browser]: Update copy for security slider to be consistent with the mobile experience

2017-12-17 Thread Tor Bug Tracker & Wiki
#21847: Update copy for security slider to be consistent with the mobile 
experience
-+-
 Reporter:  isabela  |  Owner:  tbb-
 |  team
 Type:  enhancement  | Status:  closed
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:  fixed
 Keywords:  tbb-usability, tbb-security-slider,  |  Actual Points:
  TorBrowserTeam201712R, GeorgKoppen201712   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by gk):

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


Comment:

 Replying to [comment:16 mcs]:
 > The followup patch looks good to me.
 > I did notice a small issue today when I ran with the new code on macOS:
 when the Security Settings window first opens, nthe "Learn More" link has
 the keyboard focus. I suppose that is just default XUL behavior (set focus
 to the first element that can have a keyboard focus), but it looks a
 little strange because macOS draws a box around the link. If you think
 this is worth fixing, the following addition to
 `torbutton_init_security_ui()` fixes it:
 > {{{
 >   let okBtn = document.documentElement.getButton("accept");
 >   if (okBtn)
 > okBtn.focus();

 Thanks, this is included in commit
 0e9fe510277aeb8617f9de73d24b85436479f129 on `master` now. The follow-up
 ticket for getting the improvements made here back to mobile is #24653.
 > }}}

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24653 [Applications/Tor Browser]: Apply security slider improvements made on desktop back to mobile

2017-12-17 Thread Tor Bug Tracker & Wiki
#24653: Apply security slider improvements made on desktop back to mobile
-+-
 Reporter:  gk   |  Owner:  tbb-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor |Version:
  Browser|   Keywords:  tbb-mobile, tbb-
 Severity:  Normal   |  torbutton, tbb-security-slider
Actual Points:   |  Parent ID:
   Points:   |   Reviewer:
  Sponsor:   |
-+-
 In #21847 we applied the copy for the mobile security slider back to the
 desktop one. It turns out there is still room for improvement which went
 into the final version for #21847. Now it's time to get those changes
 included into mobile.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24566 [Applications/Tor Browser]: When I open TorBrowser 7.0.11 the popup goes completely white on macOS 10.13.2

2017-12-17 Thread Tor Bug Tracker & Wiki
#24566: When I open TorBrowser 7.0.11 the popup goes completely white on macOS
10.13.2
--+--
 Reporter:  Dbryrtfbcbhgf |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:  TorBrowserTeam201712  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * keywords:   => TorBrowserTeam201712


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24566 [Applications/Tor Browser]: When I open TorBrowser 7.0.11 the popup goes completely white on macOS 10.13.2 (was: When I open TorBrowser 7.0.11 the popup goes completely white)

2017-12-17 Thread Tor Bug Tracker & Wiki
#24566: When I open TorBrowser 7.0.11 the popup goes completely white on macOS
10.13.2
--+--
 Reporter:  Dbryrtfbcbhgf |  Owner:  tbb-team
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by gk):

 * status:  needs_information => closed
 * priority:  High => Medium
 * resolution:   => fixed
 * severity:  Major => Normal


Comment:

 Thanks for tracking this down. I cherry-picked the patch from `mozilla-
 central`. It is commit dca73c105071dc969df0f9d03892c786868d4ee7 on `tor-
 browser-52.5.2esr-7.5-2`. We'll see if Mozilla is backporting it to ESR
 52.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24652 [Core Tor/Tor]: Rust builds fail on macOS with linker error

2017-12-17 Thread Tor Bug Tracker & Wiki
#24652: Rust builds fail on macOS with linker error
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.2.1-alpha
 Severity:  Normal| Resolution:
 Keywords:  rust  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 This is an upstream issue:
 https://github.com/rust-lang/rust/issues/46797

 We can fix it by linking our rust builds to -lresolv.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23881 [Core Tor/Tor]: Implement a way to utilise tor's logging system from Rust code

2017-12-17 Thread Tor Bug Tracker & Wiki
#23881: Implement a way to utilise tor's logging system from Rust code
--+
 Reporter:  isis  |  Owner:  chelseakomlo
 Type:  enhancement   | Status:  needs_review
 Priority:  High  |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust, rust-pilot  |  Actual Points:
Parent ID:| Points:  3
 Reviewer:|Sponsor:
--+
Changes (by chelseakomlo):

 * status:  needs_revision => 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] #23881 [Core Tor/Tor]: Implement a way to utilise tor's logging system from Rust code

2017-12-17 Thread Tor Bug Tracker & Wiki
#23881: Implement a way to utilise tor's logging system from Rust code
--+
 Reporter:  isis  |  Owner:  chelseakomlo
 Type:  enhancement   | Status:  needs_revision
 Priority:  High  |  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust, rust-pilot  |  Actual Points:
Parent ID:| Points:  3
 Reviewer:|Sponsor:
--+

Comment (by chelseakomlo):

 See fixes from Manish's review on the same branch:
 `https://oniongit.eu/network/tor/merge_requests/7`

 A couple thoughts:

 1. Testing

 I wasn't able to test the inline logging function, as I wasn't sure the
 best way how to. I think I could properly test this with a global variable
 that was only defined for unit tests (such as a Cursor, and "log" to
 it in the no-op implementation. However, I ran into issues due to the
 limitation of creating non-struct static types in stable Rust.

 For example, for the following declaration:

 `pub static mut log_cursor: Cursor =
 Cursor::new(Vec::new());`

 I received this error:
 `calls in statics are limited to struct and enum constructors`

 And for this declaration:

 {{{
   struct LastLogged {
 function: Option
 message: Option
   }
 }}}

 I received this error:
 `destructors in statics are an unstable feature`

 Maybe we just need to wait for this feature to land in stable, but it
 would be nice to have the flexibility for functions that are inherently
 hard to test, without having to change the code itself.

 2. Feature flags for `cargo test`

 I am unable to run `cargo test` with a specific flag. For example, I
 wanted to be able to run `cargo test --feature "testing"`, but this flag
 is not applied to other modules as well (i.e, running tests in protover
 will not result in tor_log being compiled with the "testing" flag). I'm
 able to run `cargo test --all-features` but being able to turn on features
 at a fine-grained level for tests would be nice.

 3. Binding compile-time constants to log level macros

 Nick- as for the declaration of log levels in src/common/torlog.h, if we
 can refactor these into compile-time constants (instead of macros) that
 would remove the need to declare _constant for each. Let me know what you
 think, I can help do this refactor.

 For example, instead of binding _LD_NET to LD_NET, we could declare LD_NET
 as a constant directly.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24652 [Core Tor/Tor]: Rust builds fail on macOS with linker error

2017-12-17 Thread Tor Bug Tracker & Wiki
#24652: Rust builds fail on macOS with linker error
--+
 Reporter:  teor  |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |Version:  Tor: 0.3.2.1-alpha
 Severity:  Normal|   Keywords:  rust
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+
 Both my gcc and clang builds get this error:
 https://travis-ci.org/teor2345/tor/jobs/316748503
 https://travis-ci.org/teor2345/tor/jobs/316748509

 {{{
 Undefined symbols for architecture x86_64:

   "_res_9_init", referenced from:

 std::sys::unix::net::res_init_if_glibc_before_2_26::h5cce5181e3d1daee in
 libtor_rust.a(std-
 af00cffd9617c4f1.std13-3c37598e0257c2e4b7713b0956fa5bab.rs.rcgu.o)

 ld: symbol(s) not found for architecture x86_64
 }}}

 The Linux builds are fine, as are the non-Rust macOS builds.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24030 [Core Tor/Tor]: Wrap types in protover.rs

2017-12-17 Thread Tor Bug Tracker & Wiki
#24030: Wrap types in protover.rs
--+
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  rust  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by frewsxcv):

 I haven't contributed to Tor before, but this looks like a ticket I could
 tackle! I'll take a stab a 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] #8897 [Core Tor/Tor]: Faster curve25519 implementation for ntor

2017-12-17 Thread Tor Bug Tracker & Wiki
#8897: Faster curve25519 implementation for ntor
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.4.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, performance, ntor,|  Actual Points:
  curve25519 crypto impl-shopping|
Parent ID:  #9662| Points:  large
 Reviewer:   |Sponsor:
-+-
Changes (by teor):

 * milestone:  Tor: unspecified => Tor: 0.3.4.x-final


Comment:

 Let's think about this in 0.3.4, because the 0.3.3 freeze is only a few
 weeks away.
 We should see if dalek is ready by then.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #8897 [Core Tor/Tor]: Faster curve25519 implementation for ntor

2017-12-17 Thread Tor Bug Tracker & Wiki
#8897: Faster curve25519 implementation for ntor
-+-
 Reporter:  nickm|  Owner:  nickm
 Type:  enhancement  | Status:
 |  needs_revision
 Priority:  Medium   |  Milestone:  Tor:
 |  unspecified
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-relay, performance, ntor,|  Actual Points:
  curve25519 crypto impl-shopping|
Parent ID:  #9662| Points:  large
 Reviewer:   |Sponsor:
-+-

Comment (by Hello71):

 my profiling results indicate that approximately 18% of my x86_64 Fast
 relay's CPU time is spent in curve25519_donna. therefore, using the 7-10%
 number from previously, this optimization will result in overall savings
 of 1.3-1.8%. not huge, but certainly not negligible.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24645 [Community]: Attention: some exit nodes are downgrading HTTPS encryption cipher!

2017-12-17 Thread Tor Bug Tracker & Wiki
#24645: Attention: some exit nodes are downgrading HTTPS encryption cipher!
-+-
 Reporter:  cypherpunks  |  Owner:  alison
 Type:  task | Status:  closed
 Priority:  High |  Milestone:
Component:  Community|Version:
 Severity:  Normal   | Resolution:  invalid
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by yawning):

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


Comment:

 I suggest familiarizing yourself with how TLS negotiates CipherSuites, and
 the purpose of the `Finished` message
 (https://tools.ietf.org/html/rfc5246#section-7.4.9), and if this issue
 personally affects you, to complain to EA about it to get them to change
 their server configuration.

 https://www.ssllabs.com/ssltest/analyze.html?d=signin.ea.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] #24399 [Webpages/Website]: Consistent set of icons for relay flags

2017-12-17 Thread Tor Bug Tracker & Wiki
#24399: Consistent set of icons for relay flags
--+
 Reporter:  irl   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by teor):

 I agree that the alternative version is more distinguishable.
 i think standardising on one symbol or two letters per icon is a good
 thing.

 One more thing I've noticed in the screenshot, that I didn't pick up
 before:

 We use "v6" on the running icons, and "IPv6" on the exit icon.
 Can we see how the exit icon would look with "v6" please?

 (And sorry for the late change.)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24507 [Metrics/Relay Search]: Allow for aggregation property to be selected from list

2017-12-17 Thread Tor Bug Tracker & Wiki
#24507: Allow for aggregation property to be selected from list
--+
 Reporter:  irl   |  Owner:  irl
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by irl):

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


Comment:

 Those changes are more complicated than they need to be.

 All that's really needed is to have a "by AS and CC" button on the
 advanced search page.

 Fixed in 9a4afc8.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24388 [Metrics/Relay Search]: Add unreachable or addresses to details view and a synthetic flag

2017-12-17 Thread Tor Bug Tracker & Wiki
#24388: Add unreachable or addresses to details view and a synthetic flag
--+
 Reporter:  irl   |  Owner:  irl
 Type:  enhancement   | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Metrics/Relay Search  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by irl):

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


Comment:

 Fixed in 6643de6.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24651 [Internal Services/Service - trac]: Rename Metrics/Atlas component to Metrics/Relay Search

2017-12-17 Thread Tor Bug Tracker & Wiki
#24651: Rename Metrics/Atlas component to Metrics/Relay Search
--+
 Reporter:  irl   |  Owner:  irl
 Type:  task  | Status:  closed
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:  fixed
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by irl):

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


Comment:

 I have renamed the component and all tickets have moved to the new
 component along with 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] #24651 [Internal Services/Service - trac]: Rename Metrics/Atlas component to Metrics/Relay Search

2017-12-17 Thread Tor Bug Tracker & Wiki
#24651: Rename Metrics/Atlas component to Metrics/Relay Search
--+--
 Reporter:  irl   |  Owner:  irl
 Type:  task  | Status:  accepted
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by irl):

 * status:  assigned => accepted


Comment:

 I have moved the development wiki page to
 [[org/teams/MetricsTeam/RelaySearch]] and updated links to the new
 component.

 There are no longer any references to the Metrics/Atlas component in the
 Relay Search codebase.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24651 [Internal Services/Service - trac]: Rename Metrics/Atlas component to Metrics/Relay Search

2017-12-17 Thread Tor Bug Tracker & Wiki
#24651: Rename Metrics/Atlas component to Metrics/Relay Search
--+--
 Reporter:  irl   |  Owner:  irl
 Type:  task  | Status:  assigned
 Priority:  Medium|  Milestone:
Component:  Internal Services/Service - trac  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Now that Atlas has been rebranded as Relay Search, the trac component
 should be renamed.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24218 [Metrics/Statistics]: Implement new metrics-web module for IPv6 relay statistics

2017-12-17 Thread Tor Bug Tracker & Wiki
#24218: Implement new metrics-web module for IPv6 relay statistics
+--
 Reporter:  karsten |  Owner:  metrics-team
 Type:  enhancement | Status:  needs_review
 Priority:  Medium  |  Milestone:
Component:  Metrics/Statistics  |Version:
 Severity:  Normal  | Resolution:
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  iwakeh  |Sponsor:
+--

Comment (by irl):

 Is there any indentation or spacing we can do to make it clearer where the
 `magrittr` pipelines begin/end? For the purpose of making formatting,
 building up ggplot2 plots can be treated as the same as a `%>%` so no
 distinction is needed there:

 {{{
 plot_relays_ipv6 <- function(start, end, path) {
   all_relay_data <- read.csv(
 "/srv/metrics.torproject.org/metrics/shared/stats/ipv6servers.csv",
 colClasses = c("valid_after_date" = "Date")) %>%
 filter(server == "relay")
   start_date <- max(as.Date(start), min(all_relay_data$valid_after_date))
   end_date <- min(as.Date(end), max(all_relay_data$valid_after_date),
 Sys.Date() - 2)
   date_breaks <- date_breaks(as.numeric(end_date - start_date))
   all_relay_data %>%
 filter(valid_after_date >= start_date, valid_after_date <= end_date)
 %>%
 group_by(valid_after_date) %>%
 summarize(total = sum(server_count_sum_avg),
   announced = sum(server_count_sum_avg[announced_ipv6 == 't']),
   reachable = sum(server_count_sum_avg[reachable_ipv6_relay == 't']),
   exiting = sum(server_count_sum_avg[exiting_ipv6_relay == 't'])) %>%
 merge(data.frame(valid_after_date = seq(start_date, end_date,
   by = "1 day")), all = TRUE) %>%
 gather(total, announced, reachable, exiting, key = "category",
   value = "count") %>%
 ggplot(aes(x = valid_after_date, y = count, colour = category)) +
 geom_line(size = 1) +
 scale_x_date(name = paste("\nThe Tor Project - ",
   "https://metrics.torproject.org/;, sep = ""),
   labels = date_format(date_breaks$format),
   date_breaks = date_breaks$major,
   date_minor_breaks = date_breaks$minor) +
 scale_y_continuous(name = "") +
 scale_colour_hue(name = "", h.start = 90,
   breaks = c("total", "announced", "reachable", "exiting"),
   labels = c("Total (IPv4) OR", "IPv6 announced OR", "IPv6 reachable
 OR",
 "IPv6 exititing")) +
 expand_limits(y = 0) +
 ggtitle("Relays by IP version") +
 theme(legend.position = "top")
   ggsave(filename = path, width = 8, height = 5, dpi = 150)
 }
 }}}

 Other than that, the R 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] #23518 [Metrics/Atlas]: Turn Atlas into page on Tor Metrics

2017-12-17 Thread Tor Bug Tracker & Wiki
#23518: Turn Atlas into page on Tor Metrics
---+--
 Reporter:  karsten|  Owner:  irl
 Type:  enhancement| Status:  accepted
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords:  metrics-2017   |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by irl):

 Things to be done:

 * Include Relay Search application in `src/main/resources/web/rs/`
 * Update `src/main/resources/web/rs/main.js` to use metrics.tpo resources
 where available
  * Replace the getPosition function in metrics.tpo's bootstrap JS from
 bootstrap 3.3.5
  * Generally all resources should be relative URLs again
 * Modify `src/main/resources/web/jsps/top.jsp` to allow inclusion of extra
 stylesheets
 * Create a stub
 `src/main/java/org/torproject/metrics/web/RelaySearchServlet.java` to
 render a JSP
 * Create a JSP based on RS's index.html at
 `src/main/resources/web/jsps/rs.jsp`
 * Add the servlet and a URL mapping to `src/main/resources/web.xml`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23830 [Metrics/Website]: Update README to get a development environment for metrics-web going

2017-12-17 Thread Tor Bug Tracker & Wiki
#23830: Update README to get a development environment for metrics-web going
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 I found that I also required `tomcat8-annotations-api-8.5.24.jar` but this
 may be due to me using different versions on Debian testing. Next year
 I'll get a Debian stable virtual machine set up for doing
 development/testing on.

 I also had to disable `duplicate="fail"` for the war target in the ant
 script. This is probably suboptimal although I don't really understand
 what that does. Maybe it's only working for me by chance.

 Other than that, using iwakeh's `task-24175-stepbystep` branch, I was able
 to set up a development instance! (:

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24650 [Core Tor/Tor]: Simplify bridge code: do we need separate addr and addport_configured?

2017-12-17 Thread Tor Bug Tracker & Wiki
#24650: Simplify bridge code: do we need separate addr and addport_configured?
--+--
 Reporter:  nickm |  Owner:  (none)
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  refactor bridges
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 Looking at the bridge code, it seems that we have separate
 addrport_configured and addr elements in the bridge_info_t... but that
 there isn't actually a way for them to diverge.  If that's true, we should
 remove one of them as redundant.

 (If they *can* diverge, we should document how that happens, exactly)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24649 [Core Tor/Tor]: Simplify bridge code: do we still need mark-unmark-and-sweep logic?

2017-12-17 Thread Tor Bug Tracker & Wiki
#24649: Simplify bridge code: do we still need mark-unmark-and-sweep logic?
+--
 Reporter:  nickm   |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Milestone:  Tor: unspecified
Component:  Core|Version:
  Tor/Tor   |
 Severity:  Normal  |   Keywords:  refactoring code-removal bridges
Actual Points:  |  Parent ID:
   Points:  |   Reviewer:
  Sponsor:  |
+--
 In an older version of the bridge code, we would encode some state
 information in the bridge_info_t object.  Therefore, when we reloaded the
 configuration, it was important that we use the old object for any bridges
 that we still had.  For that reason, we would (on reloading the
 configuration) first mark all bridges, then unmark any bridges that were
 still in the configuration (while adding any new bridges), and finally
 we'd free all the marked bridges.

 But, looking at the code now, it appears we no longer take this approach:
 once marked_for_removal is set on a bridge, nothing clears it. If that's
 the case, we could simplify our bridge configuration logic a bit by just
 clearing the bridge list and rebuilding it, and dropping this whole
 "marked_for_removal" business.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24501 [Core Tor/Tor]: When we hit MaxMemInQueues, make the log message more quantitative

2017-12-17 Thread Tor Bug Tracker & Wiki
#24501: When we hit MaxMemInQueues, make the log message more quantitative
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  needs_revision
 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 Hello71):

 semi-OT, but I just noticed that some tor commits have Signed-off-by and
 some don't. since Signed-off-by is supposed to be defined per-project,
 this seems like a bad idea.

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

Re: [tor-bugs] #24501 [Core Tor/Tor]: When we hit MaxMemInQueues, make the log message more quantitative

2017-12-17 Thread Tor Bug Tracker & Wiki
#24501: When we hit MaxMemInQueues, make the log message more quantitative
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  needs_revision
 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 Hello71):

 * status:  needs_review => needs_revision
 * cc: alex_y_xu@… (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] #24501 [Core Tor/Tor]: When we hit MaxMemInQueues, make the log message more quantitative

2017-12-17 Thread Tor Bug Tracker & Wiki
#24501: When we hit MaxMemInQueues, make the log message more quantitative
--+
 Reporter:  arma  |  Owner:  (none)
 Type:  defect| Status:  needs_review
 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 Hello71):

 I think the commit summary could be better. "Add numbers to OOM log msg"
 still leaves you with a bunch of characters for other stuff, like the
 ticket number.

 Tor doesn't use Signed-off-by.

 'z' format qualifier isn't used in other places in Tor. I think a
 discussion might be needed before it's introduced. also, %zd is invalid to
 print size_t. use %zu.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #23830 [Metrics/Website]: Update README to get a development environment for metrics-web going

2017-12-17 Thread Tor Bug Tracker & Wiki
#23830: Update README to get a development environment for metrics-web going
-+--
 Reporter:  irl  |  Owner:  metrics-team
 Type:  enhancement  | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Normal   | Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--

Comment (by irl):

 `libpostgresql-jdbc-java` is missing from this list.

 Only `r-cran-rjava` doesn't contains Rserve.jar, but `r-cran-rserve` has
 both.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24277 [Metrics/Website]: Reduce vertical header size

2017-12-17 Thread Tor Bug Tracker & Wiki
#24277: Reduce vertical header size
-+
 Reporter:  Hello71  |  Owner:  irl
 Type:  enhancement  | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Minor| Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+

Comment (by irl):

 Yes, we can. See above. Tested in responsive design view in Firefox, I'm
 unable to find a size where things break.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24277 [Metrics/Website]: Reduce vertical header size

2017-12-17 Thread Tor Bug Tracker & Wiki
#24277: Reduce vertical header size
-+
 Reporter:  Hello71  |  Owner:  irl
 Type:  enhancement  | Status:  needs_revision
 Priority:  Medium   |  Milestone:
Component:  Metrics/Website  |Version:
 Severity:  Minor| Resolution:
 Keywords:   |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+
Changes (by irl):

 * Attachment "0001-Reduces-default-vertical-header-size-
 Fixes-24277.2.patch" 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] #18859 [Core Tor/Tor]: A new SOCKS connection should use a pre-built circuit for its first stream

2017-12-17 Thread Tor Bug Tracker & Wiki
#18859: A new SOCKS connection should use a pre-built circuit for its first 
stream
-+-
 Reporter:  arthuredelstein  |  Owner:
 |  arthuredelstein
 Type:  defect   | Status:
 |  merge_ready
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tbb-performance, tor-client, |  Actual Points:
  performance, 031-backport  |
Parent ID:   | Points:
 Reviewer:  nickm|Sponsor:
-+-
Changes (by cypherpunks):

 * keywords:  tbb-performance tor-client  performance  031-backpot => tbb-
 performance, tor-client, performance, 031-backport


Comment:

 Thanks, Arthur!

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24633 [Core Tor/Tor]: to->pending->tqh_last is 0xFFFFFFFFFFFFFFFF。

2017-12-17 Thread Tor Bug Tracker & Wiki
#24633: to->pending->tqh_last is 0x。
-+-
 Reporter:  sx5486510|  Owner:  nickm
 Type:  defect   | Status:
 |  accepted
 Priority:  Medium   |  Milestone:  Tor:
 |  0.3.2.x-final
Component:  Core Tor/Tor |Version:  Tor:
 |  0.3.2.1-alpha
 Severity:  Normal   | Resolution:
 Keywords:  msvc 029-backport 030-backport   |  Actual Points:
  031-backport   |
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by cypherpunks):

 * keywords:  msvc 029-backport 030-backpot 031-backpot => msvc 029-backport
 030-backport 031-backport


Comment:

 pot, hmm...

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24579 [Applications/Tor Browser]: Download- and Play-button are not visible on https://songs.pk

2017-12-17 Thread Tor Bug Tracker & Wiki
#24579: Download- and Play-button are not visible on https://songs.pk
-+--
 Reporter:  gk   |  Owner:  tbb-team
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Applications/Tor Browser |Version:
 Severity:  Normal   | Resolution:
 Keywords:  noscript, tbb-usability-website  |  Actual Points:
Parent ID:   | Points:
 Reviewer:   |Sponsor:
-+--
Changes (by cypherpunks):

 * keywords:  tbb-usability-website => noscript, tbb-usability-website


Comment:

 Replying to [comment:2 gk]:
 > Replying to [comment:1 cypherpunks]:
 > > Workaround: enable JS on High Security.
 >
 > How does that help?
 It bypasses XSS bug ;)
 > I don't see the player even on Tor Browser's default mode.
 Yes. And?
 > I suspect this could be related to our fix for #8725, though.
 No, but that fix needs revision.
 This is https://forums.informaction.com/viewtopic.php?f=7=24143

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18361 [Applications/Tor Browser]: Issues with corporate censorship and mass surveillance

2017-12-17 Thread Tor Bug Tracker & Wiki
#18361: Issues with corporate censorship and mass surveillance
--+--
 Reporter:  ioerror   |  Owner:  tbb-team
 Type:  enhancement   | Status:  reopened
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  security, privacy, anonymity  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  None
--+--

Comment (by cypherpunks):

 Replying to [comment:246 cypherpunks]:
 > According to other posts, GK have a connection to Cloudflare employee.
 He has contacts with them, so?

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #16261 [Webpages/Website]: Update the "Running a Bridge" section of the website

2017-12-17 Thread Tor Bug Tracker & Wiki
#16261: Update the "Running a Bridge" section of the website
-+-
 Reporter:  isis |  Owner:  isis
 Type:  defect   | Status:  new
 Priority:  Medium   |  Milestone:
Component:  Webpages/Website |Version:
 Severity:  Normal   | Resolution:
 Keywords:  tor-bridges, docs, pts, website- |  Actual Points:
  content|
Parent ID:  #24497   | Points:
 Reviewer:   |Sponsor:
-+-
Changes (by irl):

 * parent:   => #24497


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24399 [Webpages/Website]: Consistent set of icons for relay flags

2017-12-17 Thread Tor Bug Tracker & Wiki
#24399: Consistent set of icons for relay flags
--+
 Reporter:  irl   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by irl):

 For comparison, this second screenshot uses the alt version of v2dir.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24399 [Webpages/Website]: Consistent set of icons for relay flags

2017-12-17 Thread Tor Bug Tracker & Wiki
#24399: Consistent set of icons for relay flags
--+
 Reporter:  irl   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by irl):

 * Attachment "Screen Shot 2017-12-17 at 11.48.23.png" 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] #24399 [Webpages/Website]: Consistent set of icons for relay flags

2017-12-17 Thread Tor Bug Tracker & Wiki
#24399: Consistent set of icons for relay flags
--+
 Reporter:  irl   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by irl):

 Attached is a screenshot of the new icons in Relay Search. I'm very happy
 with how these have turned out.

 I've now finished off some scripts that generate PNGs and font files from
 the icons, and you can download a tar.gz archive from
 https://people.torproject.org/~irl/icons/ including the generated fonts
 and PNGs.

 teor: How strongly do you feel about using the blank directory for the
 V2Dir flag? It's ok at larger sizes but I think that the V2 does help to
 visually distinguish it from being a black rectangle at 16x16.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24399 [Webpages/Website]: Consistent set of icons for relay flags

2017-12-17 Thread Tor Bug Tracker & Wiki
#24399: Consistent set of icons for relay flags
--+
 Reporter:  irl   |  Owner:  (none)
 Type:  enhancement   | Status:  needs_revision
 Priority:  Medium|  Milestone:
Component:  Webpages/Website  |Version:
 Severity:  Normal| Resolution:
 Keywords:  ux-team   |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+
Changes (by irl):

 * Attachment "Screen Shot 2017-12-17 at 11.29.17.png" 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] #22867 [Applications/Tor Browser]: Some URLs are saved in the Tor Browser places.sqlite database as part of the browsing history

2017-12-17 Thread Tor Bug Tracker & Wiki
#22867: Some URLs are saved in the Tor Browser places.sqlite database as part of
the browsing history
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Major | Resolution:
 Keywords:  tbb-disk-leak |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 It happened to me again (!!) this time with
 `https://subscribe.washingtonpost.com/acq?promo=`

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24646 [Community/Tor Support]: Unable to login to Squirrel Email

2017-12-17 Thread Tor Bug Tracker & Wiki
#24646: Unable to login to Squirrel Email
---+-
 Reporter:  newbie1|  Owner:  phoul
 Type:  defect | Status:  closed
 Priority:  Medium |  Milestone:
Component:  Community/Tor Support  |Version:
 Severity:  Normal | Resolution:  invalid
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+-

Comment (by cypherpunks):

 Javascript required though.

 Or try http://secmailw453j7piv.onion/src/login.php

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #18361 [Applications/Tor Browser]: Issues with corporate censorship and mass surveillance

2017-12-17 Thread Tor Bug Tracker & Wiki
#18361: Issues with corporate censorship and mass surveillance
--+--
 Reporter:  ioerror   |  Owner:  tbb-team
 Type:  enhancement   | Status:  reopened
 Priority:  High  |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Critical  | Resolution:
 Keywords:  security, privacy, anonymity  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:  None
--+--

Comment (by cypherpunks):

 According to other posts, GK have a connection to Cloudflare employee.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24321 [Applications/Tor Browser]: Include Cloudflare's Official "Privacy Pass" addon to end Cloudflare captcha madness!

2017-12-17 Thread Tor Bug Tracker & Wiki
#24321: Include Cloudflare's Official "Privacy Pass" addon to end Cloudflare
captcha madness!
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Low   |  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:  #18361| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

 * priority:  Very High => Low
 * severity:  Critical => Normal


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

Re: [tor-bugs] #23141 [Applications/Tor Browser]: Cloudflare breaks loading the chat on http://www.goftesh.com/

2017-12-17 Thread Tor Bug Tracker & Wiki
#23141: Cloudflare breaks loading the chat on http://www.goftesh.com/
--+--
 Reporter:  gk|  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal| Resolution:
 Keywords:  cloudflare|  Actual Points:
Parent ID:  #18361| Points:
 Reviewer:|Sponsor:
--+--
Changes (by cypherpunks):

 * parent:   => #18361


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #22582 [Applications/Tor Browser]: www.nexusmods.com not working properly in TOR

2017-12-17 Thread Tor Bug Tracker & Wiki
#22582: www.nexusmods.com not working properly in TOR
---+--
 Reporter:  WalrusInAnus   |  Owner:  tbb-team
 Type:  defect | Status:  reopened
 Priority:  Medium |  Milestone:
Component:  Applications/Tor Browser   |Version:
 Severity:  Normal | Resolution:
 Keywords:  tbb-usability-website, cloudflare  |  Actual Points:
Parent ID:  #18361 | Points:
 Reviewer: |Sponsor:
---+--
Changes (by cypherpunks):

 * parent:   => #18361


--
Ticket URL: 
Tor Bug Tracker & Wiki 
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] #24648 [Applications/Tor Browser]: for Future Firefox ESR: Set privacy.resistFingerprinting.block_mozAddonManager to true

2017-12-17 Thread Tor Bug Tracker & Wiki
#24648: for Future Firefox ESR: Set
privacy.resistFingerprinting.block_mozAddonManager to true
--+--
 Reporter:  cypherpunks   |  Owner:  tbb-team
 Type:  task  | Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 https://github.com/ghacksuserjs/ghacks-user.js/issues/289

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