Feature #16705
Update our explanation of JavaScript protections in Tor Browser
Start date:
Due date:
% Done:
0%
Subtasks
Related issues
Blocks Tails - |
Resolved | 2018-09-11 |
History
#1 Updated by sajolida 2019-05-06 08:51:35
- blocks
Feature #15941: Core work 2018Q4 → 2019Q2: Technical writing added
#2 Updated by anonym 2019-05-06 14:53:48
- Status changed from Confirmed to Resolved
#3 Updated by anonym 2019-05-06 14:56:04
- Status changed from Resolved to Confirmed
#4 Updated by anonym 2019-05-06 15:03:22
- Target version changed from Tails_3.13.2 to Tails_3.14
#5 Updated by sajolida 2019-05-14 19:04:44
- Assignee changed from sajolida to cbrownstein
- QA Check set to Ready for QA
- Feature Branch set to doc/16705-javascript-protections
This was much easier than I thought. See doc/16705-javascript-protections.
After 9021f83ee6 I don’t think that we need to mention canvas fingerprinting protection.
If the security analysis is outside of your comfort zone, please don’t spend too much time on it and I can always ask someone else to review this part specifically.
#6 Updated by cbrownstein 2019-05-15 21:53:00
- Assignee changed from cbrownstein to sajolida
I’ve pushed a few changes:
https://0xacab.org/cbrownstein/tails/commits/doc/16705-javascript-protections
> If the security analysis is outside of your comfort zone, please don’t spend too much time on it and I can always ask someone else to review this part specifically.
The security analysis is within my comfort zone. And I followed the thread on tails-dev@. :-)
#7 Updated by sajolida 2019-05-16 09:49:39
You rock!
#8 Updated by intrigeri 2019-05-18 06:26:49
- Status changed from Confirmed to In Progress
#9 Updated by sajolida 2019-05-21 16:53:17
- Status changed from In Progress to Resolved
- Assignee deleted (
sajolida) - QA Check deleted (
Ready for QA)
Merged!