News for hackers. Stuff that matters.

A comment on Glibc Buffer Overflow in Iconv. Parent comment

Re:Glibc Buffer Overflow in Iconv by snnn on Sunday April 21, 2024 @07:49PM (#40110236)
Because that's how "dirname(3)" is implemented in glibc, except it searches '/' instead of '\'. Here all character encodings share the same code.
[ Parent | on HN ]
Re:Glibc Buffer Overflow in Iconv by Karellen on Monday April 22, 2024 @03:46AM (#40112180)
But the byte '/' can never be part of any filename/dirname under a UNIX filesystem. Which kinda sucks generally for anyone wanting to use a charset like that, but doesn't it also mean that should never be a problem for `dirname()`?

I'm struggling to imagine how this failure would manifest. Can you give an example of how dirname() would fail? What combination of existing file/directory name, and usage of that function, would not work as expected?

Edit: I'm also a bit confused how this counts as being a problem for "modern Linux systems" - wouldn't it have always been a problem for all Unix-based OSs?

[ Parent | on HN ]