Special characters handling on Linux

[darkk]

Linux has the following command generated while running node test.js (newlines added after ; for readability):

cd "/mnt/sudo-prompt";
export SUDO_PROMPT_TEST_ENV="hello world";
"/usr/bin/pkexec" --disable-internal-agent /bin/bash -c "echo SUDOPROMPT; echo \"$SUDO_PROMPT_TEST_ENV\""

The command has the following issues:

• pkexec changes workdir to /root, so the code fails to preserve CWD as cd is done in an "outer" shell and does not propagate through pkexec
• SUDO_PROMPT_TEST_ENV does not come from pkexec'ed environment, it comes from an "outer" shell. So, command env | grep ^SUDO_PROMPT_TEST_ENV= shows nothing
• working directory is wrapped with double quotes, so shell variable expansion is applied, e.g. the code fails to run in a directory named /mnt/$udo-prompt" with stderr: "/bin/sh: 1: cd: can't cd to /mnt/-prompt\n"
• variable value is wrapped with double quotes, so shell variable expansion is applied there as well

I can provide a PR with fixes, but some of the fixes may break backwards compatibility, and I ask for some guidance from the maintainer before submitting a PR.

1. may command echo "$PATH" change the behavior and show after-sudo PATH instead of before-sudo PATH? It refers to the difference between the following commands:

$ sudo sh -c "echo $HOME"
/home/node
$ sudo sh -c 'echo $HOME'
/root

2. may env {name: 'something like $million'} change the behavior and preserve $million as-is instead of doing shell variable expansion?
3. may the command be skipped if the script fails to change the directory?