all downloads from MS developer dashboard are being marked dangerous |
||||
Issue descriptionChrome Version: 66.0.3343.0 (Official Build) canary (64-bit) (cohort: Clang-64) OS: Windows 10 Version 1607 (OS Build 14393.2007) What steps will reproduce the problem? (1) Go to MS developer dashboard (2) Download a memory dump for a crash. (3) What is the expected result? Is not dangerous What happens instead? It's marked as dangerous. Please use labels and text to provide additional information. Since the developer dashboard is not public and needs a login, I can demonstrate this, or I can provide additional information. I do have some entries in my chrome://safe-browsing that might help - they are showing entries in "Full Hash Cache" with various "threat_entry_type" and "threat_type" and can provide those if they would be useful. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
Feb 8 2018
If you don't mind restarting your browser, could you please do the following: 1. Restart Chrome. 2. Open chrome://safe-browsing and grab a copy of it before and after downloading the memory dump.
,
Feb 8 2018
Here are the links (Google access only) before: http://shortn/_CUTHhUH2XX after: http://shortn/_Q8vyWimRS0 the actual URL of the download: http://shortn/_DGxV2a3zON
,
Feb 8 2018
,
Feb 8 2018
Thanks for sharing the links. The file is not showing the warning any more so it looks like the warning that was shown was for uncommon download. I looked inside the file and found nothing suspicious so I'll check with the Safe Browsing team to see why the warning was shown in the first place. Thanks.
,
Feb 8 2018
It's showing for every file I download. Each file will probably at most be downloaded once so will never become a 'common download'.
,
Feb 8 2018
some additional information requested by vakh is here -> http://shortn/_tz2F9kJaqK
,
Feb 8 2018
Yes, this warning should not have been shown because of the origin of the download. I'll investigate this.
,
Feb 9 2018
This should be fixed now. Please let me know if it isn't. |
||||
►
Sign in to add a comment |
||||
Comment 1 by vssummer...@gmail.com
, Feb 8 2018