Follow-up Comment #3, bug #64816 (project findutils):
> [...] shells don't work very well with NULL delimited output.
I'm not sure I follow this statement.
Actually, NUL-terminated processing is the safest way of file name
processing with tools in shells, because the NUL character is the only one
(apart from a directory separator) which cannot be part of a file name.
Therefore, instead of going the route further down to use escaped strings
in find/xargs for further processing, the better way is IMO to give better
support of NUL-terminated in-/output to all tools.
The recent addition of the '-files0-from ...' option in find(1) was exactly
doing that.
The above is addressing the area of safely processing of file names in
combination
with other tools via shell scripts/pipes, etc.
The discussion about 'find -ls' displaying information to the terminal and
which
quoting style to be chosen best is a different one.
The point here is that the output should be safe no matter what malicious
file
an attacker might have placed, i.e., it should not disturb the terminal
settings.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64816>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
