-
Notifications
You must be signed in to change notification settings - Fork 161
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
ShellDriver.put_ssh_key not working on read-only filesystem #93
Comments
Emantor
referenced
this issue
in Emantor/labgrid
Nov 15, 2017
Previously we did a bind mount on just the authorized key file, this breaks if we have a read only file system. Create a directory in /tmp and bind mount the whole ~/.ssh directory instead. Fixes #93 Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Emantor
referenced
this issue
in Emantor/labgrid
Nov 15, 2017
Previously we did a bind mount on just the authorized key file, this breaks if we have a read only file system. Create a directory in /tmp and bind mount the whole ~/.ssh directory instead. Fixes #93 Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Emantor
referenced
this issue
in Emantor/labgrid
Nov 29, 2017
Previously we did a bind mount on just the authorized key file, this breaks if we have a read only file system. Create a directory in /tmp and bind mount the whole ~/.ssh directory instead. Fixes #93 Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Emantor
referenced
this issue
in Emantor/labgrid
Nov 29, 2017
Previously we did a bind mount on just the authorized key file, this breaks if we have a read only file system. Create a directory in /tmp and bind mount the whole ~/.ssh directory instead. Fixes #93 Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Emantor
referenced
this issue
in Emantor/labgrid
Nov 29, 2017
Previously we did a bind mount on just the authorized key file, this breaks if we have a read only file system. Create a directory in /tmp and bind mount the whole ~/.ssh directory instead. Fixes #93 Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
jluebbe
pushed a commit
that referenced
this issue
Dec 6, 2017
Previously we did a bind mount on just the authorized key file, this breaks if we have a read only file system. Create a directory in /tmp and bind mount the whole ~/.ssh directory instead. Fixes #93 Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Doing
ShellDriver.put_ssh_key()
on a read-only file system only results in a stacktrace for me:… which, in hindsight, is obvious, because on the target console:
On most freshly installed targets,
/root/.ssh
will most probably not exist, so on a read-only system,mkdir ~/.ssh
in ShellDriver.py, line 179 will fail. I'm guessing the read-write mount is only done a few lines later withmount --bind
, and if this works like I imagine, I think this issue could be solved by doing amount --bind
on the whole/root/
directory instead of only theauthorized_keys
file.The text was updated successfully, but these errors were encountered: