/data no longer viable for providing SSH keys |
|||
Issue descriptionFuchsia now includes a /data minfs volume in the SDK FVM image. We need to supply keys through some other path. The planned approach is to insert the key into the boot image zircon.zbi.
,
Nov 7
,
Nov 8
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2d5d35d8aa91dd959ba9bf5bf9be30d89137332d commit 2d5d35d8aa91dd959ba9bf5bf9be30d89137332d Author: Kevin Marshall <kmarshall@chromium.org> Date: Thu Nov 08 02:52:34 2018 Fuchsia: Include SSH keys in zircon.zbi, eliminate FVM creation. Fuchsia's SDK FVM file now includes its own minfs partition which collides with the minfs partition that we create in our runner scripts. We relied on the partition to supply client public keys to sshd on the device. This change adds the keys directly to the Zircon boot image at runtime and boots using the modified image. Rolls SDK to 9853d7bcb5f3944a9f3e599dbd4ec6ee1ce95852. Bug: 902908 Change-Id: I5bb15756039d1b3b58a4f3989b13a5b88496d1fd Reviewed-on: https://chromium-review.googlesource.com/c/1324234 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#606302} [modify] https://crrev.com/2d5d35d8aa91dd959ba9bf5bf9be30d89137332d/build/fuchsia/boot_data.py [modify] https://crrev.com/2d5d35d8aa91dd959ba9bf5bf9be30d89137332d/build/fuchsia/device_target.py [modify] https://crrev.com/2d5d35d8aa91dd959ba9bf5bf9be30d89137332d/build/fuchsia/linux.sdk.sha1 [modify] https://crrev.com/2d5d35d8aa91dd959ba9bf5bf9be30d89137332d/build/fuchsia/qemu_target.py [modify] https://crrev.com/2d5d35d8aa91dd959ba9bf5bf9be30d89137332d/third_party/fuchsia-sdk/gen_build_defs.py
,
Nov 8
|
|||
►
Sign in to add a comment |
|||
Comment 1 by kmarshall@chromium.org
, Nov 7Status: Assigned (was: Untriaged)