[issue19470] email.header.Header - should not allow two newlines in a row

R. David Murray added the comment: Having thought further about this (prompted by a suggested fix by Varun Sharma), I'm going to reject it. The reason is that the email package in 3.2 compatibility mode still uses the Header object to encapsulate headers that have invalid binary data in them.

[issue19470] email.header.Header - should not allow two newlines in a row

R. David Murray added the comment: I'm not sure how appropriate it is to "validate" a header using the Header object. Header is for *composing* internationalized headers, and does no validation to speak of. However, if you'd like to write a patch to add this check, I would probably commit it

[issue19470] email.header.Header - should not allow two newlines in a row

Changes by hhm : -- versions: +Python 3.3 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue19470] email.header.Header - should not allow two newlines in a row

Changes by Vajrasky Kok : -- nosy: +r.david.murray, vajrasky ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue19470] email.header.Header - should not allow two newlines in a row

hhm added the comment: (see also http://bugs.python.org/issue5871) -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue19470] email.header.Header - should not allow two newlines in a row

New submission from hhm: An email.header.Header object should not allow two consecutive newlines, since this terminates interpretation of headers and starts the body section. This can be exploited by an attacker in a case of user input being used in headers, and validated with the Header objec