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 serhiy.storchaka
Recipients Arfrever, georg.brandl, pitrou, r.david.murray, serhiy.storchaka
Date 2013-02-03.08:50:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <201302031050.31166.storchaka@gmail.com>
In-reply-to <1359839705.04.0.945551859333.issue17106@psf.upfronthosting.co.za>
Content
Crash is possible not only when reading from text files, but also when decoder 
returns a non-string or when decoder's state is not a bytes object. This is 
possible with malicious decoder and perhaps with some old not bytes-to-string 
decoder in stdlib codecs registry.

Here are patches for different versions.
Files
File name Uploaded
textio_type_check-2.7.patch serhiy.storchaka, 2013-02-03.08:50:53
textio_type_check-3.2.patch serhiy.storchaka, 2013-02-03.08:50:54
textio_type_check-3.3.patch serhiy.storchaka, 2013-02-03.08:50:53
History
Date User Action Args
2013-02-03 08:50:54serhiy.storchakasetrecipients: + serhiy.storchaka, georg.brandl, pitrou, Arfrever, r.david.murray
2013-02-03 08:50:54serhiy.storchakalinkissue17106 messages
2013-02-03 08:50:54serhiy.storchakacreate