Unicode bug in the convert_to_unicode function of joliet.c
A Tool Box with tools written or managed by Jörg Schilling
Brought to you by:
schily
Menu
▾
▴
#6 Unicode bug in the convert_to_unicode function of joliet.c
OpenIndiana user claimes unicode bug in the convert_to_unicode function of joliet.c file of cdrecord and perhaps schily tools as well, see https://github.com/OpenIndiana/oi-userland/commit/5656b8cbc8d0b6444a70b2b795c1f872cef2753c#commitcomment-30201326 for the report and proposed patch. Is this a genuine bug? Is the fix valid?
The patch is not valid as the related problem in the unicode vonversion has been fixed in December 2017 and January 2018.
The problem was triggered by chinese and japanese characters (with a length of more than two octetts).
The bug was reported by a chinese person and the reason why this has not been detected for a long time is that there was space for 2x the strlen(), so only a string with a sufficient amount of chinese characters inside was longer than expected.
BTW: The latest published changes are from May 2018, but the next release will get an updated libfind that supports -newermt, so it makes sense to check the next release that will most likely be available to the end of this week.