Re^2: Filenames named "..\n" (unix)

Given this, would it not be more of a feature to ignore a filename named "..\n" instead of a bug. If someone bothered to embed a "\n" in the filename I probably dont want to process it anyways!? :)

Comment on Re^2: Filenames named "..\n" (unix)

Replies are listed 'Best First'.
Re^3: Filenames named "..\n" (exploits) by tye (Sage) on Aug 02, 2005 at 06:07 UTC
Exploits often justify paranoia... You wouldn't want your script that looks for set-UID exploits to miss one because the cracker put it in a file named "..\n". - tye	[reply]
Re^4: Filenames named "..\n" (exploits) by zzspectrez (Hermit) on Aug 02, 2005 at 06:09 UTC
true, true... In that case you want them all..	[reply]
Re^4: Filenames named "..\n" (exploits) by Anonymous Monk on Aug 02, 2005 at 08:31 UTC
If you have a cracker that can create set-UID exploits, the fact the file name has a newline in it is the least of your worries.	[reply]


"be consistent"
	PerlMonks