)]}' { "log": [ { "commit": "2d30a2f5b1c81eb61de4bf82180a910d45f22e81", "tree": "c0dbf217af4d4b908d3ff23fff2b0d2c54f355ee", "parents": [ "d187cd3fc792f8bcefbee4587c83eafbd08441fc" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Mon Mar 07 23:20:56 2016" }, "committer": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Mon Mar 07 23:38:57 2016" }, "message": "Import vboot_reference under _vboot_reference\n\nvboot_reference has been copied to this repository prior to this change\nThus, all commits below here originate from vboot_reference.\n\nFiles under _vboot_reference will not be modified in place but they\u0027ll be\nmoved out of the directory (then modified) as needed by v3. This way, we\ncan trace the history of the files which originate from vboot_reference.\n\nBUG\u003dnone\nBRANCH\u003dtot\nTEST\u003dnone\n\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\n" }, { "commit": "d187cd3fc792f8bcefbee4587c83eafbd08441fc", "tree": "d6131fce72fb414346dec9f34b3249e1007dd82d", "parents": [ "478b6d34afb9fd98daf0663dd6093d8f058a9f34" ], "author": { "name": "Duncan Laurie", "email": "dlaurie@chromium.org", "time": "Sat Feb 20 04:20:10 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Feb 24 00:58:50 2016" }, "message": "vb2: Modify phase2 behavior for S3 resume case\n\nIf a platform does verification of memory init then it must be careful\nto use the same slot for resume that it booted from. This is\naccomplished by adding a context flag to indicate this is an S3 resume\nand that vboot should treat it differently than a normal boot.\n\nWhen this flag is set then the same slot that was booted is read from\nVBNV and re-used for the resume path, without adjusting any try flags.\nIf this slot is B then the related context flag is set.\n\nThis will allow the firmware updater to update the other (non-booted)\nslot and set flags indicating that on the next boot the updated slot\nshould be tried, while still allowing suspend/resume to work with the\nexisting firmware slot.\n\nThis assumes that the last tried slot was successfully booted, which\nshould be a safe assumption since the system was able to boot and then\nsuspend. It isn\u0027t reliable to check last_fw_result for \"success\"\nstatus because that status is only set some time after boot when\nchromeos-setgoodkernel calls chromeos-firmwareupdate --mode\u003dbootok\nand so it may still report a status of \"trying\" on resume depending\non how soon after boot the suspend happened.\n\nIt also avoids setting the vboot flag indicating that a slot choice\nwas made in order to avoid altering the try counter on failure since\nthis is explicitly not attempting to boot the new slot.\n\nBUG\u003dchromium:577269\nBRANCH\u003dglados\nTEST\u003dmanually tested on chell:\n1) ensure that booting from slot A resumes from slot A.\n2) ensure that booting from slot B resumes from slot B.\n3) do RW update while booted from slot A (so the flags are set to try\nslot B) and ensure that suspend/resume still functions properly using\ncurrent slot A.\n4) do RW update while booted from slot B (so the flags are set to try\nslot A) and ensure that suspend/resume still functions properly using\ncurrent slot B.\n\nChange-Id: I500faef2b5d19a02f32839976354abf6d551c9f6\nSigned-off-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/328812\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "478b6d34afb9fd98daf0663dd6093d8f058a9f34", "tree": "b72e60c01d16d6817a8c746132048966c2d71f43", "parents": [ "933c4e7aa4b873f0ad9cd4c348a1ea4f37f66aa7" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Wed Jan 13 22:49:03 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Feb 03 22:59:16 2016" }, "message": "sign_nv_cbootimage: Update signing scripts for nv bootloader and lp0\n\nCurrently, nvidia tools do not provide the support to perform signing\nof bootloader or lp0 image. Thus, the signing script is updated to\nsupport this. Once, we have the required tools, this script can be\nsimplified again.\n\nCQ-DEPEND\u003dCL:*244234\nBUG\u003dchrome-os-partner:43018\nBRANCH\u003dnone\nTEST\u003dVerified that signed bootloader and lp0 work fine on dev-PKC\nfused devices.\n\nReference:\nhttps://code.google.com/p/chrome-os-partner/issues/attachmentText?id\u003d43018\u0026aid\u003d430180067000\u0026name\u003dsign-lp0.sh\u0026token\u003dABZ6GAcjz4b2mEk55WqREzwTnWWpEyE_7A%3A1452631308268\nhttps://code.google.com/p/chrome-os-partner/issues/attachmentText?id\u003d43018\u0026aid\u003d430180060000\u0026name\u003dsign.sh\u0026token\u003dABZ6GAcRky67XrzMOgKZfkJxr70qm-tTAg%3A1452631308240\n\nChange-Id: Icb024a1d9a61714df6e52d94c96cf43481cac869\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/321459\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "933c4e7aa4b873f0ad9cd4c348a1ea4f37f66aa7", "tree": "7a4f3c3dfd33e9d43044e5b7e0d49c1d8ddfab54", "parents": [ "7cbd1ced18e6abf63e1017b2d02ad80391b47cd7" ], "author": { "name": "Duncan Laurie", "email": "dlaurie@chromium.org", "time": "Fri Jan 29 17:45:51 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Jan 30 00:01:57 2016" }, "message": "vboot_display: Keep track of displayed screen\n\nVboot needs to track the currently displayed screen so when it needs to\nchange the locale or display the debug overlay it knows which screen to\nredraw. Currently only the legacy path is doing this so change the new\npath to update the current screen if it is successfully drawn.\n\nBUG\u003dchrome-os-partner:49766\nBRANCH\u003dglados\nTEST\u003dboot on glados in dev mode, hit tab and ensure screen does not go black\n\nChange-Id: I4a2bf028275db57b2d0469fc1cb574e871820713\nSigned-off-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/324549\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "7cbd1ced18e6abf63e1017b2d02ad80391b47cd7", "tree": "0709b17c9a84679bf50e216f96651de2f394a4d6", "parents": [ "6502935d9f610f8d62acf2de2534e5e64ee50643" ], "author": { "name": "Aaron Durbin", "email": "adurbin@chromium.org", "time": "Fri Jan 22 21:06:05 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Jan 26 22:56:36 2016" }, "message": "vb20: add vb2api_check_hash_get_digest() for retrieving hash result\n\nFor x86 systems, which resume through the boot reset vector, to\nimplement vboot verification of the memory init code one needs\ncheck that the slot chosen on the resume path is the same as\nthe original boot path. That check is done by storing the\nresulting hash of the slot. However, vb2api doesn\u0027t export\nthe resulting hash from vb2api_check_hash(). Thus, provide\na variant which saves the resulting digest in the supplied\nbuffer.\n\nBUG\u003dchrome-os-partner:46049\nBRANCH\u003dglados\nTEST\u003dSuspended and resumed on chell. Also, tested with an EC build\n which returns a bad hash to ensure that is properly caught.\n\nChange-Id: Ic20be2024afedabc2d8bc767f1b794376348523c\nSigned-off-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/323460\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\n" }, { "commit": "6502935d9f610f8d62acf2de2534e5e64ee50643", "tree": "f9715e3fccc77a6831312938fd1ea977846c4103", "parents": [ "3061777b091c183a39fd5cb4666e026371445b62" ], "author": { "name": "Alexandru M Stan", "email": "amstan@chromium.org", "time": "Tue Jan 12 19:45:29 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Jan 26 22:56:30 2016" }, "message": "Pipe the custom_music use flag to the define\n\nThis will allow the definition of CUSTOM_MUSIC from\nthe individual board ebuilds.\n\nTEST\u003dDefine use flag and extra functions on a board, enjoy the custom tunes\nBUG\u003dchrome-os-partner:48657\nBRANCH\u003dmaster\n\nChange-Id: I974f9cc51f9b25fb3dff063926e6ea01cf1e031b\nSigned-off-by: Alexandru M Stan \u003camstan@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/323833\nCommit-Ready: Alexandru Stan \u003camstan@chromium.org\u003e\nTested-by: Alexandru Stan \u003camstan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-by: Julius Werner \u003cjwerner@chromium.org\u003e\n" }, { "commit": "3061777b091c183a39fd5cb4666e026371445b62", "tree": "93baddeada72e08782d70e8ddbbba97232ffac3b", "parents": [ "eea0116590ccf332b75b589b1f3f64ffb55d3fb5" ], "author": { "name": "Alexandru M Stan", "email": "amstan@chromium.org", "time": "Fri Dec 18 23:28:32 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Jan 26 22:56:29 2016" }, "message": "Increase MAX_CUSTOM_DELAY to 5 minutes\n\nRialto will soon need a longer dev mode delay, this variable would prevent it.\n\nBUG\u003dchrome-os-partner:48657\nTEST\u003dSee follow up CLs\nBRANCH\u003dmaster\n\nChange-Id: Ie5ada9c5441b5b042bd0801d66559ab715fbbf47\nSigned-off-by: Alexandru M Stan \u003camstan@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/323832\nCommit-Ready: Alexandru Stan \u003camstan@chromium.org\u003e\nTested-by: Alexandru Stan \u003camstan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-by: Julius Werner \u003cjwerner@chromium.org\u003e\n" }, { "commit": "eea0116590ccf332b75b589b1f3f64ffb55d3fb5", "tree": "0ac3dcdb192d8046c74b7bf4c2a943db18bdd123", "parents": [ "bcf8389d9bb046341a0342c35fdda7321d22ea10" ], "author": { "name": "Duncan Laurie", "email": "dlaurie@chromium.org", "time": "Wed Jan 20 20:53:15 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Jan 21 02:25:38 2016" }, "message": "vboot: Disable VBNV_OPROM_NEEDED after successful update\n\nThe VBOOT_OPROM_NEEDED flag is used for EC software sync when the\nVBSD_EC_SLOW_UPDATE flag is set.\n\nAfter a successful EC software sync vboot requests a reboot to disable\ngraphics but it is not clearing the VBNV flag first. With vboot1 this\nwas getting cleared as a side effect of calling VbInit in normal mode.\n\nBUG\u003dchrome-os-partner:49560\nBRANCH\u003dglados\nTEST\u003dEnable EC_SLOW_UPDATE on chell and test EC software sync in normal\nmode and ensure that it reboots and does not do graphics init if the\nupdate is successful.\n\nChange-Id: I2aa0c4c3b1ad357a5b8ddc14539e264a1f5b76b2\nSigned-off-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/322731\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "bcf8389d9bb046341a0342c35fdda7321d22ea10", "tree": "ba668586092f3e66ae2e36db59bfce9cd7482291", "parents": [ "fd2b02abbf1c61f3887a0e4409dc7599a943c1f4" ], "author": { "name": "Mary Ruthven", "email": "mruthven@chromium.org", "time": "Wed Jan 06 19:30:55 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sun Jan 10 21:40:50 2016" }, "message": "Modify EC software sync to update RO if necessary\n\nAllow the AP to sync and verify the EC read only image after updating\nthe rewritable image.\n\nBUG\u003dchrome-os-partner:48703\nBRANCH\u003dnone\nTEST\u003dmanual\n\n1. Update EC to a new version\n2. rebuild EC code\n3. Update AP firmware\n4. Reboot and check that the RO image is updated after the RW image is\nupdated.\n\nCQ-DEPEND\u003dCL:319213\n\nChange-Id: I774ef25320103f20d8c7d1c180a220dd0819c04d\nSigned-off-by: Mary Ruthven \u003cmruthven@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/320614\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "fd2b02abbf1c61f3887a0e4409dc7599a943c1f4", "tree": "1664fcdea0967c7560afca90e38634cd30ab3d8b", "parents": [ "58cb8c532b0909edb34d17c7fd32b0559b917eb9" ], "author": { "name": "Bryan Freed", "email": "bfreed@chromium.org", "time": "Thu Jan 07 17:11:58 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Jan 07 22:29:42 2016" }, "message": "Update a utility to support the new tpm sysfs class directory\n\nKernel TPM patches from 4.x moved /sys/class/misc/tpm0 to /sys/class/tpm/tpm0.\nSupport both paths in this utility.\n\nBUG\u003dchromium:573368\nBRANCH\u003dnone\nTEST\u003duntested, not sure if this utility is still used.\n\nChange-Id: Ib81476eee4c9de921502a3a47f6990b9e6b1968b\nReviewed-on: https://chromium-review.googlesource.com/320892\nCommit-Ready: Bryan Freed \u003cbfreed@chromium.org\u003e\nTested-by: Bryan Freed \u003cbfreed@chromium.org\u003e\nReviewed-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\n" }, { "commit": "58cb8c532b0909edb34d17c7fd32b0559b917eb9", "tree": "6aa5c6bf58273c1109a9553932fdc08d8e716282", "parents": [ "7e0728dfca6d4f27c07434c9a6af468c966046a4" ], "author": { "name": "Doug Evans", "email": "dje@google.com", "time": "Thu Nov 19 23:57:23 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Jan 07 09:46:35 2016" }, "message": "Port to musl: musl doesn\u0027t have execinfo.h.\n\nChange-Id: Idc2f18880581d3a2e67185becee8b77cfa5cdf04\nReviewed-on: https://chromium-review.googlesource.com/313388\nCommit-Ready: Doug Evans \u003cdje@google.com\u003e\nTested-by: Doug Evans \u003cdje@google.com\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "7e0728dfca6d4f27c07434c9a6af468c966046a4", "tree": "668b9a11eae59472c210836284680188e641349f", "parents": [ "785343089c8fa38eacf9a71a33618125bb4174b9" ], "author": { "name": "Mary Ruthven", "email": "mruthven@chromium.org", "time": "Fri Dec 18 19:16:02 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Jan 07 04:43:25 2016" }, "message": "vboot: Change VbExEc implementations to support RO update\n\nThis change will be used to support EC-RO software sync by allowing for\naccess to the readonly region of firmware. Currently only the writable\nsection is accessed by vboot using VB_SELECT_FIRMWARE_A and B.\n\nBUG\u003dchrome-os-partner:48703\nBRANCH\u003dnone\nTEST\u003dbuilt on jerry and check that the RO hash can be read and the image\ncan be updated.\nCQ-DEPEND\u003dCL:319185,CL:320425,CL:320598\n\nChange-Id: Ic3942d86b65da3123798cfd11a78056f5dab6699\nSigned-off-by: Mary Ruthven \u003cmruthven@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/319213\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "785343089c8fa38eacf9a71a33618125bb4174b9", "tree": "1fb1b5977ebe31cce04a676ab30f040d0b77dc22", "parents": [ "aad73ca83ec10ce04d84e35fc280d3220af40928" ], "author": { "name": "Doug Evans", "email": "dje@google.com", "time": "Thu Nov 19 23:05:45 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Jan 07 00:58:18 2016" }, "message": "Include \u003cfcntl.h\u003e instead of \u003csys/fcntl.h\u003e.\n\nMusl complains about using sys/fcntl.h, and with -Werror that\ngives a compilation failure. Every other file includes \u003cfcntl.h\u003e\nso just use that.\n\nChange-Id: Ibc743bbe335e9e9b91da7e4eacc01cc80cd8b35a\nReviewed-on: https://chromium-review.googlesource.com/313419\nCommit-Ready: Doug Evans \u003cdje@google.com\u003e\nTested-by: Doug Evans \u003cdje@google.com\u003e\nReviewed-by: Nam Nguyen \u003cnamnguyen@chromium.org\u003e\n" }, { "commit": "aad73ca83ec10ce04d84e35fc280d3220af40928", "tree": "6b8f2989d0acb4e429d45d070696cb6dedc39b82", "parents": [ "46d78db74a0c14a99adc86b3a8b4536ce0c87365" ], "author": { "name": "Doug Evans", "email": "dje@google.com", "time": "Thu Nov 19 22:58:25 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Jan 06 18:53:51 2016" }, "message": "Use ${WERROR} consistently.\n\nChange-Id: I37b414b030cc69fab2b4feec70b55297dcd5fdb7\nReviewed-on: https://chromium-review.googlesource.com/313198\nCommit-Ready: Doug Evans \u003cdje@google.com\u003e\nTested-by: Doug Evans \u003cdje@google.com\u003e\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "46d78db74a0c14a99adc86b3a8b4536ce0c87365", "tree": "1d6b7944fa4b1cb8a34283d4374f6a0dd47423ee", "parents": [ "0e5f54d79158f216edeb42bfe9c5cd6d35dc6e0d" ], "author": { "name": "Mary Ruthven", "email": "mruthven@chromium.org", "time": "Tue Jan 05 22:59:05 2016" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Jan 06 13:22:40 2016" }, "message": "vboot2: Add try RO software sync flag\n\nThis flag will be used by the firmware updater to indicate that RO\nsoftware sync should be attempted.\n\nBUG\u003dchrome-os-partner:48703\nBRANCH\u003dNone\nTEST\u003dmake runtests\n\nChange-Id: I42090ac47da45c724e66334648ab447ad3c21178\nSigned-off-by: Mary Ruthven \u003cmruthven@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/320621\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "0e5f54d79158f216edeb42bfe9c5cd6d35dc6e0d", "tree": "f2debdb6b476a1ea954b0ec7b591c589383dc646", "parents": [ "885b6ae60561c5b864afd94230dd0bdad53ce4d5" ], "author": { "name": "Doug Evans", "email": "dje@google.com", "time": "Thu Nov 19 22:14:18 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Dec 17 05:49:34 2015" }, "message": "Move default target up so it\u0027s really the default.\n\nThe line\n${FUTIL_BIN}: ${UTILLIB21}\nwas changing the default.\n\nChange-Id: I7988af498c9a9a1981cf2485e4f9d3496412f133\nReviewed-on: https://chromium-review.googlesource.com/313245\nCommit-Ready: Bill Richardson \u003cwfrichar@chromium.org\u003e\nTested-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "885b6ae60561c5b864afd94230dd0bdad53ce4d5", "tree": "e24e910b45e8af6ce779f4399a8bdad8967a12b0", "parents": [ "b37e6672ebb4be7f2a3ec7d55a3e322f7afe1900" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Tue Dec 15 19:39:21 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Dec 16 11:35:42 2015" }, "message": "Test sha-256 with multiple odd-length updates\n\nThis verifies that the VB2 sha-256 library can handle odd-length\nupdates.\n\nThe expected digest was generated from:\n echo -n \u0027test1test2test3\u0027 | sha256sum\n\nBUG\u003dNone\nBRANCH\u003dNone\nTEST\u003dmake runtests\n\nChange-Id: Ia7d57322a1a4b10e718c47f1dae38ed244cf8ebc\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/318363\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "b37e6672ebb4be7f2a3ec7d55a3e322f7afe1900", "tree": "8448bc569dd2805e5a34480781cc895d5cfbef24", "parents": [ "758360b12a2eada0a01a839c3f8ba658dd7be22d" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Thu Dec 10 23:03:22 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Dec 16 11:35:12 2015" }, "message": "Add BDB library\n\nThis is a standalone library for verifying the BDB structures in the\ncommon boot flow document, and a bdb_create utility to create test BDB\nstructures. Eventually, creating these structures will be rolled into\nfutility.\n\nBUG\u003dchrome-os-partner:48448\nBRANCH\u003dnone\nTEST\u003dcd bdb \u0026\u0026 make runtests\n\nChange-Id: Ic57c26ca84137205da3b6c7d532f5324c93b4285\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/317275\nReviewed-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\n" }, { "commit": "758360b12a2eada0a01a839c3f8ba658dd7be22d", "tree": "d3d7bf22abcb2e4bb905ead6865f70539226f8a1", "parents": [ "c20d1cfc3c52a4f228494f246561d2fb895f1f8d" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Wed Dec 02 20:05:41 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Dec 03 10:21:22 2015" }, "message": "add error code for screen drawing failure\n\nThis patch adds error code for screen drawing failure.\n\nBUG\u003dnone\nBRANCH\u003dtot\nTEST\u003dTested on Glados\n\nChange-Id: I04b349fd2c0bc539338b7ee27b8fa9544c85c873\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/315257\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "c20d1cfc3c52a4f228494f246561d2fb895f1f8d", "tree": "365c25a22fdc5637f0b468c1a1800624280fe42a", "parents": [ "368594b3fc1197e2920e2a300ef0bbae1182d30d" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Wed Nov 18 01:44:46 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Dec 03 10:21:22 2015" }, "message": "Fix error message for VbGbbReadBmpHeader\n\nBUG\u003dnone\nBRANCH\u003dtot\nTEST\u003dTested on Jerry\n\nChange-Id: I1ecfd28b4c694e4aa531ed0e77219b2160509bd0\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/313744\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "368594b3fc1197e2920e2a300ef0bbae1182d30d", "tree": "95ac56252d2dd31115c961d6b837d67ddc0e8b15", "parents": [ "ffc446b2418d3a01be57c10a7c24db5e92efc708" ], "author": { "name": "Vincent Palatin", "email": "vpalatin@chromium.org", "time": "Tue Nov 17 19:18:19 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Nov 18 02:34:48 2015" }, "message": "sign_official_build: add a fallback key for standalone accessories\n\nThe standalone accessories are using a key name like this:\nkey_\u003cproduct\u003e.pem or key_\u003cproduct\u003e.vbprik2\nwhen it doesn\u0027t exist, fallback using key.pem or key.vbprik2.\n\nBRANCH\u003dnone\nBUG\u003dchrome-os-partner:47557\nTEST\u003dmanual:\n./scripts/image_signing/sign_official_build.sh accessory_usbpd ../ec/build/zinger/ec.bin tests/devkeys-acc /tmp/ec-zinger.TEST.SIGNED.bin\n./scripts/image_signing/sign_official_build.sh accessory_rwsig ../ec/private/build/hadoken/keyboard_app.bin tests/devkeys-acc /tmp/ec-hadoken.TEST.SIGNED.bin\n./scripts/image_signing/sign_official_build.sh accessory_rwsig ../ec/private/build/hadoken/keyboard_app.bin /tmp /tmp/ec-hadoken.TEST.SIGNED.bin\n\nChange-Id: I68863664bdb9da1695e91b1986f3a0148af7da26\nReviewed-on: https://chromium-review.googlesource.com/312836\nCommit-Ready: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "ffc446b2418d3a01be57c10a7c24db5e92efc708", "tree": "f49d6381a9fd0b0fdc65705b9d0e911fb2fae834", "parents": [ "bbdd62f9b030db7ad8eef789aaf58a7ff9a25656" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Mon Nov 16 19:47:28 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Nov 17 22:40:23 2015" }, "message": "Give more screen control to vboot_draw_screen\n\nNew devices have Depthcharge render vboot screens by calling\nvboot_draw_screen. Thus, display initialization and backlight control should\nnot be duplicated. This patch prevents VbDisplayScreen from initializing\ndisplay and controlling backlight when vboot is rendering screens using GBB.\n\nBUG\u003dchrome-os-partner:43706,chromium:502066\nBRANCH\u003dtot\nTEST\u003dTested on Glados\n\nChange-Id: I50cd2decb7065af96779601b12f0fbf2554ff6ed\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/312749\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "bbdd62f9b030db7ad8eef789aaf58a7ff9a25656", "tree": "08580fd9ad1fdd1c8045d3e072ad049c73000587", "parents": [ "c62f42b5c3ece037001bf6791d3de538421b705b" ], "author": { "name": "Julius Werner", "email": "jwerner@chromium.org", "time": "Fri Nov 06 22:28:44 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Mon Nov 09 20:49:18 2015" }, "message": "crossystem: Remove savedmem_base and savedmem_size fields\n\nI don\u0027t even know what this is. It seems to have marked some kind of\ndebug buffer provided by H2C BIOS on pre-Daisy Chromebooks and has not\nbeen touched since it was copied in here when crossystem was first\nadded. I can\u0027t find any references in our codebase so I doubt anybody\nwould miss it. Let\u0027s remove it so the \u0027(error)\u0027 fields returned there on\nany modern Chromebook stop confusing our vendors.\n\nBRANCH\u003dNone\nBUG\u003dchromium:551715\nTEST\u003dBuilt for Falco and Jerry.\n\nChange-Id: Ie2baec536b50bb192eb4cd3e48df212cce53561a\nSigned-off-by: Julius Werner \u003cjwerner@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/311346\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-by: Bernie Thompson \u003cbhthompson@chromium.org\u003e\n" }, { "commit": "c62f42b5c3ece037001bf6791d3de538421b705b", "tree": "81425017d57485ca7d65f50c47201e137b53bff5", "parents": [ "e85f6948f0ae8a147ec4d51421ca1bc63f557261" ], "author": { "name": "Julius Werner", "email": "jwerner@chromium.org", "time": "Fri Nov 06 22:22:32 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Mon Nov 09 20:49:18 2015" }, "message": "crossystem: Remove platform_family field\n\nThis field doesn\u0027t seem to be used for anyone and it keeps adding work\nfor people trying to bring up new platforms. If we ever needed something\nlike this again, we\u0027d probably prefer to have it in mosys now anyway.\nLet\u0027s get rid of it.\n\nBRANCH\u003dNone\nBUG\u003dchromium:551715\nTEST\u003dBuilt for Falco and Jerry.\n\nChange-Id: I6b96e255968fdd22a345d4a75bfdc1e79d3f5896\nSigned-off-by: Julius Werner \u003cjwerner@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/311345\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-by: Bernie Thompson \u003cbhthompson@chromium.org\u003e\n" }, { "commit": "e85f6948f0ae8a147ec4d51421ca1bc63f557261", "tree": "bfc5b4f2fddeec9c1863493dfd5d442610d04d44", "parents": [ "74a94db035275f2acaf375d4993647e1981bab7d" ], "author": { "name": "Vincent Palatin", "email": "vpalatin@chromium.org", "time": "Fri Oct 30 23:34:37 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Nov 03 19:01:24 2015" }, "message": "Update accessories test keys location\n\nMove around the test keys used for standalone accessories signing\nunittesting, so they are easier to use.\n\nBRANCH\u003dsmaug, samus\nBUG\u003dchrome-os-partner:46635\nTEST\u003drun cros-signing unittests (./signing_unittests.py)\n\nChange-Id: I02fcf444ec76bf6ebf6eb477e1236869aa877210\nReviewed-on: https://chromium-review.googlesource.com/309967\nCommit-Ready: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "74a94db035275f2acaf375d4993647e1981bab7d", "tree": "7911b06b545c2c13806f9fa6316bbef5282d38d5", "parents": [ "b491bc8bb1499452536eb140c22f749d1c9f9fc3" ], "author": { "name": "Mary Ruthven", "email": "mruthven@chromium.org", "time": "Wed Oct 28 17:48:59 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Nov 03 17:08:14 2015" }, "message": "vboot: Add GBB flag to turn on serial output\n\nCurrently this does nothing. This will eventually be used to enable\nserial output.\n\nBUG\u003dchromium:210230\nBRANCH\u003dnone\nTEST\u003dnone\n\nChange-Id: I5c25fd7406e30b96d12bc4bf8210d3c3f4ae79f1\nSigned-off-by: Mary Ruthven \u003cmruthven@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/309716\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "b491bc8bb1499452536eb140c22f749d1c9f9fc3", "tree": "08ea69814d669670fa225c75de11c44f0c19efe8", "parents": [ "faa8c7f6223701613965a89123227676d142ca9e" ], "author": { "name": "Shawn Nematbakhsh", "email": "shawnn@chromium.org", "time": "Wed Oct 21 21:31:02 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Oct 29 18:55:45 2015" }, "message": "vboot_api_kernel: Add new EcVbootDone API\n\nAdd a new post-EC software sync API VbExEcVbootDone() to take actions\nwhich normally need to happen after EC verification / sysjump.\n\nBUG\u003dchromium:537269\nTEST\u003dManual on Glados. Set CHG_MW thresh to 20000, BAT_PCT to 50. Verify\nthat LIMIT_POWER host event is set until Zinger negotiates to 20V. Also\nverify that we do not proceed with boot when Donette is plugged.\nBRANCH\u003dNone\nCQ-DEPEND\u003dCL:307885,CL:309523\n\nChange-Id: I77e6000aa8a44e3aca4fb5982e5b5f5191774989\nSigned-off-by: Shawn Nematbakhsh \u003cshawnn@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/307952\nCommit-Ready: Shawn N \u003cshawnn@chromium.org\u003e\nTested-by: Shawn N \u003cshawnn@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "faa8c7f6223701613965a89123227676d142ca9e", "tree": "75dcab24c29c02db3b55718d0d116057866bd0e6", "parents": [ "55484550bcedc2b70d84504ec59932f441988838" ], "author": { "name": "Vincent Palatin", "email": "vpalatin@chromium.org", "time": "Wed Oct 28 16:21:43 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Oct 29 07:03:33 2015" }, "message": "sign_official_build: fix support for signing standalone accessories\n\nMy previous patch using futility to re-sign standalone accessory\nfirmware images had a mistake in the key directory path : fix it.\n\nAlso add RSA-2048 \u0027accessory\u0027 keys for signer unit testing.\n\nBRANCH\u003dsmaug, samus\nBUG\u003dchrome-os-partner:46635\nTEST\u003drun cros-signing unittests (./signing_unittests.py)\n\nChange-Id: Ia2f641c85337c67f81968be4730643a6ad5f22cf\nReviewed-on: https://chromium-review.googlesource.com/309530\nCommit-Ready: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "55484550bcedc2b70d84504ec59932f441988838", "tree": "11e104b115fa7920461044bf7e29c497f4a87b6b", "parents": [ "d6723ed12b429834c2627c009aab58f0db20ce73" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Wed Oct 28 20:01:27 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Oct 29 03:44:39 2015" }, "message": "VbVerifyMemoryBootImage: Allow integrity-only check in dev mode with\nFASTBOOT_FULL_CAP set\n\nThis change allows developers to boot dev-signed boot images in\nunlocked mode if DEV_BOOT_FASTBOOT_FULL_CAP is set in VbNvStorage or\nGBB_FLAG_FORCE_DEV_BOOT_FASTBOOT_FULL_CAP is set.\n\nBUG\u003dchrome-os-partner:47002\nBRANCH\u003dNone\nTEST\u003dCompiles successfully. make -j runtests\n\nChange-Id: I56e3879594da1b57051dfe242ff347ac970c96bb\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/309606\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "d6723ed12b429834c2627c009aab58f0db20ce73", "tree": "d92216bb25dc02d33b90218ec96fc3c350a6589a", "parents": [ "3a631486bddaeab1e8cc2abe0fb725721f2a0be0" ], "author": { "name": "Vincent Palatin", "email": "vpalatin@chromium.org", "time": "Tue Oct 20 00:22:07 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 27 17:13:38 2015" }, "message": "sign_official_build: add support for signing standalone accessories\n\nUse futility to re-sign standalone accessory firmware images either the\nformer \"usbpd1\" used by USB Power Delivery firmware generated from the\nEC codebase or the new \"rwsig\" format.\n\nBRANCH\u003dsmaug, samus\nBUG\u003dchrome-os-partner:46635\nTEST\u003dmanual:\nopenssl genrsa -F4 -out key_zinger.pem 2048\nopenssl genrsa -F4 -out key_hadoken.pem 2048\nfutility create --desc\u003d\"Hadoken fake MP key\" key_hadoken.pem key_hadoken\n./scripts/image_signing/sign_official_build.sh accessory_usbpd build/zinger/ec.bin . build/zinger/ec.SIGNED.bin\n./scripts/image_signing/sign_official_build.sh accessory_rwsig build/hadoken/keyboard_app.bin . build/hadoken/keyboard_app.SIGNED.bin\nand compare the re-signed files with the original files.\n\nChange-Id: I586ba3e4349929782e734af1590f394824e7dd44\nReviewed-on: https://chromium-review.googlesource.com/306795\nCommit-Ready: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "3a631486bddaeab1e8cc2abe0fb725721f2a0be0", "tree": "bb6ae76d4965913377ec526fa1e7a9f813f22462", "parents": [ "be5eca9126a048d7187d5c96de46d27df3b1359c" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Wed Oct 21 01:31:10 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Mon Oct 26 18:24:18 2015" }, "message": "Save recovery reason before user three-finger-salutes\n\nWhen a user hits esc+refresh+power to start recovery, the true recovery\nreason will be lost after reboot. (It would always look like\nVB2_RECOVERY_RO_MANUAL.) This patch makes VbBootRecovery save\nthe reason in the subcode area before entering the new \u0027broken\u0027 loop.\n\nBUG\u003dchromium:501060\nBRANCH\u003dtot\nTEST\u003dtest_that -b veyron_jerry suite:faft_bios\n\nChange-Id: Ib536daa0633721bfc975381782d348f122b3d337\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/307586\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "be5eca9126a048d7187d5c96de46d27df3b1359c", "tree": "12df4a6a2b17f99babc667f8e5d625e91dd2b7c8", "parents": [ "27c90708e63f5f042aa52de6bc1b89c282ca8c4a" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Wed Oct 07 00:03:08 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 20 18:18:53 2015" }, "message": "Add VbExGetLocalizationCount\n\nVbExGetLocalizationCount is a callback function which is supposed to\nreturn the number of screen locales supported by VbExDisplayScreen.\n\nAfter this change, we still try to get the number of locales from GBB\nfirst but when it fails, VbExGetLocalizationCount is called. The error\ncode from VbGbbReadBmpHeader will be masked, similarly to the error from\nVbDislayScreenFromGBB.\n\nBUG\u003dchromium:502066\nBRANCH\u003dtot\nTEST\u003dTested on Samus. make runtests\n\nChange-Id: I04ef8bf1ea02b1aaa05e65673b57bcea1932d8b0\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/304376\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "27c90708e63f5f042aa52de6bc1b89c282ca8c4a", "tree": "356818f84486955e3591c4ab974ce70639c5097a", "parents": [ "4d47243c9088ef295892fbc25b9c3622e43ad639" ], "author": { "name": "Vincent Palatin", "email": "vpalatin@chromium.org", "time": "Fri Oct 16 00:54:34 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Oct 17 16:53:07 2015" }, "message": "futility: add support for .pem with public key\n\nAdd support for PEM file containing a RSA Public key in futility \"show\"\nand \"create\" commands.\n\nWhen \"futility create\" is given a PEM file with only a RSA public key,\ngenerate the proper .vbpubk2 rather than failing.\n\nBRANCH\u003dsmaug\nBUG\u003dnone\nTEST\u003dmake runtests\nand run manually\nfutility show tests/testkeys/key_rsa4096.pub.pem\nfutility show tests/testkeys/key_rsa4096.pem\n\nChange-Id: I707ceca54c80ba21f53869ad86c86fa23b31e665\nReviewed-on: https://chromium-review.googlesource.com/306683\nCommit-Ready: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "4d47243c9088ef295892fbc25b9c3622e43ad639", "tree": "07df0c98c2819fbdf0d77fc349eb6802e69fc0b6", "parents": [ "02ac2885fd797fba7f12ef040f0eb041dda7af20" ], "author": { "name": "Vincent Palatin", "email": "vpalatin@chromium.org", "time": "Fri Oct 16 00:46:58 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Oct 17 15:18:48 2015" }, "message": "futility: fix segfault on short files\n\nVerify the size of the buffer read from the file before trying to use 1KB of\nit for the new rwsig format detection.\n\nAdd a new test case with a short file containing only 4 bytes of unknown\ndata and run \"futility show\" on it.\n\nBRANCH\u003dsmaug\nBUG\u003dnone\nTEST\u003dfutility show foobar.pub.pem\nwhere foobar.pub.pem is a 451-byte file.\ncheck that \"make runtests\" passes with the fix\nand fails without it with the following message :\ntest_file_types.sh ... failed\nFAIL: 13 / 14 passed\n\nChange-Id: Ia9d68c6b528c2b3a595ea6791c907374616d051f\nReviewed-on: https://chromium-review.googlesource.com/306682\nCommit-Ready: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "02ac2885fd797fba7f12ef040f0eb041dda7af20", "tree": "8c8386e3fc07bb5f7cc8c5c485cf10a58dec1340", "parents": [ "df0e1a391fa7b8d7bdb31f9623fbbcbb158cd2ad" ], "author": { "name": "Bill Richardson", "email": "wfrichar@chromium.org", "time": "Thu Oct 15 07:23:18 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 16 02:57:13 2015" }, "message": "futility: Revised support for RO+RW firmware\n\nThe \"rwsig\" type is used for independent device firmware (not\nChromebook BIOS) that need to verify themselves instead of using\nsoftware sync.\n\nThe expected use case is that a RO firmware contains a\nvb2_public_key struct along with an FMAP or other pointers to a\nslot for RW firmware. The RW firmware slot reserves room for a\nvb2_signature struct.\n\nThis CL changes the args and behavior of the rwsig type, so that\nthe RW firmware can be [re]signed independently of the rest of\nthe image.\n\nBUG\u003dchrome-os-partner:46254\nBRANCH\u003dsmaug,ToT\nTEST\u003dmake runtests, manual\n\nCreate a keypair:\n\n futility create --desc \"Key One\" tests/testkeys/key_rsa2048.pem foo\n\nSign a RW binary and build a complete image out of the parts:\n\n futility sign --type rwsig --prikey foo.vbprik2 rw.bin sig.bin\n\n dd if\u003d/dev/zero bs\u003d65536 count\u003d1 of\u003dimage.bin\n dd if\u003drw.bin of\u003dimage.bin conv\u003dnotrunc\n dd if\u003dsig.bin bs\u003d$((65536 - 1024)) seek\u003d1 of\u003dimage.bin conv\u003dnotrunc\n\nVerify both the separate parts and the combined image:\n\n futility show --type rwsig --pubkey foo.vbpubk2 rw.bin sig.bin\n futility show --type rwsig --pubkey foo.vbpubk2 image.bin\n\nRe-sign the combined image with a different keypair:\n\n futility create --desc \"Key Two\" tests/testkeys/key_rsa1024.pem bar\n\n futility sign --type rwsig --prikey bar.vbprik2 image.bin\n\nNow the first key no longer verifies:\n\n futility show --type rwsig --pubkey foo.vbpubk2 image.bin\n\nBut the second key does:\n\n futility show --type rwsig --pubkey bar.vbpubk2 image.bin\n\nChange-Id: Ifdddab08f218f506eb1dce28851b153d70140a7b\nSigned-off-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/305980\nTested-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\n" }, { "commit": "df0e1a391fa7b8d7bdb31f9623fbbcbb158cd2ad", "tree": "2ebc8138f7a5df143d9196d955976a1e28797bd3", "parents": [ "9354379d64025bbb96a7ae28c3f1a81c1657bc4a" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Thu Oct 15 22:38:36 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 16 02:57:13 2015" }, "message": "Revert \"image_signing: use sparse partition extraction\"\n\nThis reverts commit 82dec09bd5098715ddf9cd7d2e4abe87606d5249.\n\nThis flag doesn\u0027t exist on Ubuntu Precise which is what the signers\nare running atm. Until we get them upgraded to Trusty, back this\nchange out.\n\nBUG\u003dchromium:530730\nTEST\u003d`./signing_unittests.py` passes\nBRANCH\u003dNone\n\nChange-Id: I9ba508c1531dbb169fd020d06ab102f6576b7342\nReviewed-on: https://chromium-review.googlesource.com/306310\nCommit-Ready: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: Amey Deshpande \u003cameyd@google.com\u003e\n" }, { "commit": "9354379d64025bbb96a7ae28c3f1a81c1657bc4a", "tree": "afeda98c6cdfe5b49e62a1bd66fe789ec368b4e5", "parents": [ "7ed261297f7b730e9f545ba59cbe2ed216850e19" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Tue Oct 06 23:50:33 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 16 01:08:23 2015" }, "message": "Pass locale to VbExDisplayScreen\n\nThis change makes VbDisplayScreen read the last saved locale from nvram\nand pass it to VbExDisplayScreen so that it can draw locale dependent\nscreens.\n\nBUG\u003dchromium:502066\nBRANCH\u003dtot\nTEST\u003dTested on Samus. make runtests.\nCQ-DEPEND\u003dCL:304382,CL:306100,CL:306110\n\nChange-Id: I9782ec5a8a9f8393998aa8a0d64e88ad1809233b\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/304375\n" }, { "commit": "7ed261297f7b730e9f545ba59cbe2ed216850e19", "tree": "32de7b1658af2d9ee19158284ffcd2b8f7cd72b7", "parents": [ "12a55f255aaea2f12362e4f832a0bd48eb29f5dd" ], "author": { "name": "Bill Richardson", "email": "wfrichar@chromium.org", "time": "Mon Oct 12 20:58:12 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Oct 14 03:22:04 2015" }, "message": "futility: Support for signing RO+RW firmware\n\nThis adds the \"rwsig\" type, with initial support for RO+RW\nfirmware images that need to verify themselves instead of using\nsoftware sync. This uses our vb2 structs instead of raw binary\nblobs. That will help us locate, identify, and verify the keys\nand signatures in the signed firmware images.\n\nBUG\u003dchrome-os-partner:46254\nBRANCH\u003dsmaug,ToT\nTEST\u003dmake runtests\n\nI also hacked up a test board with the EC-side signature\nverification routines from a preliminary CL and tested this\nsigning scheme with that. It works.\n\nAdditional work is needed to make this seamless, but you can try\nit out like so:\n\n futility create ./tests/testkeys/key_rsa2048.pem foo\n\n futility sign --type rwsig --prikey foo.vbprik2 --pubkey foo.vbpubk2 ec.bin\n\nChange-Id: I876ab312a2b0b36411c5f739fe3252529728d034\nSigned-off-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/305394\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "12a55f255aaea2f12362e4f832a0bd48eb29f5dd", "tree": "f235ebf2cd846c852371a96cf76e3282ff0c26be", "parents": [ "73a6372d22f74d0396253f6e5080442edec55d7f" ], "author": { "name": "Mary Ruthven", "email": "mruthven@google.com", "time": "Tue Oct 06 17:42:31 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Oct 13 21:02:26 2015" }, "message": "Add NV flag to default boot legacy OS\n\nIn developer mode, this option will make the system try to boot into\na legacy OS first after the 30 second timeout. This removes the need to\npress a key during boot to try legacy mode and the need to remove the\nwrite protect screw to boot legacy as default.\n\nBUG\u003dchromium:310697\nBRANCH\u003dnone\nTEST\u003dmake runtests\n\nChange-Id: I9a9f64c14ad015e21d08eec36e8fc187189cd2f2\nSigned-off-by: Mary Ruthven \u003cmruthven@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/304077\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "73a6372d22f74d0396253f6e5080442edec55d7f", "tree": "2db550c27ad465112187b14b92ea83f7bab74e6d", "parents": [ "f29dbbcbd5c47161389541b9889ae5e88a336586" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Thu Apr 30 19:41:24 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Mon Oct 12 20:15:49 2015" }, "message": "Add broken screen\n\nIn the new recovery process, a user will see \u0027broken\u0027 screen\ninstead of \u0027remove\u0027 screen, where usb stick presence is no longer\ndetected. A user instead has to hit esc+refresh+power to proceed\nto recovery mode.\n\nBUG\u003dchromium:501060\nBRANCH\u003dtot\nTEST\u003dmake runtests\n\nChange-Id: Icd511c1ca892628b96befbb0a34c2c84b881c857\nReviewed-on: https://chromium-review.googlesource.com/304404\nCommit-Ready: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nTested-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "f29dbbcbd5c47161389541b9889ae5e88a336586", "tree": "614fdb2ec039d5743e5418dfa734a6885b21a1f0", "parents": [ "dabb158ad27610661ef16639843e2909f2a3dba5" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Wed Aug 19 04:19:28 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Oct 09 01:42:31 2015" }, "message": "recovery: Add recovery reason for fastboot mode requested in\nuser-mode.\n\nBUG\u003dchrome-os-partner:42674\nBRANCH\u003dNone\nTEST\u003dCompiles successfully and behavior verified.\n\nChange-Id: I67ec056f28596dd0c0005a54e454abe1b4104cfb\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/294276\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n(cherry picked from commit 6d9a9a9fdd3bcdadbfc4f44640da4c462803a69d)\nReviewed-on: https://chromium-review.googlesource.com/304673\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "dabb158ad27610661ef16639843e2909f2a3dba5", "tree": "7f3fc2b412ab31cb7c5cfab8fb357042e0b521a4", "parents": [ "82db93d5fc924860e4f1fb4cf24f29b5b335a480" ], "author": { "name": "Amey Deshpande", "email": "ameyd@google.com", "time": "Thu Sep 17 01:16:42 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Oct 03 23:26:08 2015" }, "message": "signer: update legacy bootloader templates after image signing\n\nSpecifically, this patch updates \u0027root_hexdigest\u0027 in legacy bootloader\ntemplates in EFI system partition to match the signed rootfs.\n\nBRANCH\u003dNone\nBUG\u003dchromium:512940\nTEST\u003dRan sign_official_build.sh locally and booted the image on kvm\n(using BIOS).\nTEST\u003dRan signing_unittests.py by locally changing vboot_stable_hash to\ninclude this patch.\n\n$ ./sign_official_build.sh base chromiumos_base_image.bin \\\n ../../tests/devkeys chromiumos_base_image_signed.bin\n\nChange-Id: Ied021c4464b113a64508f5081605069bdcecbc1f\nReviewed-on: https://chromium-review.googlesource.com/301742\nCommit-Ready: Amey Deshpande \u003cameyd@google.com\u003e\nTested-by: Amey Deshpande \u003cameyd@google.com\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "82db93d5fc924860e4f1fb4cf24f29b5b335a480", "tree": "084dfc2c4854fa2fd4b378a496c935a35abb162e", "parents": [ "5b202a94f0ef30421c532b2aed963ac9f6f78521" ], "author": { "name": "Bill Richardson", "email": "wfrichar@chromium.org", "time": "Thu Sep 24 17:59:41 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 25 17:31:24 2015" }, "message": "futility: Add show capability for usbpd1 images\n\nThe firmware for the USB Type-C power adapters uses raw binary\nblobs for the public keys and signatures instead of\nreadily-identifiable structs. We\u0027ve been able to sign these\nfirmware images for some time, but verifying the result generally\nrequired testing them on hardware.\n\nThis CL adds some futilty support for recognizing and verifying\nthose images too. It just tries various sig and hash algorithms,\nuntil it finds a combination for which the image is\nself-consistent (where the pubkey blob verifies the signature\nblob).\n\nBUG\u003dnone\nBRANCH\u003dnone\nTEST\u003dmake runtests\n\nThis change also adds additional tests for usbpd1 images. We\nensure that we correctly recognize and verify an MP-signed\nfirmware, plus test signing and verifying usbpd1 images using\nmultiple signature and hash algorithms.\n\nChange-Id: I4fbe8b37a694992f635d5469ae1c2449b1610dfd\nSigned-off-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/302415\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "5b202a94f0ef30421c532b2aed963ac9f6f78521", "tree": "93e678132624b9e4ca2d704fd79e6ae501cc28ba", "parents": [ "300ff7ffdcb9b55c4b8a1b000661d3fae48be74b" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Tue Sep 22 16:09:27 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 23 22:58:52 2015" }, "message": "vboot: Move GPT entry operator functions to gpt_misc\n\nThis is to allow external entities using vboot library\n(e.g. depthcharge) to utilize these operator functions to perform get\n/ set operations on GPT entry.\n\nBUG\u003dchrome-os-partner:45670\nBRANCH\u003dNone\nTEST\u003dCompiles successfully \"sudo emerge vboot_reference\" \"emerge-smaug\nvboot_reference\". \"make -j runtests\" successful.\n\nChange-Id: I9e34a2a7afeae6293a78424794797d5755950888\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/301475\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "300ff7ffdcb9b55c4b8a1b000661d3fae48be74b", "tree": "2db8e93080ee006aa0e3800d55b1660b81312bc3", "parents": [ "45e3021c409cd4cf7c09077c5693c1054ebd4a40" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Thu Sep 17 22:50:48 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 22 18:46:26 2015" }, "message": "vboot2: tpm error doesn\u0027t block gbb dev flag\n\nIn recovery mode, the TPM may be bad / corrupt. This prevents access to\nthe soft developer switch stored in secdata. But it should not prevent\nsetting dev mode via GBB or context flags. Those flags may be set\nduring manufacturing or testing, and override the contents of secdata\nanyway.\n\nBUG\u003dchrome-os-partner:45511\nBRANCH\u003dryu\nTEST\u003dmake runtests\n\nChange-Id: I242714528203cc7cf78a714c660b7f8bbd0e04d0\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/300621\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "45e3021c409cd4cf7c09077c5693c1054ebd4a40", "tree": "b33977e769872aacfabc97579303b0a93452e076", "parents": [ "c8e48545d5cbf43ebbe9acd008aa6b9985d514d6" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Fri Sep 11 23:05:37 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 18 00:35:14 2015" }, "message": "sign_official_build: support signing \u0027recovery_kernel\u0027 image type\n\nBRANCH\u003dNone\nBUG\u003dchrome-os-partner:44227\nTEST\u003d\u0027sign_official_build.sh recovery_kernel boot.img keys\nboot.img.recovery-signed\u0027 works fine and able to boot in locked recovery mode\nusing fastboot boot.\n\nChange-Id: Iabde28bb2068b8294fc3d03f2f771c63368ecbb5\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/300250\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: David Riley \u003cdavidriley@chromium.org\u003e\n" }, { "commit": "c8e48545d5cbf43ebbe9acd008aa6b9985d514d6", "tree": "8f1db95bb733ed24c867b3431d25b6549382fead", "parents": [ "85f646613c7cb194a52608255e18cf827207c91a" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Thu Sep 17 19:54:51 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Fri Sep 18 00:35:11 2015" }, "message": "vboot2: Support reboot requested by secdata\n\nWhen a TPM goes from the disabled state to the enabled state, it must\nreboot after being enabled, before it can be initialized. In vboot1,\nTLCL was part of vboot and this was handled internally. In vboot2, the\ncaller must set a context flag, so that vboot can decide whether to\nallow the reboot, or whether to go directly to recovery mode. This\ncheck is necessary to handle the following cases:\n\n1) The device is booting normally, but the TPM needs a reboot. This\nshould simply reboot, without going to recovery mode.\n\n2) The device is booting in recovery mode, but the TPM needs a reboot.\nIf this is the first time it asked us, allow the reboot.\n\n3) The TPM asked for a reboot last time, so we did. And it\u0027s still\nasking. Don\u0027t reboot, because that runs the risk that whatever is wrong\nwon\u0027t be fixed next boot either, and we\u0027ll get stuck in a reboot loop\nthat will prevent recovery. Boot into recovery mode.\n\nAdd a new NvStorage bit to track whether the TPM requested a reboot on\nthe previous boot. That\u0027s better than what we did in vboot1, where we\nused a special recovery request. Vboot1 couldn\u0027t track getting stuck in\na reboot loop in normal mode, only in recovery mode. The new code can\ncatch both.\n\nBUG\u003dchrome-os-partner:45462\nBRANCH\u003dryu\nTEST\u003dmake runtests\n\nChange-Id: I2ee54af107275ccf64a6cb41132b7a0fc02bb983\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/300572\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Julius Werner \u003cjwerner@chromium.org\u003e\n" }, { "commit": "85f646613c7cb194a52608255e18cf827207c91a", "tree": "ecf2aed6b9f150f24b48402b8fc9cf4f1fa37680", "parents": [ "82dec09bd5098715ddf9cd7d2e4abe87606d5249" ], "author": { "name": "Shelley Chen", "email": "shchen@chromium.org", "time": "Mon Sep 14 22:39:29 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Tue Sep 15 06:47:03 2015" }, "message": "crossystem: Updated crossystem to accomodate Android\n(resubmit)\n\nPreviously crossystem assumed that mosys was located\nin /usr/sbin. In Android mosys is currently located\nin /system/bin. Using fixed paths as opposed to\n\u0027which\u0027 to prevent attacks where attacker could insert\nmosys in PATH.\n\ndifference from previous commit:\n Removed the allocation of duplicate arrays. Kept\n with simplicity of original version, just returning\n correct constant depending on detected platform.\n\nBUG\u003dchromium:527484\nBRANCH\u003dnone\nTEST\u003dran crossystem, crossystem fw_try_count/\nfw_try_next, crossystem fw_try_count/fw_try_next\u003dx\non smaug and daisy.\n\nChange-Id: I923206db1411a9a35c9c8e3f9ede5016f49b5f26\nSigned-off-by: Shelley Chen \u003cshchen@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/299801\nReviewed-by: danny chan \u003cdchan@chromium.org\u003e\n" }, { "commit": "82dec09bd5098715ddf9cd7d2e4abe87606d5249", "tree": "09bdaa079fc39fa8fa8bdbb64320b058ca73815d", "parents": [ "df9bf4eef39afffb296ed5332fdecdc7af01813f" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Thu Sep 10 20:18:03 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Sep 12 01:36:29 2015" }, "message": "image_signing: use sparse partition extraction\n\nOften the partitions we extract have extra space in them, but the dd\nutility will still write out the excess zeros. That can mean we write\nout hundreds of megs of data which could otherwise be skipped. We thus\nwaste a good amount of I/O and storage.\n\nFor now, only use this flag when extracting a partition to a new file\nas this should be safe (there\u0027s no pre-existing data to clobber/merge).\n\nBUG\u003dchromium:530730\nTEST\u003d`./signing_unittests.py` passes\nBRANCH\u003dNone\n\nChange-Id: Ic32665cf7c38fc0a5efc3f8b227fa8ff408ca9e3\nReviewed-on: https://chromium-review.googlesource.com/299450\nCommit-Ready: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: David Riley \u003cdavidriley@chromium.org\u003e\n" }, { "commit": "df9bf4eef39afffb296ed5332fdecdc7af01813f", "tree": "3963c08a5b0414f208c0bf06580432594c290348", "parents": [ "afb07f4967e891f2b4e28e3415e4a6858a096a35" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Wed Sep 09 21:00:57 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Sep 12 00:10:41 2015" }, "message": "image_signing: use sparse copying when creating the signed image\n\nThis should speed up the copies significantly by using less disk\nstorage \u0026 I/O when the unpacked file is not sparse already. This\noption has been in cp for a long time, and works in Ubuntu Precise\n(coreutils-8.13) \u0026 Trusty (coreutils-8.21).\n\nBUG\u003dchromium:530730\nTEST\u003d`./signing_unittests.py` passes\nBRANCH\u003dNone\n\nChange-Id: I82192455a623eabf96abf4f25296f3dc0c129ca2\nReviewed-on: https://chromium-review.googlesource.com/299440\nCommit-Ready: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: David Riley \u003cdavidriley@chromium.org\u003e\nReviewed-by: Amey Deshpande \u003cameyd@google.com\u003e\n" }, { "commit": "afb07f4967e891f2b4e28e3415e4a6858a096a35", "tree": "15ee0e5d6c80de92dc6abf0fdbe1e85e8fdb82a1", "parents": [ "28f43363b414e86a188ff27378710078fd9fc9cc" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Thu Sep 10 20:29:34 2015" }, "committer": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Thu Sep 10 20:37:32 2015" }, "message": "image_signing: do not delete output when signing loem firmware\n\nRather than use the existence of the output as a marker for running the\ngbb step, key off the loem index. We want to run it the first time and\nnot bother after that.\n\nBUG\u003dchrome-os-partner:44227\nBRANCH\u003dNone\nTEST\u003dsigner can still sign loem keysets\n\nChange-Id: I26e9ccaf1333f769d6993a8e0d84c63644bb2597\nReviewed-on: https://chromium-review.googlesource.com/298980\nReviewed-by: David Riley \u003cdavidriley@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "28f43363b414e86a188ff27378710078fd9fc9cc", "tree": "9eb6d97639c039263bdc0efe17b79fc9c9428427", "parents": [ "907bc34086d21482e48adddc5da20f48e1a3c0a1" ], "author": { "name": "David Riley", "email": "davidriley@chromium.org", "time": "Tue Sep 08 20:05:56 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 09 06:32:43 2015" }, "message": "signer: create devkeys with and without pkc\n\nSigning test of firmware for non-t210 targets fails when PKC\nkeys are present so separate devkeys into two keysets where only\none has the PKC key.\n\nBUG\u003dchrome-os-partner:44227\nTEST\u003dsign_official_build.sh nv_lp0_firmware tegra_lp0_resume.fw tests/devkeys-pkc tegra_lp0_resume.fw.signed versions.default\nBRANCH\u003dsigner\n\nChange-Id: Ie0670638d30d17692f1113b5a9f0309ea610d72a\nSigned-off-by: David Riley \u003cdavidriley@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/298091\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "907bc34086d21482e48adddc5da20f48e1a3c0a1", "tree": "39b86ebfdcd3674ecb3342fc4ac7ed8611cd8d8a", "parents": [ "69898e6c513fd5b9e74de12714d2edbd17a4a56a" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Wed Apr 08 17:43:01 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 09 01:43:42 2015" }, "message": "keygeneration: fix some portability aspects\n\nThe \"function\" keyword is not portable -- use the normal function style.\n\nThe awk command uses a non-portable regex (the word anchor \\\u003e). Rework\nit to avoid regexes entirely.\n\nBUG\u003dchromium:475101\nTEST\u003dkeyset_version_check.sh works on a POSIX system\nBRANCH\u003dNone\n\nChange-Id: I5446f63aa9181d06da1898aafb8fab17f5042989\nReviewed-on: https://chromium-review.googlesource.com/296562\nCommit-Ready: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: David Riley \u003cdavidriley@chromium.org\u003e\n" }, { "commit": "69898e6c513fd5b9e74de12714d2edbd17a4a56a", "tree": "f4a13f4eea5583bad6b2428303f1a72e37e6e95b", "parents": [ "7d0845475599bf98493afabc6861d5949bf08f16" ], "author": { "name": "David Riley", "email": "davidriley@chromium.org", "time": "Fri Sep 04 23:05:06 2015" }, "committer": { "name": "David Riley", "email": "davidriley@chromium.org", "time": "Tue Sep 08 18:21:23 2015" }, "message": "signer: Add signing support for nvidia lp0 firmware from signer\n\nSigner was calling sign_official_build.sh in a manner that wasn\u0027t\nbeing accepted correctly. Also add test keys from firmware branch.\n\nBUG\u003dchrome-os-partner:44227\nTEST\u003dsign_official_build.sh nv_lp0_firmware tegra_lp0_resume.fw tests/devkeys tegra_lp0_resume.fw.signed versions.default\nBRANCH\u003dsigner\n\nChange-Id: Icd298ac75e3da746220826dc2fb9cc2466e41f1d\nSigned-off-by: David Riley \u003cdavidriley@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/297802\nReviewed-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "7d0845475599bf98493afabc6861d5949bf08f16", "tree": "463f5068a9ad48203a0f117718f4c20caddba4fc", "parents": [ "90cd023d0132a13ba85b592ceafd60064ce1857d" ], "author": { "name": "Mike Frysinger", "email": "vapier@chromium.org", "time": "Fri Sep 04 23:37:12 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Sat Sep 05 06:02:14 2015" }, "message": "image_signing: rework input/output files and firmware signing\n\nThe new nvidia logic expects to have the \"real\" output filename and not\nyet another temp path. Since sign_firmware.sh supports being passed in\nthe input as the output and doing in-place signing, just document it and\nupdate the callers.\n\nBUG\u003dchrome-os-partner:44227\nBRANCH\u003dNone\nTEST\u003dsigner outputs pubkey.sha to the same location as the output firmware\n\nChange-Id: Iadc5dc5aaace6be9e22ff2c55bfbc58b7e1b3ef0\nReviewed-on: https://chromium-review.googlesource.com/296574\nCommit-Ready: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nReviewed-by: David Riley \u003cdavidriley@chromium.org\u003e\n" }, { "commit": "90cd023d0132a13ba85b592ceafd60064ce1857d", "tree": "504c540a03db21f46a807e0ea4bebe7504e03c3e", "parents": [ "1196aa05d438b440f6e690204f6fe5cd9bbf2290" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Tue Sep 01 07:11:35 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 02 02:19:04 2015" }, "message": "signer: Add signing support for nvidia lp0 firmware\n\nBUG\u003dchrome-os-partner:44227\nBRANCH\u003dNone\nTEST\u003dunittests run fine.\n\nChange-Id: I7d623a22d73a1749ebebd323fe09cbbeb8cbd61e\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/296429\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "1196aa05d438b440f6e690204f6fe5cd9bbf2290", "tree": "437bc16752671f3ec8f0eab6a05e3bfe2495f8be", "parents": [ "f8ba822b8a114af5cc88b208fd277d3079476677" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Mon Aug 31 18:30:42 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Wed Sep 02 02:19:04 2015" }, "message": "sign_firmware: Add nv_pkc_signing step if required\n\nIf nv_pkc.pem file is present for a device, use nv_pkc_signing for\nadding PKC signature in the firmware image.\n\nBUG\u003dchrome-os-partner:44227\nBRANCH\u003dNone\nTEST\u003dunittests run fine. verified image boots on fused system.\n\nChange-Id: I9b2f48da55137a0e4a75f23d16d3779be1aa94c8\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/296452\nCommit-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "f8ba822b8a114af5cc88b208fd277d3079476677", "tree": "7e72da40a38ed223b946821479f62641d178ec41", "parents": [ "9cd821ca51e637780d66f4b658193466e4535d9f" ], "author": { "name": "Lee Leahy", "email": "leroy.p.leahy@intel.com", "time": "Wed Aug 26 22:56:05 2015" }, "committer": { "name": "chrome-bot", "email": "chrome-bot@chromium.org", "time": "Thu Aug 27 17:20:24 2015" }, "message": "VBOOT2: Add work buffer too small error message\n\nUpdate VBOOT2 to add work buffer too small error message.\n\nBRANCH\u003dnone\nBUG\u003dNone\nTEST\u003dBuild and run on kunimitsu\n\nChange-Id: Icb4b873e0c350a5667948e106c111356acab6a82\nSigned-off-by: Lee Leahy \u003cLeroy.P.Leahy@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/295753\nCommit-Ready: Leroy P Leahy \u003cleroy.p.leahy@intel.com\u003e\nTested-by: Leroy P Leahy \u003cleroy.p.leahy@intel.com\u003e\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "9cd821ca51e637780d66f4b658193466e4535d9f", "tree": "b85a3559c9cd5039a83fee38ab36ca54ba0f4e1b", "parents": [ "076a5395e94607e0eb658b6882049776a841d469" ], "author": { "name": "Eric Caruso", "email": "ejcaruso@chromium.org", "time": "Sat Aug 22 00:22:29 2015" }, "committer": { "name": "Eric Caruso", "email": "ejcaruso@chromium.org", "time": "Sat Aug 22 00:24:02 2015" }, "message": "Revert \"crossystem: Updated crossystem to accomodate Android\"\n\nThis reverts commit 26825b53dc914e4599767ae1e78fe731840027c1.\n\nThis looks like it breaks ARM systems by causing crossystem to crash freeing stuff.\n\nBUG\u003dchromium:523189\n\nChange-Id: Ic1e1594519354e7b80424f5c66dc9bdb2605ec73\nReviewed-on: https://chromium-review.googlesource.com/295215\nReviewed-by: Eric Caruso \u003cejcaruso@chromium.org\u003e\nCommit-Queue: Eric Caruso \u003cejcaruso@chromium.org\u003e\nTested-by: Eric Caruso \u003cejcaruso@chromium.org\u003e\n" }, { "commit": "076a5395e94607e0eb658b6882049776a841d469", "tree": "3de6c915d33198c954267eebe5df00d3c3ba21db", "parents": [ "26825b53dc914e4599767ae1e78fe731840027c1" ], "author": { "name": "David Riley", "email": "davidriley@chromium.org", "time": "Fri Aug 21 07:57:38 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri Aug 21 20:08:56 2015" }, "message": "sign_official_build: support signing \u0027kernel\u0027 image type\n\nBRANCH\u003dsigner\nBUG\u003dchrome-os-partner:44227\nTEST\u003d\u0027sign_official_build.sh kernel boot_devsigned.img keys boot_resigned.img\u0027\n\nChange-Id: I805231ef4bd4ed86b35c0d7ca2d3fe1e704caabc\nSigned-off-by: David Riley \u003cdavidriley@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/294954\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\n" }, { "commit": "26825b53dc914e4599767ae1e78fe731840027c1", "tree": "d4090adfa5386e6490b5e66ce5d7bebf7d3ccc5e", "parents": [ "d8ace3dee99487a77be0057e7872b0b5b3a05c0b" ], "author": { "name": "Shelley Chen", "email": "shchen@chromium.org", "time": "Mon Aug 10 18:24:36 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Aug 20 23:26:59 2015" }, "message": "crossystem: Updated crossystem to accomodate Android\n\nPreviously crossystem assumed that mosys was located\nin /usr/sbin. In Android mosys is currently located\nin /system/bin. Using fixed paths as opposed to\n\u0027which\u0027 to prevent attacks where attacker could insert\nmosys in PATH.\n\nBUG\u003dnone\nBRANCH\u003dnone\nTEST\u003dran crossystem, crossystem fw_try_count/\nfw_try_next, crossystem fw_try_count/fw_try_next\u003dx\non link and smaug.\n\nChange-Id: I9604f008d457147188dc852c173d5a184163b339\nSigned-off-by: Shelley Chen \u003cshchen@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/292314\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "d8ace3dee99487a77be0057e7872b0b5b3a05c0b", "tree": "fdccd42aa25bcbc07f9e80288c3837527de8453e", "parents": [ "831f91315ba24ae24e476c7683f0d393f807d779" ], "author": { "name": "Amey Deshpande", "email": "ameyd@google.com", "time": "Fri Aug 14 21:51:21 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Aug 18 01:46:10 2015" }, "message": "sign_official_build: support signing \u0027base\u0027 image type\n\nBRANCH\u003dsigner\nBUG\u003dchromium:512940\nTEST\u003dTested with the following command:\n\n$ ./sign_official_build.sh base chromiumos_base_image.bin ../../tests/devkeys \\\n chromiumos_base_image_signed.bin ../../tests/devkeys/key.versions\n\nChange-Id: Ife2284a6ca82f4306ca26278159859928c0ff2b5\nReviewed-on: https://chromium-review.googlesource.com/293636\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nTested-by: Amey Deshpande \u003cameyd@google.com\u003e\nCommit-Queue: Amey Deshpande \u003cameyd@google.com\u003e\n" }, { "commit": "831f91315ba24ae24e476c7683f0d393f807d779", "tree": "c9afd24160cd88163aa1cbe0c6d0d6a6fd331ecf", "parents": [ "8804be8cbeccfca8085a45c76c0d510f030d9061" ], "author": { "name": "Kevin Cernekee", "email": "cernekee@chromium.org", "time": "Wed Jul 29 00:25:04 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Mon Aug 10 20:42:12 2015" }, "message": "Add \"tpmc pcrextend\" command to extend a PCR\n\nThis is useful for testing different configurations without repeatedly\nreflashing the firmware, e.g.\n\n # stop tcsd\n # tpmc pcr 0\n 0000000000000000000000000000000000000000\n # tpmc pcrextend 0 c42ac1c46f1d4e211c735cc7dfad4ff8391110e9\n # tpmc pcr 0\n 865aedd337518e56f648440b81b4cbd9359fdff3\n \u003creboot and try another value\u003e\n\nBUG\u003dnone\nBRANCH\u003dnone\nTEST\u003dmanual\n\nChange-Id: Ie5814ca2a3a5cf5a0eaf0ffee0385315db09bf25\nSigned-off-by: Kevin Cernekee \u003ccernekee@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/289009\nReviewed-by: Luigi Semenzato \u003csemenzato@chromium.org\u003e\nReviewed-by: Kees Cook \u003ckeescook@chromium.org\u003e\n" }, { "commit": "8804be8cbeccfca8085a45c76c0d510f030d9061", "tree": "f44f8c919a125880d3ed2630da0a27a0be3ecaa7", "parents": [ "14f122601f45d95a0162be8ad1456d9824cb80f9" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Thu Jul 30 20:38:24 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Sat Aug 01 02:51:38 2015" }, "message": "VbNvStorage: Add flags for misc settings\n\n1. Change offset 8 to hold all misc settings (fastboot, boot_on_ac\ndetect) instead of only fastboot settings.\n2. Add flag to hold state of boot_on_ac_detect (If set to 1, AP should\nstart booting as soon as AC is connected in off-state).\n\nBUG\u003dchrome-os-partner:41680\nBRANCH\u003dNone\nTEST\u003dCompiles successfully. make runtests successful.\n\nChange-Id: I64b3fc69bd52cbcaf5899c953ccafa2e81b5b8a5\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/289900\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Vincent Palatin \u003cvpalatin@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "14f122601f45d95a0162be8ad1456d9824cb80f9", "tree": "30463f3d790c81a9e8cbd9317485adea3f0294ee", "parents": [ "a0206634baea037a4958986d72e66231eef8769d" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Fri Jul 17 16:44:29 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jul 21 21:11:28 2015" }, "message": "futility: Compute / verify root key hash\n\nRyu will store a hash of the GBB root key in a struct inside its boot\nblock. Add a vb2_ryu_root_key_hash struct for that.\n\nIf \u0027futility gbb_utility\u0027 is used to set the root key, also look for a\nroot key hash struct and fill it in. No error if not found, because\nthis needs to work on other platforms where the struct is not present.\nThis way, we don\u0027t need to change the signing scripts.\n\nAdded a --roothash option which can be used to check if the root key\nhash is found, and if so, whether it\u0027s empty, valid, or invalid.\n\nBUG\u003dchromium:511405\nBRANCH\u003dryu\nTEST\u003dmanual\n\n Take any existing image.bin.\n cp image.bin image.orig\n\n gbb_utility --roothash image.bin\n - ryu root hash not found\n\n Extract the root key\n gbb_utility -k rootkey.bin image.bin\n - exported root_key to file: rootkey.bin\n\n Now, append a blank ryu root hash struct to it\n echo \u00270000000: 5274 4b79 4861 7368 0100 0000 3000 0000\u0027 | xxd -r \u003e\u003e image.bin\n echo \u00270000000: 0000 0000 0000 0000 0000 0000 0000 0000\u0027 | xxd -r \u003e\u003e image.bin\n echo \u00270000000: 0000 0000 0000 0000 0000 0000 0000 0000\u0027 | xxd -r \u003e\u003e image.bin\n\n Nothing is set yet\n gbb_utility --roothash image.bin\n - ryu root hash is unset\n\n Setting the root key also sets the root hash\n gbb_utility -s -k rootkey.bin image.bin\n - import root_key from rootkey.bin: success\n - calculate ryu root hash: success\n successfully saved new image to: image.bin\n\n See, it verifies\n gbb_utility --roothash image.bin\n - ryu root hash verified\n\n Now, append a bad ryu root hash struct to it\n cp image.orig image.bin\n echo \u00270000000: 5274 4b79 4861 7368 0100 0000 3000 0000\u0027 | xxd -r \u003e\u003e image.bin\n echo \u00270000000: 0001 0000 0000 0000 0000 0000 0000 0000\u0027 | xxd -r \u003e\u003e image.bin\n echo \u00270000000: 0000 0000 0000 0000 0000 0000 0000 0000\u0027 | xxd -r \u003e\u003e image.bin\n\n See, it fails\n gbb_utility --roothash image.bin\n - ryu root hash does not verify\n\n Make sure the library doesn\u0027t contain the magic string\n strings `which futility` | grep RtKyHash\n (should be no output)\n\nChange-Id: Ib46f93cac0f2b532bada4b187ae48efcf4926702\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/286237\nReviewed-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "a0206634baea037a4958986d72e66231eef8769d", "tree": "bdf160cb9d0a40f35595ee5cef573a4d37ee3e16", "parents": [ "0ab72c307a3772c198baf1678c1e65065e081abf" ], "author": { "name": "Duncan Laurie", "email": "dlaurie@chromium.org", "time": "Tue Jul 21 03:01:34 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jul 21 06:07:18 2015" }, "message": "crossystem: Add Skylake PCH GPIO controller ID\n\nAdd the GPIO controller ID that is used in the Skylake PCH\nso it can properly export and use GPIOs that are exported\nin VBNV for write protect.\n\nBUG\u003dchrome-os-partner:42560\nBRANCH\u003dnone\nTEST\u003dverify crossystem output with and without WP enabled\n\nChange-Id: Ic85c202bd0ca15c154c10481926ef18bafe3fac5\nSigned-off-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/286827\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "0ab72c307a3772c198baf1678c1e65065e081abf", "tree": "18a24a34f4695c4fbe8ee100f579479330b2c112", "parents": [ "23769544293077e40815ce9f9bd2cf75b8ccf287" ], "author": { "name": "Hung-Te Lin", "email": "hungte@chromium.org", "time": "Thu Jul 16 10:04:00 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jul 21 04:50:36 2015" }, "message": "image_signing: Add more description to set_gbb_flags.\n\nThere are two new GBB flags added (lid/fastboot) and we should update the\ndescription in set_gbb_flags.\n\nBRANCH\u003dnone\nBUG\u003dnone\nTEST\u003demerge-link vboot_reference\n\nChange-Id: I0d16df03e9427ec1c8780fbb6be10c31eed9bf9e\nSigned-off-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/286052\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "23769544293077e40815ce9f9bd2cf75b8ccf287", "tree": "ee2cf3839551a11c90e4487060386f4fab97764f", "parents": [ "5f16cceb3eca2d20b15531234256fd3e788ecbbc" ], "author": { "name": "Duncan Laurie", "email": "dlaurie@chromium.org", "time": "Tue Jul 21 00:05:52 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jul 21 04:50:29 2015" }, "message": "crossystem: Add skylake platform IDs\n\nAdd the skylake-u and skylake-y vendor/device IDs so it can be\nreported by crossystem.\n\nBUG\u003dchrome-os-partner:42560\nBRANCH\u003dnone\nTEST\u003drun \"crossystem platform_family\" on glados\n\nChange-Id: I5f9b92d404166e56d77cf8b0cd627a3a0b63bedf\nSigned-off-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/286921\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\n" }, { "commit": "5f16cceb3eca2d20b15531234256fd3e788ecbbc", "tree": "6ab0c195755abd037362a7b15971eb54c8a03306", "parents": [ "0e8c964915fffb58032bb59bdb31949de718ca90" ], "author": { "name": "John Zhao", "email": "john.zhao@intel.com", "time": "Thu Apr 02 17:24:51 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jul 14 03:30:32 2015" }, "message": "crossytem:Fix the write protect line gpio value\n\nFor crossystem to work correctly on Strago/Cyan,\nadd Braswell string and correct GPIO offset\ncalculations.\nIn Braswell, write protect line is MF_ISH_GPIO_4\nas encoded as 0x10016 where the GPEAST offset\n(COMMUNITY_OFFSET_GPEAT) is 0x10000\n\nBUG\u003dchrome-os-partner:40835\nBRANCH\u003dNone\nTEST\u003dtest_that -b \u003cstrago/cyan\u003e \u003cIP\u003e platform_Crossystem\n\nChange-Id: I365f3d6ca9f3ac7ef50abb9b2ba13f184d39c100\nSigned-off-by: John Zhao \u003cjohn.zhao@intel.com\u003e\nSigned-off-by: Arindam Roy \u003carindam.roy@intel.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/274841\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\nCommit-Queue: Bernie Thompson \u003cbhthompson@chromium.org\u003e\n" }, { "commit": "0e8c964915fffb58032bb59bdb31949de718ca90", "tree": "131745e2804d4d2c3d766cc864c2b03293c366e6", "parents": [ "fbf631c845c08299f0bcbae3f311c5807d34c0d6" ], "author": { "name": "Hung-Te Lin", "email": "hungte@chromium.org", "time": "Thu Jul 09 06:53:33 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Jul 09 12:30:38 2015" }, "message": "crossystem: Revise description of sw_wpsw_boot.\n\nThe sw_wpsw_boot was made for some feature that was almost never completed, and\nonly makes sense on Baytrail platforms. To prevent confusion we should address\nthat in the crossystem description.\n\nBRANCH\u003dnone\nBUG\u003dchromium:508269\nTEST\u003dmake test\n\nChange-Id: I1fbc7a0e9e8c1f8503ae8ae9dfb6e80c8da892e3\nReviewed-on: https://chromium-review.googlesource.com/284425\nTested-by: Hung-Te Lin \u003chungte@chromium.org\u003e\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\nCommit-Queue: Hung-Te Lin \u003chungte@chromium.org\u003e\n" }, { "commit": "fbf631c845c08299f0bcbae3f311c5807d34c0d6", "tree": "16b1c866d8d6d8e86c032ef89fc643e438741a53", "parents": [ "dc600e8b129327e4f5a8cfbbe5343630f0f65b68" ], "author": { "name": "David Hendricks", "email": "dhendrix@chromium.org", "time": "Mon Jun 29 22:05:58 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jun 30 10:47:49 2015" }, "message": "crossystem: Add check for \"mkbp\" back\n\nWe may have been over-zealous earlier when trying to eliminate\nreferences to mkbp. Since crossystem runs on all ChromeOS devices,\nthis re-adds \"mkbp\" back to mitigate the risk of encountering\nproblems on systems running newer versions of ChromeOS but with\nolder firmware.\n\nBUG\u003dchrome-os-partner:21097\nBRANCH\u003dnone\nTEST\u003dCompiled for veyron_brain\n\nChange-Id: Ia0086687fbc3a1195b062367ccb6ee5c41acd026\nSigned-off-by: David Hendricks \u003cdhendrix@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/282602\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-by: Julius Werner \u003cjwerner@chromium.org\u003e\n" }, { "commit": "dc600e8b129327e4f5a8cfbbe5343630f0f65b68", "tree": "cb741d3b7a0475e0837748036a77bc3e5dfdce5b", "parents": [ "f843871cd5cc071ce1f6c15e8f1fd8036edc423b" ], "author": { "name": "David Hendricks", "email": "dhendrix@chromium.org", "time": "Tue May 26 23:48:39 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Jun 25 02:11:47 2015" }, "message": "crossystem: Check for \"cros-ec\" instead of \"mkbp\" for *NvStorage\n\nThis changes the string we look for in the devicetree on ARM\nplatforms to look for \"cros-ec\" (DT uses dashes instead of\nunderscores) instead of \"mkbp\".\n\nBUG\u003dchrome-os-partner:21097\nCQ-DEPEND\u003dCL:273347\nBRANCH\u003dnone\nTEST\u003dwith depthcharge patch applied, ran crossystem on newly\nbooted system and saw VBNV-related variables turn out the same.\n\nSigned-off-by: David Hendricks \u003cdhendrix@chromium.org\u003e\nChange-Id: Iac43f5381327eb878a8d0db606b78bb7bdce816f\nReviewed-on: https://chromium-review.googlesource.com/273391\nCommit-Queue: Stefan Reinauer \u003creinauer@chromium.org\u003e\nTested-by: Stefan Reinauer \u003creinauer@chromium.org\u003e\nReviewed-by: Stefan Reinauer \u003creinauer@chromium.org\u003e\n" }, { "commit": "f843871cd5cc071ce1f6c15e8f1fd8036edc423b", "tree": "ac8dd04ac511064a8275a2788497c53dfa0df203", "parents": [ "1eb83efdba367db2a590eb94a0cc45cd538aa696" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Sat Jun 20 21:17:42 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jun 23 20:41:30 2015" }, "message": "recovery: Add recovery reason for fastboot mode requested in fw\n\nBUG\u003dchrome-os-partner:40196\nBRANCH\u003dNone\nTEST\u003dCompiles successfully\n\nChange-Id: Ic69834f2e23926e618349b5a56db549a290cd0c2\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/280922\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "1eb83efdba367db2a590eb94a0cc45cd538aa696", "tree": "72efa521b7d5357346c7054c65243454e6234c1e", "parents": [ "637ff03502f3511d90e8d79cc1c52b3be01d6cd3" ], "author": { "name": "Andrey Ulanov", "email": "andreyu@google.com", "time": "Thu Jun 11 03:02:06 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Sat Jun 13 02:53:36 2015" }, "message": "cgpt repair: fix segfault which occurs when one of the headers is bad\n\nWhen one of GPT headers is invalid the corresponding partition table\nis not loaded and corresponding pointers in GptData are NULL.\nGptRepair will try to memcpy one entries table to another which\nresults in SIGSEGV.\n\nThis change fixes it by freeing and then reallocating bad copy of\npartition table. This potentially fixes problems which would occur\nif two tables have different size.\n\nChange that initially introduced this problem by not always allocating\nsecondary_entries:\nhttps://chromium-review.googlesource.com/223800\n\nTEST\u003d\"cgpt repair\" works where it previously didn\u0027t\nTEST\u003dmake runtests\nBUG\u003dbrillo:1203\nBRANCH\u003dnone\n\nChange-Id: Ibb2fcf33faa5ba157b0865d04c90ee3f26eee113\nReviewed-on: https://chromium-review.googlesource.com/276766\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Andrey Ulanov \u003candreyu@google.com\u003e\nTested-by: Andrey Ulanov \u003candreyu@google.com\u003e\n" }, { "commit": "637ff03502f3511d90e8d79cc1c52b3be01d6cd3", "tree": "8398811b813ebc297c9a3774d5bff560b2d64ef1", "parents": [ "d7f0f93fa878e6dd7435adbe034e1fc7474f94b0" ], "author": { "name": "Yunlian Jiang", "email": "yunlian@google.com", "time": "Tue Jun 09 23:21:56 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Jun 11 18:27:24 2015" }, "message": "vboot_reference: fix unittest when building with clang.\n\nWhen linking vboot_api_kernel4_tests, there are two VbBootNormal()\navailable, the gcc chooses the one in vboot_api_kernel4_tests.c and\nthe test passes, the clang chooses the one in vboot_api_kernel.c and\nmake the unittest fail. This CL makes the one in vboot_api_kernel.c\na weak symbol so that clang can choose the one in\nvboot_api_kernel4_tests.c\n\nBUG\u003dchromium:498469\nBRANCH\u003dnone\nTEST\u003dCC\u003dx86_64-cros-linux-gnu-clang FEATURES\u003d\u0027test\u0027\n emerge-amd64-generic vboot_reference\n\nChange-Id: Ibcb78ee055fc9485dbc2bcc1d1cf98144a1a3b64\nReviewed-on: https://chromium-review.googlesource.com/276504\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Yunlian Jiang \u003cyunlian@chromium.org\u003e\nTested-by: Yunlian Jiang \u003cyunlian@chromium.org\u003e\n" }, { "commit": "d7f0f93fa878e6dd7435adbe034e1fc7474f94b0", "tree": "7206dcafd5f53b9a16e9908fd9a0470697f72db4", "parents": [ "3479e84e3041336f1e967c302c5a35cb64819927" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Tue May 19 20:41:09 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jun 09 21:30:39 2015" }, "message": "vboot2: Add 2.0 api layer to verify kernel partition\n\nThis allows the caller to load the kernel partition and then pass it\nto vboot for verification, rather than having vboot assume the kernel\npartitions are all on a block storage device.\n\nNext up, APIs for the caller to parse partition information from a GPT\n(yes, that\u0027s cgptlib, but we\u0027ll make it more easily callable by\ndepthcharge).\n\nBUG\u003dchromium:487699\nBRANCH\u003dnone\nTEST\u003dmake -j runtests\n\nChange-Id: I388085c7023f4c76d416f37df0607019bea844ac\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/275646\nReviewed-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\n" }, { "commit": "3479e84e3041336f1e967c302c5a35cb64819927", "tree": "0fb1c4ad8766579de88b8335680a84ecc6bf8a97", "parents": [ "22da78ce594d1e9893fe418e4a021db17002f777" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Thu Jun 04 16:07:49 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Jun 04 20:50:58 2015" }, "message": "recovery: Add recovery reasons for BCB\n\nBCB is bootloader control block. Add reasons specific to BCB:\n1. In case of any error reading/writing BCB (internal FW error)\n2. User-mode requested recovery via BCB (user-mode requested)\n\nBUG\u003dchrome-os-partner:40960\nBRANCH\u003dNone\nTEST\u003dCompiles successfully\n\nChange-Id: I0ac362ba7267a08313cb3077be686aa73367e53b\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/275222\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "22da78ce594d1e9893fe418e4a021db17002f777", "tree": "f6a0ab675426653a9cb9a5febd90e107b23d8bb0", "parents": [ "7a1c0d1ec852ee86237aba7f3c87d642ca8e00b0" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Fri May 29 17:53:11 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Jun 04 19:32:56 2015" }, "message": "vboot2: Add routines to load kernel preamble\n\nThe kernel data itself will be read and verified by a subsequent\nchange.\n\nBUG\u003dchromium:487699\nBRANCH\u003dnone\nTEST\u003dmake -j runtests\n\nChange-Id: Ife4f8250493ec6457f91fda57ae8d4d7bf18ec89\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/274038\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "7a1c0d1ec852ee86237aba7f3c87d642ca8e00b0", "tree": "191893fb52afa5fce615f6f1e2ff3929f8c349d6", "parents": [ "04e2338857e66ee1af7a826e320e6fe755711f65" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Tue Jun 02 17:32:52 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu Jun 04 11:57:47 2015" }, "message": "cgpt: Add a callback to allow override of GPT entry priority\n\nThis can be used by implementations that want to request vboot to\nfavor a particular kernel entry for booting without affecting the\nchecks for rollback protection and image verification.\n\nCQ-DEPEND\u003dCL:274716, CL:274932, CL:275171\nBUG\u003dNone\nBRANCH\u003dNone\nTEST\u003dCompiles successfully. make -j runtests successful.\n\nChange-Id: I6a4600020354f5d4118c17f083c353c2585c4181\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/274558\nReviewed-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Stefan Reinauer \u003creinauer@chromium.org\u003e\nTested-by: Nicolas Boichat \u003cdrinkcat@chromium.org\u003e\nCommit-Queue: Nicolas Boichat \u003cdrinkcat@chromium.org\u003e\nTrybot-Ready: Nicolas Boichat \u003cdrinkcat@chromium.org\u003e\n" }, { "commit": "04e2338857e66ee1af7a826e320e6fe755711f65", "tree": "86da63d1fed480baa19dae5f91660a67716def90", "parents": [ "7e21698e42dba31cc3e3c6b58a31bd050d3698ac" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Sat May 30 01:00:46 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jun 02 18:40:57 2015" }, "message": "vboot_api_kernel: Do not pre-populate variables in\nVbVerifyMemoryBootImage\n\nDo not use values from the header or preamble until it is known to be\ngood.\n\nBUG\u003dNone\nBRANCH\u003dNone\nTEST\u003dCompiles successfully and VbVerifyMemoryBootImage returns early\nfor images with bad values in header.\n\nChange-Id: Ic026f49292a139e0a04c2556ca9fa62ff277b18f\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/274141\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "7e21698e42dba31cc3e3c6b58a31bd050d3698ac", "tree": "c6f2e5839de0e1a7f71ff80e31ae2e54c4c06acf", "parents": [ "773b5ac3a61f4ced2e0815959a6824bf8ba62f4f" ], "author": { "name": "Julius Werner", "email": "jwerner@chromium.org", "time": "Fri May 29 23:56:20 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue Jun 02 01:04:00 2015" }, "message": "vboot2: secdata: Check struct_version on initialization\n\nThis patch reintroduces a vb2_secdata-\u003estruct_version check similar to\nthe one that was removed in CL:244846. The CRC is not a reliable way to\ndetect zeroed buffers, so this check helps vboot fail earlier and more\nclearly in certain situations.\n\nBRANCH\u003dkitty,smaug,storm,veyron\nBUG\u003dchrome-os-partner:40778\nTEST\u003dmake runtests. Rebooted Jerry with \u0027mem w 0xff7601b0 0xfdb9\u0027, saw\nthat recovery reason was now 0x2b (VBNV_RECOVERY_VB2_SECDATA_INIT).\n\nChange-Id: Ic4376d127e6d14d4ef9c2f53c83090040ca4cb68\nSigned-off-by: Julius Werner \u003cjwerner@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/274138\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-by: Vadim Bendebury \u003cvbendeb@chromium.org\u003e\n" }, { "commit": "773b5ac3a61f4ced2e0815959a6824bf8ba62f4f", "tree": "4349fed1342677e51dafceaaf667ac84f58b4f1b", "parents": [ "d08a3435f867700c90e33398bf104557d98bf791" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Tue May 26 04:49:11 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri May 29 11:29:29 2015" }, "message": "fastboot: Add routines for unlock and lock device\n\nAdd support for functions to request unlock and lock of devices in\nresponse to fastboot oem unlock/lock commands. Unlock operation is\nequivalent to enabling dev mode and lock operation is equivalent to\nleaving dev mode. It is the responsibility of the caller to ensure\nthat user confirmation is obtained before unlock/lock operations.\n\nBUG\u003dchrome-os-partner:40196\nBRANCH\u003dNone\nTEST\u003dCompiles successfully and fastboot lock/unlock operations work as\nexpected on smaug. Added tests to ensure lock/unlock operations are\ncovered. Verified using make -j runtests.\n\nChange-Id: Ibafe75abdd1202473009208a414f3996d537db4f\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/273182\nReviewed-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "d08a3435f867700c90e33398bf104557d98bf791", "tree": "51ea35318cd6b29399930ee97beb05af0a0e53af", "parents": [ "c180460febf4039c86b87ba708c8299749cbfdd6" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Tue May 26 04:48:02 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri May 29 11:29:26 2015" }, "message": "fastboot: Add fastboot related flags to vb2\n\nBUG\u003dchrome-os-partner:40196\nBRANCH\u003dNone\nTEST\u003dCompiles successfully.\n\nChange-Id: I4305436b2ae46254e4e8b12039ffed95634d62c2\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/273181\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "c180460febf4039c86b87ba708c8299749cbfdd6", "tree": "13f9dd770685ac500abea63fd0b3c1d06cc7253a", "parents": [ "ebf886b5fd3dd75a00205879f3847198ecf83bdd" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Tue May 26 04:46:10 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri May 29 11:29:20 2015" }, "message": "fastboot: Add fastboot related flags to nvstorage\n\nUse unused offset 8 for fastboot related flags.\n\nBUG\u003dchrome-os-partner:40196\nBRANCH\u003dNone\nTEST\u003dCompiles successfully.\n\nChange-Id: I6df0985924ba80cdcb68bb6b7658bf962f01287f\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/273180\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "ebf886b5fd3dd75a00205879f3847198ecf83bdd", "tree": "79ca3669907a75aefbc84d1a9d3ac659e741f5e1", "parents": [ "f27436032668e332b4ed7cc168bbcc2a939ae7b9" ], "author": { "name": "Patrick Georgi", "email": "pgeorgi@google.com", "time": "Tue Feb 10 13:58:28 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu May 28 16:30:17 2015" }, "message": "Provide a way to disable counting failed boots\n\nWhen the lid is closed and external power is applied\nthe system may boot and shut down faster than required\nfor the OS to determine that things were alright.\n\nIn timed charging setups this led to systems ending up\nto consider the current version broken because it \"failed\"\nrepeatedly.\n\nRemain generic about the reason for not counting boots\nsince there may be more situations in which we want to\nhandle the situation optimistically.\n\nBRANCH\u003dnone\nBUG\u003dchromium:446945\nTEST\u003dnone\n\nChange-Id: Iea350e3c98d5c00156da682e52c90a882ba017c0\nSigned-off-by: Patrick Georgi \u003cpgeorgi@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/249150\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\n" }, { "commit": "f27436032668e332b4ed7cc168bbcc2a939ae7b9", "tree": "89e269aa24e47bb0c102606b4c96992e80d3d87e", "parents": [ "05371345b75454c20a12433384a0d5dc29064f07" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Thu May 21 21:39:11 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Wed May 27 23:18:43 2015" }, "message": "fastboot: Add routine for verifying kernel image loaded in memory\n\nThis API allows fastboot boot from memory command to verify that the\nimage loaded in memory is signed properly using recovery keys. Thus,\nonly officially signed recovery images can be booted using fastboot\nboot command in recovery mode.\n\nHowever, if GBB_FLAG_FORCE_DEV_BOOT_FASTBOOT_FULL_CAP is set, then\nthis routine will not perform any check and return okay for any image\nsent by fastboot boot.\n\nBUG\u003dchrome-os-partner:40196\nBRANCH\u003dNone\nTEST\u003dCompiles successfully. With GBB override for FASTBOOT_FULL_CAP\nset any signed image is allowed to boot. With FASTBOOT_FULL_CAP not\nset, then only officially signed image is allowed to boot. (make -j\nruntests successful)\n\nChange-Id: I78028853bd1ad09d3c610a687f327560557d5681\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/272696\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "05371345b75454c20a12433384a0d5dc29064f07", "tree": "ce59c865af7bc94865b4357748e7e597c63b74e4", "parents": [ "3d5cd88f90ca38e7b2736bb1569c50049e710453" ], "author": { "name": "Amey Deshpande", "email": "ameyd@google.com", "time": "Thu May 21 21:46:06 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri May 22 16:49:06 2015" }, "message": "sign_official_build: preserve /boot for legacy BIOS\n\nThis patch checks for \u0027cros_legacy\u0027 in the kernel config, and skips\nrunning strip_boot_from_image.sh if present. This is because\n\u0027cros_installer postinst\u0027 on legacy BIOS relies on presence of /boot in\nrootfs.\n\nBRANCH\u003dsigner\nBUG\u003db:20947354\nTEST\u003dRan the script with devkeys, and checked presence of /boot in the\nsigned .bin file by mounting locally\n\n$ ./sign_official_build.sh ssd chromiumos_image.bin ../../tests/devkeys \\\n chromiumos_image_signed.bin ../../tests/devkeys/key.versions\n\nChange-Id: Ieb919067b353839019bc1c561d7bb66bebac1040\nReviewed-on: https://chromium-review.googlesource.com/272742\nTested-by: Amey Deshpande \u003cameyd@google.com\u003e\nReviewed-by: Mike Frysinger \u003cvapier@chromium.org\u003e\nCommit-Queue: Amey Deshpande \u003cameyd@google.com\u003e\n" }, { "commit": "3d5cd88f90ca38e7b2736bb1569c50049e710453", "tree": "691881177554996b0a9dd51c00976b69491e2600", "parents": [ "b87d1ec11813e0f75dafd15fa0a309b506208bc6" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Thu May 21 00:22:17 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri May 22 01:22:04 2015" }, "message": "vboot2: Add routines to load and verify kernel keyblock\n\nThese are slightly more complex than the firmware versions, because\nthey need to deal with developer-signed keyblocks and keyblock flags.\n\nBUG\u003dchromium:487699\nBRANCH\u003dnone\nTEST\u003dmake -j runtests\n\nChange-Id: I682c14ddfe729984f2629dfbe66750e5cd5ab75e\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/272541\nReviewed-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\n" }, { "commit": "b87d1ec11813e0f75dafd15fa0a309b506208bc6", "tree": "ea7954c041ddd762b2e1156c0cccfd6e3429a536", "parents": [ "2d25e837ccc1c4f3123fedc056a396b3e6e3aa5f" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Tue May 19 19:45:20 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Fri May 22 01:21:59 2015" }, "message": "vboot2: Split keyblock checking and signature validation\n\nThis is necessary for the next change, which adds keyblock hash checking.\n\nAlso clean up some other assorted comments, and move the diagnostic\ncheck of root key to see if it\u0027s the checked-in one earlier in\nfirmware preamble validation so it\u0027s closer to where the root key is\nloaded.\n\nNo functional or higher-level API changes; just shuffling around code\nunder the covers.\n\nBUG\u003dchromium:487699\nBRANCH\u003dnone\nTEST\u003dmake -j runtests\n\nChange-Id: Ibc3960a4d882dc2ad8684e235db4b9d066eac080\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/272223\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "2d25e837ccc1c4f3123fedc056a396b3e6e3aa5f", "tree": "54ce9bede8f2b3cc08e2304e3acb90d4d61972f0", "parents": [ "ea71df260e9041dd5260425dae3d6f5412516b9b" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Tue May 12 23:39:01 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu May 21 03:44:13 2015" }, "message": "vboot2: Add routine to verify kernel preamble\n\nThis also checks that the bootloader and vmlinuz headers, if present,\nare within the signed part of the kernel blob; the vboot1 routines\ndidn\u0027t do that. That wasn\u0027t harmful at firmware boot time because the\nvboot1 routines would only load as much data as was signed, but in\nvboot2 loading the kernel data is the responsibility of the caller so\nwe need to check.\n\nBUG\u003dchromium:487699\nBRANCH\u003dnone\nTEST\u003dmake -j runtests\n\nChange-Id: I73eb4831e5d3d7a642b6cb85cb55857d87fcc0af\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/270797\n" }, { "commit": "ea71df260e9041dd5260425dae3d6f5412516b9b", "tree": "115e83f5aef8e7e1e0da38c0758d1806e220d3d4", "parents": [ "138bb3c004154f67f3b37aafef3a6efa8bf0b338" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Sat May 16 01:15:18 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Sat May 16 04:17:26 2015" }, "message": "GBB: Add missing flag LID_SHUTDOWN to vb2_gbb_flag structure\n\nBUG\u003dNone\nBRANCH\u003dNone\nTEST\u003dCompiles successfully\n\nChange-Id: I80a501efc3940ca5657dc143c0ab3c6b020dc1e0\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/271620\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "138bb3c004154f67f3b37aafef3a6efa8bf0b338", "tree": "c67f7fa0e11061126681eadd743ea69ed165532d", "parents": [ "9101df2fe3ed4f0e8b65121ffc1c7e8b2d65b35d" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Fri May 15 07:44:41 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Sat May 16 04:17:21 2015" }, "message": "GBB: Add flag for forcing full fastboot capability in firmware\n\nThis flag is equivalent to FORCE_DEV_BOOT_USB. It allows full fastboot\ncapability in firmware for developer mode.\n\nBUG\u003dchrome-os-partner:40196\nBRANCH\u003dNone\nTEST\u003dCompiles successfully for smaug.\n\nChange-Id: I82a2ebe7a8b3bbf38694ab81ca2678624f77fca1\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/271410\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "9101df2fe3ed4f0e8b65121ffc1c7e8b2d65b35d", "tree": "e90832599181e8222d660055bf962ecf84c3b5b5", "parents": [ "07e56f22b852f4d96af2b2df57da11f6938778dd" ], "author": { "name": "Furquan Shaikh", "email": "furquan@google.com", "time": "Thu May 14 19:53:19 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Sat May 16 04:17:16 2015" }, "message": "nvstorage: Add new flag VBNV_DEV_BOOT_FASTBOOT_FULL_CAP\n\nAdd a new flag to nvstorage for controlling fastboot capabilities\noffered in firmware in dev-mode. By default, value of this flag would\nbe ignored in normal mode. Thus, when fastboot-based recovery is\nentered from normal mode, only limited capability would be available\nin firmware.\n\nAfter switching to dev-mode, this flag can be set automatically by\nuser script after performing the wipe or it can be set manually using\ncrossystem. When fastboot-based recovery is entered from dev mode and\nthis flag is set, it will provide full fastboot capability in the\nfirmware.\n\nBUG\u003dchrome-os-partner:40196\nBRANCH\u003dNone\nTEST\u003dCompiles successfully for smaug. make runalltests successful.\n\nChange-Id: I761a9ab304dd90f0b73081acc9ce1f8d9052325f\nSigned-off-by: Furquan Shaikh \u003cfurquan@google.com\u003e\nReviewed-on: https://chromium-review.googlesource.com/271369\nReviewed-by: Aaron Durbin \u003cadurbin@chromium.org\u003e\nReviewed-by: Randall Spangler \u003crspangler@chromium.org\u003e\nCommit-Queue: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTrybot-Ready: Furquan Shaikh \u003cfurquan@chromium.org\u003e\nTested-by: Furquan Shaikh \u003cfurquan@chromium.org\u003e\n" }, { "commit": "07e56f22b852f4d96af2b2df57da11f6938778dd", "tree": "5c55ca659e9962b20b55eda6d4633b9101f0c7f4", "parents": [ "fb4e4080112d9005f83b57551ab19cbf478da36a" ], "author": { "name": "Julius Werner", "email": "jwerner@chromium.org", "time": "Tue Jan 06 18:02:46 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Sat May 16 01:42:28 2015" }, "message": "chromeos-tpm-recovery: Convert to manual TPM reset script for developers\n\nchromeos-tpm-recovery has not been used for anything in forever (see\nCL:238236), but it is still installed on every image. Resetting the TPM\n(e.g. to resolve rollback issues when reflashing an MP-signed device to\ndev firmware) is a common request by developers, and I get tired of\nalways digging out the required tpmc commands manually again. Let\u0027s\nrepurpose this script as a simple one-shot tool for developers to reset\ntheir TPM, so the next time someone asks we can just tell them \u0027boot a\ntest image in recovery mode and run chromeos-tpm-recovery\u0027.\n\nBRANCH\u003dnone\nBUG\u003dchromium:419942\nTEST\u003dRan on a Jerry, confirmed that TPM spaces were reset.\n\nChange-Id: Ia95246cfed3dc9b0c6fdb0481218e3ae14d8318a\nSigned-off-by: Julius Werner \u003cjwerner@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/271512\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\nReviewed-by: Luigi Semenzato \u003csemenzato@chromium.org\u003e\n" }, { "commit": "fb4e4080112d9005f83b57551ab19cbf478da36a", "tree": "1d7f42ca5856dfc0bda6562c72f553f167df91db", "parents": [ "dc49a6827670abc0f2dc45178c2623e070ff5961" ], "author": { "name": "Julius Werner", "email": "jwerner@chromium.org", "time": "Fri May 15 19:50:07 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Sat May 16 01:42:20 2015" }, "message": "vboot2: Support VB2_GBB_FLAG_DISABLE_FW_ROLLBACK_CHECK\n\nLooks like the DISABLE_FW_ROLLBACK_CHECK GBB flag (0x200) was forgotten\nin the vboot2 implementation. It\u0027s too late for Veyron now, but let\u0027s at\nleast fix it for future devices.\n\nBRANCH\u003dnone\nBUG\u003dNone\nTEST\u003dmake runtests\n\nChange-Id: I867f7aada28be3897efda73a6bdc3b0848c23dca\nSigned-off-by: Julius Werner \u003cjwerner@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/271419\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "dc49a6827670abc0f2dc45178c2623e070ff5961", "tree": "7971d6d9adc3f2440b98e5ba2157bdc91c6a7d03", "parents": [ "bf9c2760d2657e29e481150fb3fab8809c3ab755" ], "author": { "name": "Daisuke Nojiri", "email": "dnojiri@chromium.org", "time": "Wed May 13 22:32:14 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu May 14 02:25:57 2015" }, "message": "Detect GBB 1.1 also as impcompatible version\n\nOlder GBB headers (e.g. 1.0 and 1.1) do not have hwid_digest. In such cases,\nPCR1 is currently extended from 0, causing a remote attestation failure.\nThis change makes all GBB headers older than 1.2 incompatible.\n\nBUG\u003dnone\nBRANCH\u003dtot\nTEST\u003dmake -j runtests\n\nChange-Id: I7a3b19c2da325a3fa4b9c1fe06ed6f43cb51fb9e\nSigned-off-by: Daisuke Nojiri \u003cdnojiri@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/270796\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "bf9c2760d2657e29e481150fb3fab8809c3ab755", "tree": "eebd400475f10183075245278893f04fe6a2548e", "parents": [ "0140cd2906b1107ef9ea60ed7a81f8cbdc9162f8" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Tue May 12 20:44:30 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Wed May 13 22:23:42 2015" }, "message": "vboot2: Add support for kernel version secure data space\n\nHolds kernel rollback information. Will be used by vboot 2.0 kernel\nverification.\n\nBUG\u003dchromium:487699\nBRANCH\u003dnone\nTEST\u003dmake -j runtests\n\nChange-Id: Ib4a70e943ebd79aac06404df09cf4ce62d719201\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/270626\nReviewed-by: Bill Richardson \u003cwfrichar@chromium.org\u003e\n" }, { "commit": "0140cd2906b1107ef9ea60ed7a81f8cbdc9162f8", "tree": "deb1efd1cda51a9d88f11708050144876a38a4db", "parents": [ "957b424c52d1cb0075f2a464e6845fcb59da41df" ], "author": { "name": "Julius Werner", "email": "jwerner@chromium.org", "time": "Sat May 09 06:00:16 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue May 12 01:17:23 2015" }, "message": "vboot1: Condition default legacy boot on dev_boot_legacy\n\nThis patch fixes what I think is an inconsistency in the existing legacy\nboot behavior: when the GBB flag that defaults to legacy boot is set,\nrunning out the 30 second timer would still boot legacy mode even if\ndev_boot_legacy is not actually set (whereas pressing CTRL+L in the\nsame configuration would beep and refuse).\n\nThis patch makes both legacy boot trgiggers check the same condition\nbefore boot. This does not restrict functionality since anyone who sets\nthe DEFAULT_DEV_BOOT_LEGACY GBB flag could simply set\nFORCE_DEV_BOOT_LEGACY at the same time. It does however open up an\ninteresting new use case of using NVRAM to change back-and-forth between\nlegacy and normal developer mode (after GBB flags are changed once and\nwrite-protection is enabled again).\n\nIf this is updated in the field it might lock existing devices out of\nlegacy mode... however, since by far the most common GBB flag\ncombination recommended on the internet seems to be 0x489 (including\nFORCE_DEV_BOOT_LEGACY), I doubt this would be a problem in practice.\n\nBRANCH\u003dtbd\nBUG\u003dchrome-os-partner:39999\nTEST\u003dBooted with GBB flags 0x4b9 and 0x439, observed difference.\n\nChange-Id: If6a6d99ab2cf116db2237fdc3df97fc22a68251c\nSigned-off-by: Julius Werner \u003cjwerner@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/270182\nReviewed-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\n" }, { "commit": "957b424c52d1cb0075f2a464e6845fcb59da41df", "tree": "ec191e5bec5612a00cfb524e28dc34145cfe41c2", "parents": [ "f81fce91bf885293f1447c1197bb0c4143d8fced" ], "author": { "name": "Julius Werner", "email": "jwerner@chromium.org", "time": "Sat May 09 05:54:14 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Tue May 12 01:17:16 2015" }, "message": "vboot1: Lock TPM physical presence (kernel rollback) on legacy boot\n\nEven though legacy boot is an unsafe mode that has to be manually\ninitiated by the user, we should still lock the kernel TPM space to be\nconsistent with existing developer mode practice.\n\nBRANCH\u003dtbd\nBUG\u003dchrome-os-partner:39999\nTEST\u003dSpent over an hour unsuccessfully trying to get SeaBIOS to boot a\nChromium test image on my Falco. Decided that\u0027s not worth it an just\ntested the firmware side of this (pressing CTRL+L when legacy mode is\nenabled and disabled, multiple times, with and without GBB flag\nDEFAULT_DEV_BOOT_LEGACY).\n\nChange-Id: I3b02b59a9055431d222c0c7446de2cd7d2e0bb82\nSigned-off-by: Julius Werner \u003cjwerner@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/270181\nReviewed-by: Duncan Laurie \u003cdlaurie@chromium.org\u003e\n" }, { "commit": "f81fce91bf885293f1447c1197bb0c4143d8fced", "tree": "f2cd42b1d7c0ccd1b5bdf0349610d34a20edee4d", "parents": [ "7dd3bd0fcf565901aacc512cd29cefe19291c2e7" ], "author": { "name": "Randall Spangler", "email": "rspangler@chromium.org", "time": "Tue May 05 23:06:50 2015" }, "committer": { "name": "ChromeOS Commit Bot", "email": "chromeos-commit-bot@chromium.org", "time": "Thu May 07 00:00:36 2015" }, "message": "Make SHA library accessible to calling firmware\n\nAnd add a vb2_digest_buffer() call which produces the hash of a buffer\nall in a single function call. That function actually already\nexisted, but was in a unit test file rather than in the library\nitself. It\u0027s a small function, so adding it won\u0027t increase the size\nof the library significantly - or at all, on platforms which compile\nwith -ffunction-sections.\n\nThis allows coreboot to reuse this SHA library for hashing CBFS\nentries and file data. All it has to do is #define\nNEED_VB2_SHA_LIBRARY and then #include \"vb2_api.h\".\n\nBUG\u003dchromium:482652\nBRANCH\u003dnone\nTEST\u003dmake -j runtests\n\nChange-Id: Ice2d0929324b58b2665f3989b5b887225f6ef61e\nSigned-off-by: Randall Spangler \u003crspangler@chromium.org\u003e\nReviewed-on: https://chromium-review.googlesource.com/269523\nReviewed-by: Julius Werner \u003cjwerner@chromium.org\u003e\n" } ], "next": "7dd3bd0fcf565901aacc512cd29cefe19291c2e7" }