summaryrefslogtreecommitdiff
path: root/utility/include
diff options
context:
space:
mode:
authorGaurav Shah <gauravsh@chromium.org>2010-06-08 00:16:35 -0700
committerGaurav Shah <gauravsh@chromium.org>2010-06-08 00:16:35 -0700
commit51734261006c8fc611b6efe6f74788b4065500ed (patch)
treee072a1d24aa816651fdc5884bd06f4ea1611dc4a /utility/include
parenta319ac9c33484381c9b6997389cfcd225a47035e (diff)
downloadvboot-51734261006c8fc611b6efe6f74788b4065500ed.tar.gz
Add option to specify a kernel subkey signing key to firmware signing utility.
If no kernel subkey signing key is specified, it reuses the firmware signing key. Review URL: http://codereview.chromium.org/2696003
Diffstat (limited to 'utility/include')
-rw-r--r--utility/include/firmware_utility.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/utility/include/firmware_utility.h b/utility/include/firmware_utility.h
index 663536a2..27c154fa 100644
--- a/utility/include/firmware_utility.h
+++ b/utility/include/firmware_utility.h
@@ -59,9 +59,11 @@ class FirmwareUtility {
std::string subkey_in_file_; // Existing key signature header.
std::string in_file_;
std::string out_file_;
+ std::string kernel_subkey_sign_pub_file_;
int firmware_key_version_;
int firmware_sign_algorithm_;
int firmware_version_;
+ int kernel_subkey_sign_algorithm_;
bool is_generate_; // Are we generating a new image?
bool is_verify_; // Are we just verifying an already signed image?
bool is_describe_; // Should we print out description of the image?