-
Notifications
You must be signed in to change notification settings - Fork 180
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
write_file does not properly escape file names #1392
Comments
Yep, looks like we are missing a |
Not just the directories:
|
I meant that both arguments to Hm, I do wonder who ends up interpreting the commands, AFAICS we always use Edit: It is indeed the expansion done by SSH. |
From ssh(1):
|
Yep, please open a PR if you find the time. |
fixes labgrid-project#1392 Signed-off-by: Florian Hars <[email protected]>
Use the wrap_command() function to escape command arguments in case a remote operation over SSH is done. Fixes labgrid-project#1392 Alternative to labgrid-project#1450 Signed-off-by: Rouven Czerwinski <[email protected]>
Use the wrap_command() function to escape command arguments in case a remote operation over SSH is done. Fixes labgrid-project#1392 Alternative to labgrid-project#1450 Signed-off-by: Rouven Czerwinski <[email protected]>
Somewhere along the way from
write_files
throughProcessWrapper
,subprocess.Popen
,ssh
to the finalcp
command, there seems to be a shell (I suspect ssh) that expands file names, so things fail if filenames contain spaces. Or other interesting things:The text was updated successfully, but these errors were encountered: