Seriously, how long do we have to wait on this to be fixed...
On Mon, 30 Mar 2015 12:58:26 -0700 Kenton Varda <ken...@sandstorm.io> wrote: > fixed 774195 2:3.17.4-1 > > Could the fixed version in experimental please get pushed along to > unstable? Otherwise we're training users to ignore https errors and > masking real problems. > > On Sat, Mar 14, 2015 at 8:00 PM, Kenton Varda <ken...@sandstorm.io> wrote: > > Because of this bug, Chrome (42.0.2311.39) now flags most HTTPS certificates > > as broken. For example, tweetdeck.twitter.com shows "https" struck out in > > red, as in this screenshot: > > > > https://lh5.googleusercontent.com/-uL3aeiJeg6U/VQOyNUF51rI/AAAAAAAAHlQ/HUFK3SyDvGk/w359-h30-no/https-not.png [1] > > Links: ------ [1] https://lh5.googleusercontent.com/-uL3aeiJeg6U/VQOyNUF51rI/AAAAAAAAHlQ/HUFK3SyDvGk/w359-h30-no/https-not.png
