Issue metadata
Sign in to add a comment
|
SECCURITY PROTOCOL
Reported by
examplen...@gmail.com,
Jan 11 2018
|
||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. REESTABLISH NEW RULES 2. REVIEW WHAT DIDNT WORK 3. IDENTIFY WHO NEEDS TO BYPASS VERIFICATION... What is the expected behavior? TO HAVE LOGIN SUCCESS What went wrong? QUESTION OF ALL QUESTIONS.... Did this work before? Yes MICROSOFT IT TECH CLOUD EARLY ACCESS NON-CONFORMANCE (NEGLIGENCE ON THE MS OFFICE/SUPPORT GROUP SIDE) Chrome version: <Copy from: 'about:version'> Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 28.0 r0 THIS WILL FIX AND THE GOAL IS TO HAVE SMEANLESS FLOW OF PROP PROTOCOL.
,
Jan 11 2018
This does not represent an actionable report of a security vulnerability in Google Chrome. If you can explain specifically what problem you're encountering, I may be able to point you in the right direction for resolving the issue.
,
Apr 20 2018
This bug has been closed for more than 14 weeks. Removing security view restrictions. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by elawrence@chromium.org
, Jan 11 2018