News for hackers. Stuff that matters.
Re:The growth of command-line options, 1979-Present by jackewiehose on Tuesday March 03, 2020 @07:10PM (#22480030)
> I eventually just gave up and made my script ignore any filenames containing \n

I think we can all do that. Did anyone ever came across a legitimate reason for filenames with newlines? All I can think of are intentionally bad-named files to exploit bugs. Those filenames should be avoided in the first place.

Re:The growth of command-line options, 1979-Present by strbean on Tuesday March 03, 2020 @08:10PM (#22480343)
Seems like a great argument for ensuring those are handled correctly, so you don't get bit by a maliciously named file.
Re:The growth of command-line options, 1979-Present by oblio on Wednesday March 04, 2020 @04:06AM (#22482220)
He is handling it correctly, he's ignoring those files.
Re:The growth of command-line options, 1979-Present by why-oh-why on Wednesday March 04, 2020 @07:45AM (#22483248)
Maybe being ignored (i.e. hidden) is the malicious intent.

What if the largest file on your drive has that filename and no tool can show it?