New issue
Advanced search Search tips

Issue 811227 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Unwanted ssl error is seen after navigating to ‘app.yesware.com’ URL

Reported by pranjali...@etouch.net, Feb 12 2018

Issue description

Chrome Version:66.0.3345.0 (Official Build) c8ce2d88ee3c73948b2c91cbd9dff78eaf9472f0-refs/heads/master@{#536026}(32/64 bit)
 
OS: Mac(10.12.6, 10.13.1, 10.13.4),Windows(7,8,8.1,10),Linux(14.04 LTS).

Steps to reproduce:
1. Launch chrome ,navigate to 'app.yesware.com' URL and Observe.

Actual: Unwanted ssl error is seen after navigating to  ‘app.yesware.com’ URL
Expected: Such error message should not be seen after navigating to  ‘app.yesware.com’ URL

This is Regression issue broken in 'M-66’ and Using the per-revision bisect providing the bisect results,

Good Build:66.0.3334.0 (Revision : 532208)
Bad Build:66.0.3335.0  (Revision : 533164)

You are probably looking for a change made after 532238 (known good), but no later than 532239 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/e93a97278842441acc34611ec2ccc0b50c13fb6b..c646e48f1ff851d8eb8e2ae713a031684b46db27

Suspect: https://chromium.googlesource.com/chromium/src/+/c646e48f1ff851d8eb8e2ae713a031684b46db27

@rsleevi :  Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Kindly refer attached screen cast 


 
Actual_result.mov
947 KB View Download
Expercted_result.mov
804 KB View Download
Labels: RegressedIn-66 FoundIn-66 Target-66
Labels: ReleaseBlock-Stable
Adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!
Components: -Internals>Network>SSL Internals>Network>Certificate
Status: WontFix (was: Assigned)
This is correct, as per https://security.googleblog.com/2017/09/chromes-plan-to-distrust-symantec.html

This site's certificate is no longer trusted. It must be replaced. The DevTools since Chrome 62 has included messaging to this effect.
The existing certificate, https://crt.sh/?id=5524515 , was scheduled to be replaced in May. The site can obtain a free replacement certificate by contacting their DigiCert sales representative.

Sign in to add a comment