Talk:Input Field Separators

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Computing

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

solution

Latest comment: 13 years ago2 comments2 people in discussion

solution to the IFS hack? Full Decent (talk) 13:10, 24 June 2009 (UTC)Reply

This page is pointed to by shebang as an example of a hack similar to the symbolic-link attack for shebang. I would guess that setting IFS before running a setuid program that uses it could cause all kinds of nasty shenanigans, it would be nice if somebody added some official information about this, including whether current systems have this problem and what solutions were done.Spitzak (talk) 17:28, 8 December 2012 (UTC)Reply

Stating that IFS is incorrectly referred to as "Internal Field Separator" is wrong

Latest comment: 3 years ago1 comment1 person in discussion

The bash manual page refers to it as "Internal Field Separator" for instance, so to say that the naming is wrong would be unfair and misinformation online would be incorrect. RisingTzar (talk) 22:32, 6 June 2023 (UTC)Reply

This page was redesigned at the edge.

solution

Stating that IFS is incorrectly referred to as "Internal Field Separator" is wrong