diff options
author | Allan Sandfeld Jensen <allan.jensen@qt.io> | 2022-02-04 17:20:24 +0100 |
---|---|---|
committer | Allan Sandfeld Jensen <allan.jensen@qt.io> | 2022-02-12 08:15:25 +0000 |
commit | 8fa0776f1f79e91fc9c0b9c1ba11a0a29c05196b (patch) | |
tree | 788d8d7549712682703a0310ca4a0f0860d4802b /chromium/docs/website/site/chromium-os/testing/autotest-developer-faq/ssh-test-keys-setup/index.md | |
parent | 606d85f2a5386472314d39923da28c70c60dc8e7 (diff) | |
download | qtwebengine-chromium-8fa0776f1f79e91fc9c0b9c1ba11a0a29c05196b.tar.gz |
BASELINE: Update Chromium to 98.0.4758.90
Change-Id: Ib7c41539bf8a8e0376bd639f27d68294de90f3c8
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>
Diffstat (limited to 'chromium/docs/website/site/chromium-os/testing/autotest-developer-faq/ssh-test-keys-setup/index.md')
-rw-r--r-- | chromium/docs/website/site/chromium-os/testing/autotest-developer-faq/ssh-test-keys-setup/index.md | 83 |
1 files changed, 83 insertions, 0 deletions
diff --git a/chromium/docs/website/site/chromium-os/testing/autotest-developer-faq/ssh-test-keys-setup/index.md b/chromium/docs/website/site/chromium-os/testing/autotest-developer-faq/ssh-test-keys-setup/index.md new file mode 100644 index 00000000000..7bf2f148c4b --- /dev/null +++ b/chromium/docs/website/site/chromium-os/testing/autotest-developer-faq/ssh-test-keys-setup/index.md @@ -0,0 +1,83 @@ +--- +breadcrumbs: +- - /chromium-os + - Chromium OS +- - /chromium-os/testing + - Testing Home +- - /chromium-os/testing/autotest-developer-faq + - Autotest Developer FAQ +page_name: ssh-test-keys-setup +title: Setting up SSH Access to your test device. +--- + +## In order to run the automated tests against your device you need to ensure it is running a Test Image and you have password-less SSH Access. + +1. First make sure you have a Chrome OS Device with a Test Image installed. + +* If you are a Google partner, please contact your Google + representative for Google Storage access to our builds for for + automated re-imaging of your test devices via the devserver + (described below). +* Otherwise: + * Download a test image from the public waterfall + <http://build.chromium.org/p/chromiumos/waterfall> + * Or build a test image. + * <http://www.chromium.org/chromium-os/developer-guide#TOC-Building-Chromium-OS> + * Once you have a test image, install it on your test device. + * <http://www.chromium.org/chromium-os/developer-guide#TOC-Installing-Chromium-OS-on-your-Device> + +2. Next, install the RSA keys to allow you SSH into the device. + +* Download the testing RSA keys into ~/.ssh/ (on your test server). + * You can get the key from the chromiumos checkout under + ***chromiumos/src/scripts/mod_for_test_scripts/ssh_keys/testing_rsa*** + * Or download from + <https://chromium.googlesource.com/chromiumos/chromite/+/HEAD/ssh_keys> +* Restrict the permissions on ~/.ssh/testing_rsa; SSH will ignore the + file if the permissions are too open: + +```none +$ chmod 0600 ~/.ssh/testing_rsa +``` + +* Add an entry for your device in your ~/.ssh/config: + +```none +Host device + HostName 172.22.168.233 # The IP address of the Chrome OS Device. + CheckHostIP no + StrictHostKeyChecking no + IdentityFile %d/.ssh/testing_rsa + Protocol 2 + User root +``` + +* Once you have done both steps verify you have password less login as + root: + +```none +$ ssh device +Warning: Permanently added '172.22.168.233' (RSA) to the list of known hosts. +Last login: Mon Mar 17 14:21:30 PDT 2014 from 172.18.72.8 on ssh +localhost ~ # +``` + +* If connecting to multiple test devices, you can share common config + options in your ~/.ssh/config: + +```none +Host 172.22.168.* # The subnet containing your Chrome OS test devices. + CheckHostIP no + StrictHostKeyChecking no + IdentityFile %d/.ssh/testing_rsa + Protocol 2 + User root +Host device1 + HostName 172.22.168.233 # The IP address of the first Chrome OS Device. +Host device2 + HostName 172.22.168.234 # The IP address of the second Chrome OS Device. +``` + +**Note:** you can also reach your device via ssh if using a Dev image, but you +will need to enable the debugging features on the setup screen after a flash or +powerwash.
\ No newline at end of file |