Although I doubt I'll ever get into trouble, if GNU parallel is
restrictive then the only thing I'll lose is a run and I'll have a log
to work with.
Warnings are ignored by people.
On Sun, Feb 23, 2025 at 12:27 PM Ole Tange wrote:
>
> GNU Parallel has had a (theoretical) security issue a few yea
On Sun, 23 Feb 2025, Ole Tange wrote:
> This of course has a negative effect when I restrict e.g. $PWD can only
> contain [-a-z0-9_+,.%@:/= ] and gives the bad experience
Good: [-_.a-zA-Z0-9/]
Bad: [+,=]
Ugly: ["'#!%@: ]
scp and crontab don't like the ugly ones but those characters are of
cource
On Sun, Feb 23, 2025 at 5:45 PM William Bader wrote:
>
> Could you have a middle option to allow unicode in general that checks that
> $PWD does not contain certain characters while still blocking control
> characters and characters with special meanings in shells?
I will prefer to express what
GNU Parallel has had a (theoretical) security issue a few years back:
https://lists.gnu.org/archive/html/parallel/2015-04/msg00045.html
Therefore GNU Parallel tries to be conservative to avoid surprising
results. --unsafe will allow GNU parallel to run in environments and
on input that are unteste
