- Dec 23, 2014
- 8,510
The general idea is to always run executable files (from the User Space, no EV certificate) with SmartScreen check. There are many ways to accomplish this.
The most simple one is to check immediately if the dropped file has the proper Zone.Identifier file stream. If so, that is OK. If not, then Zone.Identifier file stream is added. I assume that the file stream will not be changed/deleted afterwards, and all executable files in the User Space have already got the proper file stream (it can be done during installation of MZWriteScanner).
The second solution (more robust) would be to make the checking/adding always when any executable file from the User Space tries to run (but before SmartScreen is triggered).
The third solution would be to make the checking as above. If the dropped file has the proper Zone.Identifier file stream, that is OK. If not, then MZWriteScanner triggers SmartScreen Filter in another way (does not add the file stream).
It would be great, if Florian could extend the functions of MZWriteScanner or Bouncer to do this task.
The most simple one is to check immediately if the dropped file has the proper Zone.Identifier file stream. If so, that is OK. If not, then Zone.Identifier file stream is added. I assume that the file stream will not be changed/deleted afterwards, and all executable files in the User Space have already got the proper file stream (it can be done during installation of MZWriteScanner).
The second solution (more robust) would be to make the checking/adding always when any executable file from the User Space tries to run (but before SmartScreen is triggered).
The third solution would be to make the checking as above. If the dropped file has the proper Zone.Identifier file stream, that is OK. If not, then MZWriteScanner triggers SmartScreen Filter in another way (does not add the file stream).
It would be great, if Florian could extend the functions of MZWriteScanner or Bouncer to do this task.
Last edited: