[roll] Roll fuchsia [ffx] Generate ssh keys if none found

This checks the `ssh.pub` and `ssh.priv` configuration values, and if
no existing keys are found, a new ed25519 key is generated and saved at
the location of the first value configured. This is typically
$HOME/.ssh/fuchsia_ed25519 and fuchsia_authorized_keys.

Typical usage would be to check for the existence when initializing
a device via flashing/paving, or starting an emulator instance. This
is preferred since generating the private key when attempting to access
a device already initialized is pointless.

Also addressed issues from `fx clippy`.

Original-Fixed: 97603, 76032
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/699186
Original-Revision: 4ced5dd5fdfcd64f60e5a4404d9dc494e2dc9f10
GitOrigin-RevId: 31cf7f57dc936d82522bf8c2f69b72d5412e8f3c
Change-Id: Ie9bcca38ad6329079e285628e508548efebf6759
1 file changed
tree: 99863b490e56abdb72cca0e8393fa08afd317fb4
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.