c***@googlecode.com
2015-06-09 08:47:45 UTC
Status: Unconfirmed
Owner: ----
Labels: Cr-Internals-Network Pri-2 Via-Wizard Type-Bug OS-Windows
New issue 498136 by ***@gmail.com: File "not commonly downloaded and
could be dangerous"; was working a few days ago
https://code.google.com/p/chromium/issues/detail?id=498136
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/43.0.2357.81 Safari/537.36
Example URL:
Steps to reproduce the problem:
1. Create a (CA signed) Windows signed executable and serve it over the web
from a HTTPS secure domain. No file redirects take place, the download is
streamed to the browser.
2. Notice the download completes but reports "... is not commonly
downloaded and could be dangerous"
What is the expected behavior?
We were not triggering this behavior before (eg a few days/week ago).
Our website issues self-signed Windowss based installer .exe executables to
a small group of people.
The download will certainly be uncommon because its only issued to a few
select people, it is not a large scale download.
The download is not malicious and has a CA-issued certificate signature
using codesign on Windows.
What went wrong?
Chrome started reporting this file is uncommon and "could be dangerous",
incorrectly alarming our users.
Did this work before? Yes At least a few weeks ago when we last tested it.
It has been working for months without issue.
Chrome version: 43.0.2357.81 Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 17.0 r0
Interested in having this regression resolved as it causes alarm to our
users and we have to explain its not our fault.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Owner: ----
Labels: Cr-Internals-Network Pri-2 Via-Wizard Type-Bug OS-Windows
New issue 498136 by ***@gmail.com: File "not commonly downloaded and
could be dangerous"; was working a few days ago
https://code.google.com/p/chromium/issues/detail?id=498136
UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML,
like Gecko) Chrome/43.0.2357.81 Safari/537.36
Example URL:
Steps to reproduce the problem:
1. Create a (CA signed) Windows signed executable and serve it over the web
from a HTTPS secure domain. No file redirects take place, the download is
streamed to the browser.
2. Notice the download completes but reports "... is not commonly
downloaded and could be dangerous"
What is the expected behavior?
We were not triggering this behavior before (eg a few days/week ago).
Our website issues self-signed Windowss based installer .exe executables to
a small group of people.
The download will certainly be uncommon because its only issued to a few
select people, it is not a large scale download.
The download is not malicious and has a CA-issued certificate signature
using codesign on Windows.
What went wrong?
Chrome started reporting this file is uncommon and "could be dangerous",
incorrectly alarming our users.
Did this work before? Yes At least a few weeks ago when we last tested it.
It has been working for months without issue.
Chrome version: 43.0.2357.81 Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 17.0 r0
Interested in having this regression resolved as it causes alarm to our
users and we have to explain its not our fault.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/a/chromium.org/group/chromium-bugs
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-bugs+***@chromium.org.