)]}' { "log": [ { "commit": "4fbe409cb84e9ae89f22c6f3e80580ee49dbc0a2", "tree": "e2067593237107b4183be8ff823de7d3db743a88", "parents": [ "5502b56f34f9703cf053be46e4ea5685c0c9ac26" ], "author": { "name": "Gilad Arnold", "email": "garnold@chromium.org", "time": "Wed Apr 17 10:00:55 2013 -0700" }, "committer": { "name": "ChromeBot", "email": "chrome-bot@google.com", "time": "Tue Apr 23 10:39:12 2013 -0700" }, "message": "paycheck: perform payload integrity check by default\n\nCurrently, paycheck requires that --check, or one of its sub-options\n(e.g. --type), is specified explicitly on the command-line in order to\ntrigger full payload checking. This means that invoking paycheck without\n*any* optional arguments will amount to loading the payload manifest and\nquitting. This is not a useful behavior.\n\nInstead, we want payload integrity check to be the default behavior when\nnothing else is requested. This also edits the help text to clarify the\ndistinction between verifying/applying a payload, and what guarantees\nare provided wrt the actual CrOS update engine.\n\nBUG\u003dNone\nTEST\u003dPayload checking triggered when no other argument is given; passes\nunit/integrity testing.\n\nChange-Id: I8199813d4654f5598fcf152a3cdc62efbfc533da\nReviewed-on: https://gerrit.chromium.org/gerrit/48373\nTested-by: Gilad Arnold \u003cgarnold@chromium.org\u003e\nReviewed-by: Darin Petkov \u003cpetkov@chromium.org\u003e\nCommit-Queue: Gilad Arnold \u003cgarnold@chromium.org\u003e\n" }, { "commit": "5502b56f34f9703cf053be46e4ea5685c0c9ac26", "tree": "5d1eb5c4d0fb8016ae03698d5a89451fcde5bde7", "parents": [ "857223b4118d7b4d9bd988d996db00d7ea313029" ], "author": { "name": "Gilad Arnold", "email": "garnold@chromium.org", "time": "Fri Mar 08 13:22:31 2013 -0800" }, "committer": { "name": "ChromeBot", "email": "chrome-bot@google.com", "time": "Fri Apr 05 17:02:56 2013 -0700" }, "message": "paycheck: unit tests + fixes to checker module\n\nThis adds missing unit tests for the checker module, bundled with fixes\nto some bugs that surfaced due to unit tests. This includes:\n\n* A fake extent (signified by start_block \u003d\u003d UINT64_MAX) that\n accompanies a signature data blob bears different requirements than\n previously implemented. Specifically, the extent sequence must have\n exactly one extent; and the number of blocks is not necessarily one,\n rather it is the correct number that corresponds to the actual length\n of the signature blob.\n\n* REPLACE/REPLACE_BZ operations must contain data.\n\n* MOVE operation validation must ensure that all of the actual message\n extents are being used.\n\n* BSDIFF operation must contain data (the diff).\n\n* Signature pseudo-operation should be a REPLACE.\n\nBUG\u003dchromium-os:34911,chromium-os:33607,chromium-os:7597\nTEST\u003dPasses unittests (upcoming); works with actual payloads.\n\nChange-Id: I4d839d1d4da1fbb4a493b208958a139368e2c8ca\nReviewed-on: https://gerrit.chromium.org/gerrit/45429\nTested-by: Gilad Arnold \u003cgarnold@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nCommit-Queue: Gilad Arnold \u003cgarnold@chromium.org\u003e\n" }, { "commit": "857223b4118d7b4d9bd988d996db00d7ea313029", "tree": "a87ec077e1f364dfb885a7c10faac5824d69b8b6", "parents": [ "aa55d1a133cced2e084e69d5b1dd4d17c0e0d054" ], "author": { "name": "Chris Sosa", "email": "sosa@chromium.org", "time": "Fri Mar 29 14:31:43 2013 -0700" }, "committer": { "name": "ChromeBot", "email": "chrome-bot@google.com", "time": "Fri Mar 29 22:37:37 2013 -0700" }, "message": "Modify paycheck to print out hashes in base64.\n\nBoth the update engine and sha256_partitions.sh print out hashes in\nbase64 encoding. Let\u0027s stay consistent with ourselves so we can diagnose\nhash mismatches correctly.\n\nBUG\u003dNone\nTEST\u003dRan it with a delta payload and compared hashes with sha256_partitions.sh\nand logs from applying it in the update_engine.\n\nChange-Id: I90c511b936792a073fbe069065ff53c24f47041c\nReviewed-on: https://gerrit.chromium.org/gerrit/46910\nCommit-Queue: Chris Sosa \u003csosa@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nTested-by: Chris Sosa \u003csosa@chromium.org\u003e\n" }, { "commit": "aa55d1a133cced2e084e69d5b1dd4d17c0e0d054", "tree": "db717fba16213ecbca4e12567c6f28f7cbacfbea", "parents": [ "553b0ec49bc64fc4b7df4358cd31396a87276d2b" ], "author": { "name": "Gilad Arnold", "email": "garnold@chromium.org", "time": "Fri Mar 08 12:05:59 2013 -0800" }, "committer": { "name": "ChromeBot", "email": "chrome-bot@google.com", "time": "Fri Mar 15 15:04:31 2013 -0700" }, "message": "Fix update out-of-bounds check for partition boundary.\n\nThis is an off-by-one error caught during the implementation of unit\ntests.\n\nBUG\u003dNone\nTEST\u003dUnit tests (upcoming) pass as expected.\n\nChange-Id: I9a5da10588f0ac4314e9a35280ff1f38c34c88ac\nReviewed-on: https://gerrit.chromium.org/gerrit/44953\nTested-by: Gilad Arnold \u003cgarnold@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nCommit-Queue: Gilad Arnold \u003cgarnold@chromium.org\u003e\nReviewed-by: Don Garrett \u003cdgarrett@chromium.org\u003e\n" }, { "commit": "553b0ec49bc64fc4b7df4358cd31396a87276d2b", "tree": "ae430c299339c9480d12c2d2da0be419426aa55d", "parents": [ "516f0f7a3d13b74f7bf6f5fb8573f5900c1eb94f" ], "author": { "name": "Gilad Arnold", "email": "garnold@chromium.org", "time": "Sat Jan 26 01:00:39 2013 -0800" }, "committer": { "name": "ChromeBot", "email": "chrome-bot@google.com", "time": "Fri Mar 08 12:01:42 2013 -0800" }, "message": "Update payload library + command-line tool\n\nAn initial implementation of a Python module for parsing, checking and\napplying a Chrome OS update payload. Comes with a command-line tool\n(paycheck.py) for applying such operations on payload files, and a test\nscript (test_paycheck.sh) for ensuring that the library and tool are\nworking correctly.\n\nSince update_payload is introduced as a package, we\u0027re moving some\npreviously merged utilities into the package\u0027s directory.\n\n(Unit testing for this code will be uploaded on a separate CL; see\nchromium-os:39663)\n\nBUG\u003dchromium-os:34911,chromium-os:33607,chromium-os:7597\nTEST\u003dtest_paycheck.sh successful on MP-signed payloads\nCQ-DEPEND\u003dI5746a1d80e822a575f0d96f94d0b4e765fc64507\n\nChange-Id: I77123a1fffbb2059c239b7145c6922968fdffb6a\nReviewed-on: https://gerrit.chromium.org/gerrit/43041\nReviewed-by: Gilad Arnold \u003cgarnold@chromium.org\u003e\nTested-by: Gilad Arnold \u003cgarnold@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nReviewed-by: Jay Srinivasan \u003cjaysri@chromium.org\u003e\nReviewed-by: Don Garrett \u003cdgarrett@chromium.org\u003e\nCommit-Queue: Gilad Arnold \u003cgarnold@chromium.org\u003e\n" }, { "commit": "516f0f7a3d13b74f7bf6f5fb8573f5900c1eb94f", "tree": "5cd340da981c44b58b41785656565787f1316eaa", "parents": [ "9c950103182df9867b32f77756dda64a49439cf1" ], "author": { "name": "Gilad Arnold", "email": "garnold@chromium.org", "time": "Fri Feb 22 12:14:16 2013 -0800" }, "committer": { "name": "ChromeBot", "email": "chrome-bot@google.com", "time": "Tue Feb 26 14:48:12 2013 -0800" }, "message": "Move update_metadata_pb2.py to host/lib/update_payload\n\nThis is necessary for proper packaging of the upcoming update_payload\nlibrary. Has to be done in a separate CL so that pylint checks can be\ndisabled (--no-verify).\n\nBUG\u003dNone\n\nTEST\u003dNone\n\nChange-Id: I5746a1d80e822a575f0d96f94d0b4e765fc64507\nReviewed-on: https://gerrit.chromium.org/gerrit/43809\nTested-by: Gilad Arnold \u003cgarnold@chromium.org\u003e\nReviewed-by: Chris Sosa \u003csosa@chromium.org\u003e\nCommit-Queue: Gilad Arnold \u003cgarnold@chromium.org\u003e\n" }, { "commit": "9c950103182df9867b32f77756dda64a49439cf1", "tree": "4b825dc642cb6eb9a060e54bf8d69288fbee4904", "parents": [], "author": { "name": "rtc@google.com", "email": "rtc@google.com@06c00378-0e64-4dae-be16-12b19f9950a1", "time": "Mon Oct 26 22:36:21 2009 +0000" }, "committer": { "name": "rtc@google.com", "email": "rtc@google.com@06c00378-0e64-4dae-be16-12b19f9950a1", "time": "Mon Oct 26 22:36:21 2009 +0000" }, "message": "Adds a local Autoupdate server and a mechanism for adding developer packages.\n\nI\u0027ve been getting frustrated by juggling usb sticks to constantly update my netbook so I wrote a simple\nserver that can run in a developer\u0027s source tree and serve updates to a netbook. I also added an upstart\ntask that will download a script from the dev server and run it. I use this to install sshfs, gdb, and vim.\n\nHere\u0027s a quick heads up about what has changed. \n\n1. /etc/lsb-release\n\nI added two new fields to the release file. One is the URL that should be pinged for updates. The other is the URL that can be used to download a developer setup script. \n\n2. chromeos_version.sh\n\nThe functionality for the release build is unchanged, however, developer builds now have a monotonically increasing version number. \n\n3. software-update.conf\n\nAutoupdate is disabled when the DEV_SERVER field in /etc/lsb-release is initialized. This field won\u0027t be set on the build server, but will be set everywhere else. \n\n4. ping_omaha.sh\n\nThe omaha server is now configured by /etc/lsb-release\n\nReview URL: http://chromereview.prom.corp.google.com/1175098\n\ngit-svn-id: svn://chrome-svn/chromeos/trunk@92 06c00378-0e64-4dae-be16-12b19f9950a1\n" } ] }