
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>

<p><span>Seriously, how long do we have to wait on this to be fixed...</span></p>

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

<div> </div>

<div> </div>

</body></html>