Forums Feature Suggestions [SUGGESTION]: Add -b parameter to /run

Hello,

In some machines when trying to use /run to open an file (e.g: an .exe file or .bat) and the computer has into the Internet Explorer the option for asking the user to run the file (Open File Security Warning) the /run returns an error and the code broke, so i suggesting (if it is possible) to add an parameter into the /run (example: -b) to by-pass this Internet Explorer Open File Security Warning to not brake down the code.

-b = attempts to by-pass the open file security warning of internet explorer for the specific running file.

NOTE: If there is any other way to by-pass this and anyone has an workaround please reply.

- Thanks!

Give some of these a try, this is a generic windows security setting and I don't think any program should be bypassing it.

http://www.sevenforums.com/tutorials/124...block-file.html

Yeah, i got all of these stuff read but nothing of its registry are working.

Since now i have found one command line tool that by-pass this s**t: http://blogs.technet.com/b/askcore/archi...deployment.aspx

I think its all about the Attachment Manager and there is an API that the -b parameter can by-pass this warning, and i suggesting this only because is breaking the /run , and of course by default the /run when someone use it is own risk, thats why also the mIRC has an lock option about it so the -b parameter is not gonna *HACK* the running progress of an file.

I wanna also add some informations about this problem/feature, i had found and test an command line tool by Microsoft (streams.exe) and working (under windows 10), that this tool by-pass this open file warning security and i had found some informations that may help mirc to implement it core (via -b paramater):

Informations:

Before downloading or opening any executable file.This is called "Open file security Warning". This is raised because of Attachment Execution Services (AES). Every program which uses the ShellExecute() API, must pass through AES.

About the Microsoft's "streams.exe" informations here

Use /run -h cmd.exe /C "<path>"

-h hides the terminal window.
/C instructs the terminal window to close after execution.

This should work since AES verification is only checked when running from a shell (i.e. Explorer)