Chromium SSL/TLS interstitials broken

[graxlop]

My device is the Nexus 5, running the latest CopperheadOS.

Ever since one of the recent Chromium updates, I've noticed oddities with Chromium's SSL certificate interstitials and the detailed connection info. They seem to show either inaccurate info or just broken HTML code in the case of the interstitials.

Screenshots attached showing both problems. Some example interstitials can be found on the site below (ex. bad host, expired cert, etc.)

https://badssl.com/

[thestinger]

There are no modifications to the Chromium build used in CopperheadOS, so there's nothing for us to do beyond continuing to update it.

[thestinger]

There are no modifications to the Chromium build used in CopperheadOS, so there's nothing for us to do beyond continuing to update it.

[thestinger]

Do you use a different locale than US English? Might be worth trying that. I might not be asking it to build the other locales... don't know what I'd need to change though.

[thestinger]

Do you use a different locale than US English? Might be worth trying that. I might not be asking it to build the other locales... don't know what I'd need to change though.

[graxlop]

I'm using US English. It also seems to show up in chrome://history

[graxlop]

I'm using US English. It also seems to show up in chrome://history

[thestinger]

This is caused by not using the Chromium linker due to #202. I don't want to track upstream Chromium issues here. The only approach that will be taken here is fixing compatibility with the usual custom linker.

[thestinger]

This is caused by not using the Chromium linker due to #202. I don't want to track upstream Chromium issues here. The only approach that will be taken here is fixing compatibility with the usual custom linker.

[thestinger]

Here's an upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=630863/.

[thestinger]

Here's an upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=630863/.

[thestinger]

Since #202 has been fixed, this problem will be avoided by using the Chromium linker again. The upstream bug is still present and I'd like to disable the Chromium linker again once it's resolved though.

[thestinger]

Since #202 has been fixed, this problem will be avoided by using the Chromium linker again. The upstream bug is still present and I'd like to disable the Chromium linker again once it's resolved though.