Glibc Buffer Overflow in Iconv

Re:Glibc Buffer Overflow in Iconv by bawolff on Sunday April 21, 2024 @05:15AM (#40104254)

We will always have to read historical formats from time to time. UTF-8 already has extremely good penetration.

[ Parent | on HN ]

Re:Glibc Buffer Overflow in Iconv by Longhanks on Sunday April 21, 2024 @05:37AM (#40104350)

Cries in WinAPI

[ Parent | on HN ]

Re:Glibc Buffer Overflow in Iconv by jsheard on Sunday April 21, 2024 @05:53AM (#40104411)

They're getting there, starting from later builds of Windows 10 there's a manifest flag you can set on your executables which makes all of the legacy ASCII interfaces accept and return UTF-8 instead. Windows is probably just converting to and from UTF-16 internally but that's not your problem anymore.

[ Parent | on HN ]

Re:Glibc Buffer Overflow in Iconv by im3w1l on Sunday April 21, 2024 @06:22AM (#40104526)

Will it refuse to run on older versions of windows or silently do the wrong thing?

[ Parent | on HN ]

Re:Glibc Buffer Overflow in Iconv by jsheard on Sunday April 21, 2024 @06:27AM (#40104541)

I believe it silently does the wrong thing so you should probably enforce a minimum Windows version by some other means. The last version to not support that UTF-8 flag has been officially EOL for years so cutting it off completely is on the table, depending on your audience.

[ Parent | on HN ]

Re:Glibc Buffer Overflow in Iconv by andreyv on Sunday April 21, 2024 @06:48AM (#40104627)

Even the original version 1507 is still supported on the LTSC channel. Support for UTF-8 manifest was added only in version 1903.

[ Parent | on HN ]

Re:Glibc Buffer Overflow in Iconv by Tempest1981 on Sunday April 21, 2024 @11:07AM (#40106324)

Maybe this? https://learn.microsoft.com/en-us/windows/apps/design/global...

[ Parent | on HN ]

Re:Glibc Buffer Overflow in Iconv by pjmlp on Sunday April 21, 2024 @06:04AM (#40104449)

Isn't that bad actually, (licks WinRT scars).

[ Parent | on HN ]