New issue
Advanced search Search tips

Issue 868575 link

Starred by 3 users
Status: Fixed
Owner:
cthomp@chromium.org
Closed: Aug 1
Cc:
ios-bugs-priority@chromium.org
ios-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , iOS , Chrome , Mac , Fuchsia
Pri: 1
Type: Task
Team-Security-UX



Sign in to add a comment

Enable "HTTP dangerous on form edit" by default

Project Member Reported by cthomp@chromium.org, Jul 27 
Starting in M70, the default will be to show a "Not Secure" warning on all http:// pages and to show a dangerous warning (red triangle) if a form field is edited. Now that M70 is Canary, we need to set this as the default behavior for the feature and let it roll through the release channels.
Project Member

Comment 1 by bugdroid1@chromium.org, Aug 1 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ad79c682232392102e3565ade44e87ce0e839c04

commit ad79c682232392102e3565ade44e87ce0e839c04
Author: Christopher Thompson <cthomp@chromium.org>
Date: Wed Aug 01 15:26:31 2018

Enable 'HTTP dangerous on form edit' by default

This CL enables the previous HTTP-Bad condition
"WarningAndDangerousOnFormEdit" by default, which shows a warning on all
http:// pages and a dangerous warning if a form field is edited. This
also updates security state tests accordingly.

Bug:  868575 
Change-Id: I6ec68a756b40e5cc312dc15e0df477891e85287a
Reviewed-on: https://chromium-review.googlesource.com/1153828
Reviewed-by: Adrienne Porter Felt <felt@chromium.org>
Commit-Queue: Christopher Thompson <cthomp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#579810}
[modify] https://crrev.com/ad79c682232392102e3565ade44e87ce0e839c04/components/security_state/core/security_state.cc
[modify] https://crrev.com/ad79c682232392102e3565ade44e87ce0e839c04/components/security_state/core/security_state_unittest.cc

Comment 2 by cthomp@chromium.org, Aug 1

Status: Fixed (was: Started)
►

Sign in to add a comment