Opened 15 months ago

Last modified 7 weeks ago

#25204 new enhancement

Switch security.insecure_connection_* prefs to warn users about insecure HTTP in FF60-esr

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: ff60-esr, ux-team
Cc: Actual Points:
Parent ID: #30037 Points:
Reviewer: Sponsor:


These prefs are much more eye grabbing as they display both the broken padlock and the "Not Secure" text, which is really important in TB context:

Child Tickets

Change History (9)

comment:1 Changed 15 months ago by cypherpunks

Keywords: ux-team added

Good idea! Putting ux-team to know what they think.

comment:2 Changed 15 months ago by cypherpunks

If enabled in the next TB stable 8.0 release this would also coincide with the time Google enables it as well, and probably Mozilla as well.

Last edited 15 months ago by cypherpunks (previous) (diff)

comment:3 Changed 11 months ago by cypherpunks

Chrome 68 will be released on: July 24th, 2018 (which will label as insecure all http by default see ) so can we get this for the next alpha as it's only a matter of flipping some prefs?

comment:4 Changed 10 months ago by ProTipGuyFWIWWeLoveARMA

It's finally the day: Today’s the day that Chrome brands plain old HTTP “not secure”

Can we get this ticket done for the next alpha? :)

comment:5 Changed 2 months ago by pili

Sponsor: Sponsor27

comment:6 Changed 7 weeks ago by pili

Sponsor: Sponsor27

comment:7 Changed 7 weeks ago by cypherpunks

No feedback from the UX team on this?

comment:8 Changed 7 weeks ago by gk

Closing #29678 as a duplicate. For Mozilla bugs on that matter, see: comment:5:ticket:29678 and comment:6:ticket:29678.

comment:9 Changed 7 weeks ago by pili

Parent ID: #30037
Note: See TracTickets for help on using tickets.