Message234598
| Author |
serhiy.storchaka |
| Recipients |
Claudiu.Popa, Guido.van.Rossum, gvanrossum, lemburg, r.david.murray, serhiy.storchaka, stephen.farris, vstinner |
| Date |
2015年01月24日.09:15:16 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1422090916.86.0.0209477352925.issue22885@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
Raising dbm.dumb.error is behavior change. It would be safer not apply this part in maintained releases.
If add sanity checks in 3.5, note that following line "key = key.encode('Latin-1')" can raise an exception too (AttributeError or UnicodeEncodeError). And incorrect data can cause an error later in __getitem__ if pos_and_siz_pair is not a pair of two integers.
I think it is worth to split this issue on two issues and fix only security issue here. |
|