History log of /external/autotest/server/site_tests/autoupdate_CatchBadSignatures/autoupdate_CatchBadSignatures.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
0c6c88721884cf40bfb9bca64cc0597d9cd2a909 17-Aug-2016 YH Lin <yueherngl@google.com> autoupdate_CatchBadSignatures: update payload and modify the test accordingly

Modify the relevant information against the new payload
autoupdate_CatchBadSignatures-payload-sentry-R54-8719.0.2016_08_18_2057-a1
as well as the instructionsi for generating it.

BUG=chrome-os-partner:55273,chromium:575960
TEST=Manually

# With devserver already started
$ cd ~/trunk/src/scripts
$ test_that -b ${BOARD} --fast <DUT_IP> autoupdate_CatchBadSignatures

Change-Id: I802c9d5853faeb492817a143d60088632c90e403
Reviewed-on: https://chromium-review.googlesource.com/371621
Commit-Ready: YH Lin <yueherngl@chromium.org>
Tested-by: YH Lin <yueherngl@chromium.org>
Reviewed-by: David Zeuthen <zeuthen@chromium.org>
/external/autotest/server/site_tests/autoupdate_CatchBadSignatures/autoupdate_CatchBadSignatures.py
69b9b975fccab1ede1e8849ed17e7e655a9d6b48 16-Apr-2016 Dan Shi <dshi@google.com> [autotest] Add hostname in devserver resolve calls

This is to make sure any attempt to resolve a devserver is able to pick a
devserver in the same subnet of the dut if it's in a restricted subnet.

BUG=chromium:577363
TEST=unittest, test push

Change-Id: If959865ef8ba04fa92299acc5b3c8c2d3bd8691b
Reviewed-on: https://chromium-review.googlesource.com/339215
Commit-Ready: Dan Shi <dshi@google.com>
Tested-by: Dan Shi <dshi@google.com>
Reviewed-by: Fang Deng <fdeng@chromium.org>
/external/autotest/server/site_tests/autoupdate_CatchBadSignatures/autoupdate_CatchBadSignatures.py
d5e2a869962711baa06c1e3e4f5917e8d84e77f4 15-May-2015 Christopher Wiley <wiley@chromium.org> Remove assorted comment references to run_remote_tests

BUG=brillo:1067
TEST=None

Change-Id: Icb24b3b75b46c7b320b83f344e955f0fdbe0b002
Reviewed-on: https://chromium-review.googlesource.com/271550
Reviewed-by: Fang Deng <fdeng@chromium.org>
Commit-Queue: Christopher Wiley <wiley@chromium.org>
Tested-by: Christopher Wiley <wiley@chromium.org>
/external/autotest/server/site_tests/autoupdate_CatchBadSignatures/autoupdate_CatchBadSignatures.py
5c59a3887029a888787737bbddd5cd4963255014 12-Feb-2014 Chris Sosa <sosa@chromium.org> CatchBadSignatures: reboot at the end of the test to clean any stale state.

We've seen a report of AU leaving behind a stale tmp mount point after an AU
failure. Since this is not incorrect behavior but may fail another test after
it, let's just keep the test clean by rebooting at the end.

BUG=chromium:342896
TEST=Manual

Change-Id: I6e1fb7a70fa9ddb7c96cf0e92bd21546f1ab7cd8
Reviewed-on: https://chromium-review.googlesource.com/186137
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: David Zeuthen <zeuthen@chromium.org>
/external/autotest/server/site_tests/autoupdate_CatchBadSignatures/autoupdate_CatchBadSignatures.py
c4632b916099d01bc23755883efb721b1e8cba8a 03-Dec-2013 David Zeuthen <zeuthen@chromium.org> Add autoupdate_CannedOmahaUpdate client-side test.

Also use this new mechanism in autoupdate_CatchBadSignatures
server-side test to overcome the issue that DUTs are not allowed to
connect to Drones (as pointed out in CL:178314.)

BUG=chromium:264352
TEST=The autoupdate_CatchBadSignatures server-side test passes.

Change-Id: I93348e879f2de5c87a9209acbd8fd95ca3f76f69
Reviewed-on: https://chromium-review.googlesource.com/178632
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: David Zeuthen <zeuthen@chromium.org>
Commit-Queue: David Zeuthen <zeuthen@chromium.org>
/external/autotest/server/site_tests/autoupdate_CatchBadSignatures/autoupdate_CatchBadSignatures.py
c9a60f9b2acdefdbddc70f2ecd3971c2779602ad 21-Nov-2013 David Zeuthen <zeuthen@chromium.org> Add autoupdate_CatchBadSignatures test.

This is a test to verify that update_engine correctly checks
signatures in the metadata hash and the update payload itself. This is
achieved by feeding updates to update_engine where the private key
used to make the signature, intentionally does not match with the
public key used for verification.

BUG=chromium:264352
TEST=Successfully passed on lumpy and daisy.

Change-Id: I9bced8430052b42beeea17db3d13e213fea12bef
Reviewed-on: https://chromium-review.googlesource.com/177631
Reviewed-by: Alex Miller <milleral@chromium.org>
Tested-by: David Zeuthen <zeuthen@chromium.org>
Commit-Queue: David Zeuthen <zeuthen@chromium.org>
/external/autotest/server/site_tests/autoupdate_CatchBadSignatures/autoupdate_CatchBadSignatures.py