New issue
Advanced search Search tips

Issue 834086 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Feature



Sign in to add a comment

Crostini image to include openssh server

Project Member Reported by joelhockey@chromium.org, Apr 17 2018

Issue description

Openssh server is required for FilesApp to do SFTP mount and make crositini files accessible.
 
Components: Platform>Apps>FileManager OS>Systems>Containers
Owner: chirantan@chromium.org
Labels: M-68
Labels: Hotlist-Crostini-Files
Cc: smbar...@chromium.org
Is there a doc for describing how this works? I have some concerns:

First, I don't think we should ship a container that out-of-the-box has services listening over TCP/UDP.

Disregarding the above, installing openssh in the container means that we cannot rely on it. The user is free to trash the container as they see fit, including uninstalling openssh-server, changing the port/auth mechanisms, deleting SSH keys, ...

SSH could be lddtree'd and run in the container, or just be run via maitred.
Doc at https://docs.google.com/document/d/1vZPG4iOq2HHdqL9a98QBAModHVDS7etHmnNrD58huUg/edit

We are aware that users may perform actions like you mention (uninstall sshd, change keys) which would break the files integration.  We assume that these users know what they are doing, and they will not be surprised/upset at what breaks.

I'm not familiar with lddtree or maitred.  Are you suggesting an alternative way that an ssh server could run outside the container and still have access to the files within the container?

So I think we want to do the same thing for the ssh server that we currently do for garcon and sommelier:  ship it with the termina component, bind mount it into the container, and have it listen on some non-standard port with its own custom config.

This way the user is free to install and run their own ssh server and be able to modify the config without having their files suddenly disappear.

Comment 9 Deleted

i don't think the lddtree approach works here.  ssh relies on quite a bit more than just `sshd` ... it needs config files, keys, and maybe even auth stacks (e.g. pam).
Cc: -smbar...@chromium.org chirantan@chromium.org joelhockey@chromium.org
Owner: smbar...@chromium.org
Set smbarber as owner.


Project Member

Comment 14 by bugdroid1@chromium.org, May 15 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/608649bd1bbc4912333437d8bf2187ea898ffe6d

commit 608649bd1bbc4912333437d8bf2187ea898ffe6d
Author: Stephen Barber <smbarber@chromium.org>
Date: Tue May 15 21:13:15 2018

vm_tools: maitred: set /run/sshd/ to sticky dir

BUG= chromium:834086 
TEST=run_container script can add ssh keys

Change-Id: I585c0349498d010b9364b229208b04948fa0805f
Reviewed-on: https://chromium-review.googlesource.com/1056496
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>

[modify] https://crrev.com/608649bd1bbc4912333437d8bf2187ea898ffe6d/vm_tools/maitred/init.cc

Project Member

Comment 16 by bugdroid1@chromium.org, May 19 2018

Status: Fixed (was: Assigned)
Fixed, will land with the next VM uprev.
Labels: -Restrict-View-Google

Sign in to add a comment