There's a very good reason for the CMD program to not use the new file execution APIs (the ones that check origin of files) : if they did, the majority of administrative scripts in use today would be broken. Admins use these scripts counting on them to run unattended (either as a scheduled job, or a login script, or what have you). Most of them make use of third-party utilities, usually downloaded form the Internet with Internet Explorer. If CMD used the new APIs, these scripts would start popping up prompts and not work any more.

Breaking everyones' batch files would hardly be in the best interest of Microsoft's customers.





[ reply ]

Link to this comment: http://www.securityfocus.com/comments/columns/265/28419#28419