[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#969634: ITP: shellescape -- Escape arbitrary strings for use as command line arguments



Description : Escape arbitrary strings for use as command line arguments

Generally this is the wrong approach and commands should be run
through fork+exec instead of escaping them and passing them through
the shell.

https://bonedaddy.net/pabs3/log/2014/02/17/pid-preservation-society/

escargs utility escargs reads lines from the standard input and prints shell-escaped versions. Unlinke xargs, blank lines on the standard input are
 not discarded.

There is already the shell-quote too from libstring-shellquote-perl in
Debian if you want something to run from an interactive shell.

Also xargs doesn't discard blank lines if you don't use the unsafe
variants of it. xargs without the -d or -0 options is unsafe.

My reason for packaging this is to use the Go library to later package pistol (https://github.com/doronbehar/pistol) which uses it to quote file paths before executing a user configurable command with `sh -c`.

However I wasn't aware that the functionality was already offered by libstring-shellquote-perl so I should've mentioned this in the description.

As a new maintainer does this mean I should only provide the library?

--
Thanks,
Jai


Reply to: