Create bootstub signing utility.

Create bootstub signing utility.

This tool uses cbootimage to sign a bootstub firmware image.  
This makes calling cbootimage from a number of scripts easier.

BUG=chromium-os:11981
TEST=run cros_sign_bootstub and sign a recovery image and write it
to a board using cros_write_firmware which hasn't been submitted yet.

Change-Id: I4b3a9c763d0659d0244eb4d6ed2f0a38154d00c4

This CL depends on: http://codereview.chromium.org/6591056/

Committed: http://chrome-svn/viewvc/chromeos?view=rev&revision=4a9554c

[vb, 2011-02-28 23:54:44]

LGTM

with a few nits to your discretion.

In the CL description:

s/This is makes/This makes/

http://codereview.chromium.org/6592053/diff/1/host/cros_sign_bootstub
File host/cros_sign_bootstub (right):

http://codereview.chromium.org/6592053/diff/1/host/cros_sign_bootstub#newcode77
host/cros_sign_bootstub:77: mkdir -p "${FLAGS_config}"
It would be cleaner to remove the directory on exit if it did not exist on
entry.

OTOH it would be good to be able to request to keep the config file.

[robotboy, 2011-03-01 00:03:40]

http://codereview.chromium.org/6592053/diff/1/host/cros_sign_bootstub
File host/cros_sign_bootstub (right):

http://codereview.chromium.org/6592053/diff/1/host/cros_sign_bootstub#newcode77
host/cros_sign_bootstub:77: mkdir -p "${FLAGS_config}"
On 2011/02/28 23:54:44, vb wrote:
> It would be cleaner to remove the directory on exit if it did not exist on
> entry.
> 
> OTOH it would be good to be able to request to keep the config file.

Yup, the intent here is that if you don't specify anything on the command line
(no --config option) then the config is generated in a /tmp/tmp.XXXXXXX
directory and cleaned up after the run.  If you do pass a --config option on the
command line then the config file is retained in that directory.

[Che-Liang Chiou, 2011-03-01 01:36:30]

LGTM.

On 2011/03/01 00:03:40, robotboy wrote:
> http://codereview.chromium.org/6592053/diff/1/host/cros_sign_bootstub
> File host/cros_sign_bootstub (right):
> 
>
http://codereview.chromium.org/6592053/diff/1/host/cros_sign_bootstub#newcode77
> host/cros_sign_bootstub:77: mkdir -p "${FLAGS_config}"
> On 2011/02/28 23:54:44, vb wrote:
> > It would be cleaner to remove the directory on exit if it did not exist on
> > entry.
> > 
> > OTOH it would be good to be able to request to keep the config file.
> 
> Yup, the intent here is that if you don't specify anything on the command line
> (no --config option) then the config is generated in a /tmp/tmp.XXXXXXX
> directory and cleaned up after the run.  If you do pass a --config option on
the
> command line then the config file is retained in that directory.