This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients Alexander Riccio, brett.cannon, paul.moore, steve.dower, tim.golden, zach.ware
Date 2016-06-30.17:25:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1467307543.13.0.550122385869.issue26137@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-06-30 17:25:43steve.dowersetrecipients: + steve.dower, brett.cannon, paul.moore, tim.golden, zach.ware, Alexander Riccio
2016-06-30 17:25:43steve.dowersetmessageid: <1467307543.13.0.550122385869.issue26137@psf.upfronthosting.co.za>
2016-06-30 17:25:43steve.dowerlinkissue26137 messages
2016-06-30 17:25:43steve.dowercreate