[Python-Dev] Deprecate invalid ctypes call protection on Windows (original) (raw)
Mariatta Wijaya mariatta.wijaya at gmail.com
Tue May 23 11:44:15 EDT 2017
- Previous message (by thread): [Python-Dev] Deprecate invalid ctypes call protection on Windows
- Next message (by thread): [Python-Dev] Deprecate invalid ctypes call protection on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
+1
My understanding is this is a documentation change, marking it as deprecated in 3.6.2 and a Misc News entry. No actual code change. Correct?
Mariatta Wijaya
On Tue, May 23, 2017 at 8:28 AM, Antoine Pitrou <solipsis at pitrou.net> wrote:
On Mon, 22 May 2017 11:17:18 -0700 Steve Dower <steve.dower at python.org> wrote: > > I'd like to propose a highly-accelerated deprecation period for this > specific feature, starting in CPython 3.6.2 and being "completed" in > 3.7.0, when we will hopefully move onto a newer libffi. > > In general, the "feature" is a misfeature anyway, since calling a native > function with incorrect arguments is unsupported and a very easy way to > cause information leakage or code execution vulnerabilities.
Agreed. > Does anyone have any reasons to oppose this? It already has votes from > another Windows expert and the 3.6/3.7 Release Manager, but we wanted to > see if anyone has a concern we haven't thought of. +1 from me. Regards Antoine.
Python-Dev mailing list Python-Dev at python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/ mariatta.wijaya%40gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20170523/294c10e4/attachment-0001.html>
- Previous message (by thread): [Python-Dev] Deprecate invalid ctypes call protection on Windows
- Next message (by thread): [Python-Dev] Deprecate invalid ctypes call protection on Windows
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]