Steve Dower added the comment:

And in case it's not clear, I *totally* recognize that AMSI is not for 
everyone. If you're running in a developer environment, your security is almost 
certainly so lax that it's irrelevant.

However, once you start getting serious about what's deployed on your 
production machines, Python gets ruled out very quickly because it lacks 
features like AMSI. Sysadmins don't want to enable a potential attack tool 
unless it's value drastically outweighs the risks (and on Windows, this is 
generally/currently not true), or there is sufficient insight into the behavior 
and use of the tool.

If we want Python to be seen as a production tool and not just a developer tool 
(which I do), we need to address these concerns.

----------

_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26137>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

Reply via email to