New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

qvm-run -p --localcmd output is interpreted by shell instead of being sent to command in appvm #4040

Open
homotopycolimit opened this Issue Jun 27, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@homotopycolimit

homotopycolimit commented Jun 27, 2018

Qubes OS version:

R4.0

Affected component(s):

qvm-run

Steps to reproduce the behavior:

in dom0 run a qvm-run -p command with the --localcmd option

for 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:

@homotopycolimit

This comment has been minimized.

Show comment
Hide comment
@homotopycolimit

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)

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment