Bug #9754
add release information in outdated Tor security warning
100%
Description
Looking for Tor Upgrade you can find the scary security warning page
https://tails.boum.org/security/Upgrade_Tor/
“The version of Tor currently shipped in Tails does not protect your anonymity as it should. This vulnerability is critical.”
Users get scared. Maybe a note saying ‘This is not a problem since version X’ can be added. I can make a patch if somebody points me to the release where it got fixed. It has the fixed tag and that, but users may freak out.
Last edited Sat 08 Sep 2012 07:15:43 AM CEST
Also, is there any specific protocol to update a security warning?
Subtasks
History
#1 Updated by intrigeri 2015-07-18 05:40:52
- Assignee set to emmapeel
- QA Check changed from Info Needed to Dev Needed
> I can make a patch if somebody points me to the release where it got fixed.
It was fixed in Tails 0.9. That’s how I found it: follow the link to the Tor blog from that blog post, note the version of Tor that fixes the bugs, and check in our changelog when we upgraded to that version.
> Also, is there any specific protocol to update a security warning?
As long as the “meta date” field is kept in the remote past, this should not affect the Atom/RSS feeds I think, so: no.
#2 Updated by emmapeel 2015-07-19 03:19:33
- Assignee deleted (
emmapeel) - QA Check changed from Dev Needed to Ready for QA
- Feature Branch set to emmapeel:bug/9754
Please review https://git-tails.immerda.ch/emmapeel/tails/diff/?h=bug/9754
#3 Updated by intrigeri 2015-07-19 04:00:54
- Status changed from New to In Progress
- Assignee set to emmapeel
- % Done changed from 0 to 20
- QA Check changed from Ready for QA to Dev Needed
“This issue affected Tails only until version 0.9” feels wrong, given that 0.9 fixed it.
#4 Updated by emmapeel 2015-07-19 05:05:14
- Assignee deleted (
emmapeel)
Ok, fixed and squashed the branch, ready again for review.
#5 Updated by intrigeri 2015-07-19 05:37:01
- Assignee set to sajolida
- Target version set to Tails_1.5
- QA Check changed from Dev Needed to Ready for QA
Yay :)
#6 Updated by sajolida 2015-08-04 04:57:49
- Target version deleted (
Tails_1.5)
#7 Updated by Anonymous 2015-08-09 12:20:21
Applied in changeset commit:122e13878320b20fae76dfb3e3af6d6329a8085c.
#8 Updated by sajolida 2015-08-09 12:37:16
- Assignee changed from sajolida to emmapeel
- Feature Branch changed from emmapeel:bug/9754 to bug/9754
Hi, thanks for working on this. I reduced your word count by 43% in commit 376fa5b :)
Also note that we usually:
- Add empty lines between
<div>lines to be nice to be nice to translators. - Use full HTML inside HTML to be nice to the CSS.
That’s 59bfade.
Please review and tell me if the meaning is still correct. Then I’ll merge.
#9 Updated by emmapeel 2015-08-21 05:49:01
- Assignee changed from emmapeel to sajolida
- QA Check changed from Ready for QA to Pass
Yes, looks great!
#10 Updated by intrigeri 2015-08-22 05:24:22
> QA Check changed from Ready for QA to Pass
Was this merged, or?
#11 Updated by emmapeel 2015-08-23 01:12:36
- QA Check changed from Pass to Ready for QA
intrigeri wrote:
> > QA Check changed from Ready for QA to Pass
>
> Was this merged, or?
I chose Pass because I reviewed the changes and thought no more reviews were needed… nothing to do with the merge.
#12 Updated by sajolida 2015-08-23 01:35:46
- Status changed from In Progress to Resolved
- % Done changed from 20 to 100
Applied in changeset commit:0372dfd8f76a948e20d4845c3994ed521b325a04.
#13 Updated by sajolida 2015-08-23 01:36:14
- Assignee deleted (
sajolida) - QA Check changed from Ready for QA to Pass
Done now.
#14 Updated by BitingBird 2015-08-25 10:51:15
- Target version set to Tails_1.6