Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqvm-run -p --localcmd output is interpreted by shell instead of being sent to command in appvm #4040
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
homotopycolimit
Jun 27, 2018
A mimimal example:
qvm-run -p --localcmd "date;sleep 1" sys-net "cat > /tmp/foo"
gives
/bin/bash: line 1: Wed: command not found (at least on a Wednesday)
homotopycolimit
commented
Jun 27, 2018
|
A mimimal example:
gives
|
andrewdavidwong
added
bug
C: core
labels
Jun 28, 2018
andrewdavidwong
added this to the Release 4.0 updates milestone
Jun 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
homotopycolimit commentedJun 27, 2018
•
edited
Edited 2 times
-
homotopycolimit
edited Jun 27, 2018 (most recent)
-
homotopycolimit
edited Jun 27, 2018
-
homotopycolimit
created Jun 27, 2018
Qubes OS version:
R4.0
Affected component(s):
qvm-run
Steps to reproduce the behavior:
in dom0 run a
qvm-run -pcommand with the--localcmdoptionfor example:
qvm-run -p --localcmd="cmd0" $appvm "cat > /home/user/output"Expected behavior:
Expect the output of cmd0 to be passed to the command on the appvm side, i.e. in this example we expect the output to be written to /home/user/output
Actual behavior:
It seems as if the output of the localcmd (cmd0) is being sent to bash (qubes-VMShell?) on the appvm side instead of to
cat. It is trying to be interpreted by the shell!General notes:
This seems to potentially be a serious issue because the shell is interpreting things that it is not meant to.
Related issues: