Talk:Input Field Separators
solution to the IFS hack? Full Decent (talk) 13:10, 24 June 2009 (UTC)Reply
 | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
solution
solution to the IFS hack? Full Decent (talk) 13:10, 24 June 2009 (UTC)
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)
Stating that IFS is incorrectly referred to as "Internal Field Separator" is wrong
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)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.