Re: [Libcdio-devel] Vulnerable use of strcpy in iso9660_fs.c

2024-04-08 Thread Rocky Bernstein
First of all Thomas, your suggestions are *greatly appreciated! * Right now I am getting ready for eclipse-watching in the US and am out of town and/or vacationing. But when I get back I'll soon travel to Singapore to talk at BlackHat Asia 2014 and will spend a couple of weeks in Malaysia after th

Re: [Libcdio-devel] Vulnerable use of strcpy in iso9660_fs.c

2024-04-08 Thread Pete Batard
Hi Thomas, Thanks for the input. At least in Rufus (and most likely in the proposal I submit) I'm not going to bother trying to "guess" what the maximum possible size of a trick UTF-8 string might be, because, if the Unicode Comittee decides to add a bunch of new codepages where a UTF-16 seque

Re: [Libcdio-devel] Vulnerable use of strcpy in iso9660_fs.c

2024-04-08 Thread Thomas Schmitt via Libcdio-devel
Hi, Pete Batard wrote: > Or maybe there's a mathematical proof that > a UTF-8 glyph byte encoding can never be larger than 1.5 the UTF-16 glyph > byte encoding I thought to have given one. Let me try again: https://datatracker.ietf.org/doc/html/rfc3629 "In UTF-8, characters from the U+..