New issue
Advanced search Search tips

Issue 865129 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 18
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

Ability to bypass blocking warning for end users

Project Member Reported by annaloraine@google.com, Jul 18

Issue description

Description:
Ability to stop the blocking warning as it sets wrong impression for the end users. Chrome doesn’t even do that for HTTP sites (non SSL sites)

Use case:
Because when an end users will get to this page, they would think that they are not allowed to proceed and use the website. This is giving a wrong expectation to their end users and this is not helping them as they would have to update re-generate and update their 13,000 certificates.

Motivation:
It will be very helpful for Admins. By having this ability to remove the blocking warning, their business continues while they are updating the certificate from the back end without service interruption for the end user. 

Existing workarounds:
No workaround at the moment. 

 
Status: WontFix (was: Untriaged)
This was discussed in landing bug  crbug.com/308330 

Especially in comment 38:
https://bugs.chromium.org/p/chromium/issues/detail?id=308330#c38

So that's why for long time (v58 to v66), to allow users to adopt to change we left EnableCommonNameFallbackForLocalAnchors until version 66.

But enabling any feature, like requested, would be against original intention (security benefits).

Sign in to add a comment