Message319701
> We have a ucd_3_2_0 in unicodedata.
Probably this 3.2 unicodedata is used for IDNA2003.
In IDNA2003 there is a step: normalize the domain_name string to Unicode Normalization Form C.
Now we changed the Composition code of Hangul to Unicode Standard 4.1+, and fixed the bug even in Unicode Standard 4.1-.
Should this (Unicode Standard 4.1+ behavior) cause a security vulnerability for someone who is using IDNA2003 via ucd_3_2_0? |
|
Date |
User |
Action |
Args |
2018-06-16 03:18:55 | malin | set | recipients:
+ malin, lemburg, loewis, vstinner, ezio.melotti, xiang.zhang, pusnow, miss-islington |
2018-06-16 03:18:55 | malin | set | messageid: <1529119135.58.0.56676864532.issue29456@psf.upfronthosting.co.za> |
2018-06-16 03:18:55 | malin | link | issue29456 messages |
2018-06-16 03:18:55 | malin | create | |
|