c6051ff378d7c865361b13d9883e0e6ebb31a4be |
|
17-Jul-2012 |
Nirnimesh <nirnimesh@chromium.org> |
[vboot_reference] Prepare for the removal of /root/.forget_usernames from test images /root/.forget_usernames is going away from test images. It was a hack. BUG=chromium-os:31807 TEST=suite:bvt Change-Id: I27b606fa0232514f3ec45a4ed765b89efcf8f07e Reviewed-on: https://gerrit.chromium.org/gerrit/27588 Reviewed-by: Gaurav Shah <gauravsh@chromium.org> Tested-by: Nirnimesh <nirnimesh@chromium.org> Commit-Ready: Nirnimesh <nirnimesh@chromium.org>
/external/vboot_reference/scripts/image_signing/tag_image.sh
|
db1d5b20f890c2109a19e7626321c3d51e13e813 |
|
11-Apr-2012 |
Mike Frysinger <vapier@chromium.org> |
signer scripts: use `sudo` if need be when modifying /etc/lsb-release If we try to run the signing_poller daemon as non-root, it fails to set the channel. Detect if the lsb file is writable, and if not, switch to using sudo on the fly. BUG=None TEST=`./signer/signing_poller.py` as non-root and setting the channel works Change-Id: Iadb10ae68582edfb332f33d3b101c83949ee9502 Reviewed-on: https://gerrit.chromium.org/gerrit/20089 Reviewed-by: Gaurav Shah <gauravsh@chromium.org> Tested-by: Mike Frysinger <vapier@chromium.org> Commit-Ready: Mike Frysinger <vapier@chromium.org>
/external/vboot_reference/scripts/image_signing/tag_image.sh
|
d170a9d542dd4770c25d5ed82429a55391d88218 |
|
10-Apr-2012 |
Gaurav Shah <gauravsh@chromium.org> |
signer scripts: unmount loop devices without -d arg to umount Investigations in crosbug.com/26483 revealed a bug in loop device handling if 'umount -d' was called on loop devices mounted using 'mount -o loop'. This CL changes all invocations of umount to remove the -d option since they are always in the context of a loop device creating using -o loop. BUG=chrome-os-partner:8156 TEST=none Change-Id: I96f30664c3f9148d3b57d430002512d8e94b66bc Reviewed-on: https://gerrit.chromium.org/gerrit/19858 Reviewed-by: David James <davidjames@chromium.org> Commit-Ready: Gaurav Shah <gauravsh@chromium.org> Tested-by: Gaurav Shah <gauravsh@chromium.org>
/external/vboot_reference/scripts/image_signing/tag_image.sh
|
192d7e14f6f0991ff1ca53180ad69136fd04570d |
|
15-Mar-2011 |
Bill Richardson <wfrichar@chromium.org> |
Add --leave_firmware_alone flag for BIOS testing purposes. BUG=chromium-os:13100 TEST=none (BIOS team will test by using it) Change-Id: Ifedeac1a0d13d36a069531bfaba4bdb7b3457406 Review URL: http://codereview.chromium.org/6696013
/external/vboot_reference/scripts/image_signing/tag_image.sh
|
cb844af2a314622f92b92836cc9ccded61eca842 |
|
19-Oct-2010 |
Gaurav Shah <gauravsh@chromium.org> |
Add a tag for removing crosh_workarounds. Also add options for manipulating /etc/lsb-release. Adds --crosh_workarounds (only removal is supported), --remove_test_label (for removing test in /etc/lsb-release) and --change_dev_to_beta (for changing "dev" -> "beta" in /etc/lsb-release) BUG=chromium-os:5920 TEST=manual Change-Id: Id4c94d76a6d8794a4d134790d0c2f5d4a336084f Review URL: http://codereview.chromium.org/3781012
/external/vboot_reference/scripts/image_signing/tag_image.sh
|
c5175e3ca3c6f2318aafd5c1e59a011b5369ee1c |
|
15-Oct-2010 |
Hung-Te Lin <hungte@chromium.org> |
tag_image.sh: support more tags To extend the usage of tag_image, added --forget_usernames and --leave_core. Output is also refined to clarify the category of each tag parameters. BUG=none TEST=./tag_image.sh --from $PATH_TO_IMAGE; leave_core seems working fine. Change-Id: I7c6517bc98af260411518c743093ade3124b76b9 Review URL: http://codereview.chromium.org/3796003
/external/vboot_reference/scripts/image_signing/tag_image.sh
|
04c00e19c6fd1d9ad09d2bf5e06518c249d62b31 |
|
30-Sep-2010 |
Hung-Te Lin <hungte@chromium.org> |
Add a utility to tag/stamp image There are several procedures in Chrome OS post-processing before being released: stamping, tagging, mod image for URLs, ... and signing. We need an integrated script to handle all the stamping / tagging. This CL can handle empty tag files like /root/.force_update_firmware or /root/.dev_mode. This CL deprecates http://codereview.chromium.org/3421040 and moved script from crosutils to vboot_reference. In the future we may isolate the non-signing post-processing scripts (set_lsb, tag_image, remove_label, ...) into crosutils. BUG=none TEST=manually: (1) Build a general dev image without firmware updates (default behavior of build_image for x86-generic ToT) (2) Enter chroot and then execute: cd ~/trunk/src/platform/vboot_reference/scripts; ./tag_image.sh \ --from ~/trunk/src/build/images/x86-generic/latest/chromiumos_image.bin Expected: output message: Update Firmware: disabled Developer Mode: Enabled (3) ./tag_image.sh --update_firmware=1 --dev_mode=0 \ --from ~/trunk/src//build/images/x86-generic/latest/chromiumos_image.bin Expected: output message: Update Firmware: disabled => Enabled Developer Mode: Enabled => disabled Manually verify: pushd ../../build/images/x86-generic/latest unpack_partitions.sh chromiumos_image.bin sudo mount -o loop,ro part_3 rootfs ls -l rootfs/root/.force_update_firmware # this file should exist ls -l rootfs/root/.dev_mode # this file should NOT exist (i.e., error) sudo umount rootfs (4) ./tag_image.sh --update_firmware=0 --dev_mod=1 \ --from ~/trunk/src/build/images/x86-generic/latest/chromiumos_image.bin Expected: output message: Update Firmware: Enabled => disabled Developer Mode: disabled => Enabled Manually verify: pushd ../../build/images/x86-generic/latest unpack_partitions.sh chromiumos_image.bin sudo mount -o loop,ro part_3 rootfs ls -l rootfs/root/.force_update_firmware # this file should NOT exist (i.e., error) ls -l rootfs/root/.dev_mode # this file should exist sudo umount rootfs Change-Id: I96af3c7201372bb904426d10cff142467a1fa2e7 Review URL: http://codereview.chromium.org/3604001
/external/vboot_reference/scripts/image_signing/tag_image.sh
|