Tails

#1 Updated by sajolida 2018-10-27 16:27:48

• File NetworkError on download and no refresh after installing extension.webm added

Reverting 6f94042 fixes the issue locally in Chromium but not in Firefox. I’ll release a new version soon and it might fix things for Firefox in production as well. But I only have 1.5 hour in front of me now, so that wouldn’t be safe.

Most likely, this has been broken since 1.0 and everybody who worked on these lines participated in creating the bug :(

#3 Updated by Anonymous 2018-11-14 11:17:08

• related to Bug #13450: Implement CSP HTTP header added

#4 Updated by Anonymous 2018-11-14 11:17:22

• related to Feature #15060: Apply a more restrictive CSP in Verification Extension added

#8 Updated by sajolida 2018-12-10 15:51:42

• Target version changed from Tails_3.11 to Tails_3.12

#11 Updated by sajolida 2018-12-25 19:21:39

• File page-reset-in-chrome.webm added
• Assignee deleted (sajolida)
• Priority changed from Elevated to Normal
• QA Check set to Dev Needed

In Chrome the page is refreshed but also reseted, see screencast in attachment.

Do you see an easy fix for this?

Still, the situation improved a lot with 2.0. Congrats!

#13 Updated by anonym 2019-01-30 11:59:35

• Target version changed from Tails_3.12 to Tails_3.13

#14 Updated by sajolida 2019-02-12 15:37:48

• Assignee set to sajolida
• Type of work changed from Code to Test

I’ll test again what’s up with that now that 3.12 has been released.

#15 Updated by sajolida 2019-02-13 21:13:53

• Status changed from Confirmed to In Progress
• Target version changed from Tails_3.13 to Tails_3.14

It was quite an odyssey but I finally managed to fix that.

To summarize, we need to fully reload the page to be able to actually use the extension. But reloading the page prevent us from sending more JavaScript to it. So in the end I’m reloading the page on a custom HTML anchor. See tails.git:4bda4d93cf.

Just out of curiosity, I’ll procrastinate to do some stats on the usage of the extension by Chrome users before and after this change (February 13). With my new script it should be fast :)

#16 Updated by sajolida 2019-02-15 10:59:31

• related to Bug #16009: Metrics for USB Image added

#18 Updated by sajolida 2019-05-03 10:47:22

• Status changed from In Progress to Resolved
• QA Check deleted (Dev Needed)

Since we release USB images the usage rate on Chrome raised by more than 1% but the usage rate which could be attributed to this UX improvement. But surprisingly, the usage rate on Firefox, with no UX change, dropped by less than 1%. Are the user segments that are downloading Tails more (eg. macOS) less prone to use the verification extension is general?

March

| Browser | Download | Successful | Failed | Total | Usage rate | Failure rate |
|---------+----------+------------+--------+-------+------------+--------------|
| Chrome  |    40576 |       5810 |    668 |  6478 |         16 |          1.6 |
| Firefox |    43429 |       9394 |   1942 | 11336 |       26.1 |          4.5 |
#+TBLFM: $5=vsum($3+$4)::$6=round(100*$5/$2,1)::$7=round(100*$4/$2,1)

April

| Browser | Download | Successful | Failed | Total | Usage rate | Failure rate |
|---------+----------+------------+--------+-------+------------+--------------|
| Chrome  |    38158 |       5231 |    605 |  5836 |       15.3 |          1.6 |
| Firefox |    39236 |       8338 |   1799 | 10137 |       25.8 |          4.6 |
#+TBLFM: $5=vsum($3+$4)::$6=round(100*$5/$2,1)::$7=round(100*$4/$2,1)

#19 Updated by intrigeri 2019-05-05 08:24:00

• Target version changed from Tails_3.14 to Tails_3.13.2

#20 Updated by anonym 2019-05-06 15:03:17

• Target version changed from Tails_3.13.2 to Tails_3.14

#21 Updated by intrigeri 2019-05-06 18:15:42

• Target version changed from Tails_3.14 to Tails_3.13.2