Bug #8092: 'Technical details' section empty when clicking padlock icon on Browser on Tails 1.2 rc

Bug #8092

'Technical details' section empty when clicking padlock icon on Browser on Tails 1.2 rc

Added by emmapeel 2014-10-13 10:40:31 . Updated 2015-05-12 18:45:45 .

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Target version:

Tails_1.4

Start date:

2014-10-13

Due date:

% Done:

100%

Feature Branch:

feature/9031-tor-browser-4.5

Type of work:

Wait

Blueprint:

Starter:

Affected tool:

Browser

Deliverable for:

Description

Reported by a user, reproduced by me.

Steps to reproduce:

- Go to a webpage with ssl.

- Click on the padlock button
- Click on Details if needed.

At the end of the window, Technical details section is empty. It should give information about the cyphersuite used, etc.

Upstream bug: https://trac.torproject.org/projects/tor/ticket/13254

Subtasks

Related issues

Blocked by Tails - ~~Feature #9031~~: Upgrade to Tor Browser 4.5

Resolved

2015-03-26

History

#1 Updated by intrigeri 2014-10-13 15:41:21

Assignee set to anonym
Parent task set to ~~Feature #7238~~

#2 Updated by intrigeri 2014-10-14 02:20:13

Reproduced on a build from feature/tor-browser-4.0. Not tried in a regular TB 4.0.

#3 Updated by anonym 2014-10-14 04:28:56

intrigeri wrote:
> Not tried in a regular TB 4.0.

I did, and it is an upstream bug. Reported as: https://trac.torproject.org/projects/tor/ticket/13404

#4 Updated by anonym 2014-10-14 05:17:52

Apparently already reported upstream as: https://trac.torproject.org/projects/tor/ticket/13254

#5 Updated by intrigeri 2014-10-15 06:35:03

Priority changed from Elevated to Normal
Target version changed from Tails_1.2 to Tails_1.2.1
Type of work changed from Code to Wait

Postponing, lowering priority as it’s not a recent regression, and now waiting for the upstream fix.

#6 Updated by intrigeri 2014-10-15 08:20:56

Parent task deleted (~~~~Feature #7238~~~~)

#7 Updated by BitingBird 2014-11-27 01:02:00

Assignee deleted (~~anonym~~)

Removing assignee, since we’re not going to work on it but waiting for upstream to fix it. Should we also remove the target version? They don’t seem to prioritize this, so I doubt that it’s going to be fixed in the next few days…

#8 Updated by intrigeri 2014-11-27 09:19:17

Assignee set to anonym

> Removing assignee, since we’re not going to work on it but waiting for upstream to fix it.

… and in this case, the assignee is the person who’s supposed to keep an eye on the progress upstream is making, and if there’s no progress, maybe ping and/or help them => setting it back.

> Should we also remove the target version? They don’t seem to prioritize this, so I doubt that it’s going to be fixed in the next few days…

The target version is here to indicate that it’s a regression brought recently, that we’d like to see fixed ASAP. I think it’s useful. Of course, it now looks like this will be postponed (at least) to the next release, but this way it stays on our radar.