lhunath 1286807185 learn xargs(1) is dangerous (broken) when processing filenames that are not NUL-terminated. If you're working with filenames, use find's -exec {} + instead (yes, it does multiple-filenames-per-invocation, too).
nDuff 1345062087 forget
nDuff 1345062116 learn xargs(1) is dangerous (broken) when processing lists that are not NUL-delimited. If you're working with filenames, use find's -exec {} + instead (yes, it does multiple-filenames-per-invocation, too).
twmb 1345062139 forget
twmb 1345062160 learn xargs(1) is dangerous (broken) when processing lists that are not NUL-delimited. If you're working with filenames, use find's -exec {} + instead (yes, it does multiple-filenames-per-invocation, too).
sjohnson 1345063283 forget
sjohnson 1345063290 learn xargs(1) is dangerous (broken, exploitable, etc.) when processing lists that are not NUL-delimited. If you're working with filenames, use find's -exec {} + instead (yes, it does multiple-filenames-per-invocation, too), or xargs -0, provided it is available and portability is not a concern.
lhunath 1374775669 forget
lhunath 1374775727 learn xargs(1) is dangerous (broken, exploitable, etc.) when reading non-NUL-delimited input. If you're working with filenames, use find's -exec {} + instead or -print0 | xargs -0 provided you don't care about portability and like doing unnecessary extra work.
lhunath 1374775838 forget
lhunath 1374775860 learn xargs(1) is dangerous (broken, exploitable, etc.) when reading non-NUL-delimited input. If you're working with filenames, use find's -exec [command] {} + instead or -print0 | xargs -0 provided you don't care about portability and like doing unnecessary extra work.
geirha 1388256781 forget
geirha 1388256784 learn xargs(1) is dangerous (broken, exploitable, etc.) when reading non-NUL-delimited input. If you're working with filenames, use find's -exec [command] {} + instead or -print0 | xargs -0 unless you don't care about portability and like doing unnecessary extra work.
geirha 1388256845 forget
geirha 1388256858 learn xargs(1) is dangerous (broken, exploitable, etc.) when reading non-NUL-delimited input. If you're working with filenames, use find's -exec [command] {} + instead or -print0 | xargs -0 provided you don't care about portability and like doing unnecessary extra work.
lhunath 1421865223 forget
lhunath 1421865235 learn xargs(1) is dangerous (broken, exploitable, etc.) when reading non-NUL-delimited input. If you're working with filenames, use find's -exec [command] {} + instead.
lhunath 1421865271 forget
lhunath 1421865307 learn xargs(1) is dangerous (broken, exploitable, etc.) when reading non-NUL-delimited input. If you're working with filenames, use find's -exec [command] {} + instead. If you can get NUL-delimited output, use xargs -0. Otherwise, you probably want a while read or for loop instead.