Bug#844631: chromium: certificate transparency error on i386

2016-12-01 Thread Adrian Thoroughgood
Dear Maintainer
This bug is preventing me from accessing amazon at all in Chromium. I get this 
message:
"Your connection is not private
Attackers might be trying to steal your information from www.amazon.co.uk (for 
example, passwords, messages, or credit cards). 
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED
www.amazon.co.uk normally uses encryption to protect your information. When 
Chromium tried to connect to www.amazon.co.uk this time, the website sent back 
unusual and incorrect credentials. This may happen when an attacker is trying 
to pretend to be www.amazon.co.uk, or a Wi-Fi sign-in screen has interrupted 
the connection. Your information is still secure because Chromium stopped the 
connection before any data was exchanged.
You cannot visit www.amazon.co.uk right now because the website uses HSTS. 
Network errors and attacks are usually temporary, so this page will probably 
work later."
I get error messages in other HTTPS websites but this is the only one I've 
found so far that is completely broken.
It has been like this ever since I installed the latest version of chromium 
53.0.2785.143-1~deb8u1Ubuntu have had the fix incorporated into their packages 
for some time. Please can we have it too? I don't know how the severity 
classifications are defined but major websites being completely unusable seems 
pretty important to me.
Thanks






Bug#844631: chromium: certificate transparency error on i386

2016-11-17 Thread Jesse Davis
Package: chromium
Version: 53.0.2785.143-1~deb8u1
Severity: important
Tags: upstream

Dear Maintainer,

When requesting some https resources a security error is displayed in
the browser:

NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

An example url:
https://images-na.ssl-images-amazon.com/images/G/01/advantage/vendor-central
/site-logo._V383469221_.jpg

This mostly seems to effect CDN resources and so sites do not load
resources correctly.


This only happens on the i386 build of chromium, and not on amd64.


The bug is described in more detail here:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380

And looks to have been fixed in ubuntu:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/comments/44

And more upstream information on this bug from chromium.org:
https://bugs.chromium.org/p/chromium/issues/detail?id=664177