So it looks like
  .v[d,s,t]x and .vs[d,s,t][x,m]
are similar in functionality to the orig
  .vs[d,s,t] that we currently ping on.

I'm not too concerned about the VB Macros, since that's already an issue for .docx etc, and we can start pinging for those only if we detect (via other means) that a significant number of them are indeed malicious.  This is a balance of privacy vs speed of protection.

I don't know why we ping on the old Visio format.

But... Ubuntu treating .vsdx as a zip (I repro'd this) is an issue since it allows any dangerous type to be cloaked in a .vsdx on Ubuntu.  So I think we should uncompress them as zips to look for bad files, and ping if there are any.

So my plan is to track all of these types, but not yet ping on them.

i think the old Visio format get a ping, because the most likely program people use to open it is the free MS Visio Viewer[unless they own MS Visio], which uses IE to open the files.
Pretty much every file format that uses IE to open as default program gets a ping, e.g. .website, .url, .svg, .partial, .xrm-ms, .rels, .xls ..., even if IE is not the default browser.

.vs[d,s,t][x,m] are all treated as archives in Ubuntu.

[After discussion offline w/ vakh@, we decided we should ping on all of these and unpack them as zips]

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

commit 8add59a69da35f2cc0c3585fa44cac696a3d003c
Author: Nathan Parker <nparker@chromium.org>
Date: Fri Oct 27 23:07:31 2017

Add a number of new download_file_types, and some enums we were missing.

Add btapp, btbtskin, btkey, btinstasll, btsearch,
    dhtml, dhtm, dht, shtml, shtm, sht, vdx, vsx,
    vtx, vsdx, vssx, vstx, vsdm, vssm, vstm.

Fix up enums that weren't correct before, an remove some platform_settings
that are set to the defaults anyway.

Bug:  771469 ,  767502 ,  762702 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I4114c35e3f1a56a067f9b61bb54bfe3a8a801531
Reviewed-on: https://chromium-review.googlesource.com/736161
Commit-Queue: Nathan Parker <nparker@chromium.org>
Reviewed-by: Luke Z <lpz@chromium.org>
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Reviewed-by: David Trainor <dtrainor@chromium.org>
Cr-Commit-Position: refs/heads/master@{#512338}
[modify] https://crrev.com/8add59a69da35f2cc0c3585fa44cac696a3d003c/chrome/browser/resources/safe_browsing/download_file_types.asciipb
[modify] https://crrev.com/8add59a69da35f2cc0c3585fa44cac696a3d003c/content/browser/download/download_stats.cc
[modify] https://crrev.com/8add59a69da35f2cc0c3585fa44cac696a3d003c/tools/metrics/histograms/enums.xml

Pushed via component update.

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