Add support for tarball contents signature
Currently only supported to allow optional image files in BMC tarball.
In order to ensure that the contents of the tarball are the expected
ones as a full package, an additional signature file has been created
for all the signature files in the tarball,
(ex: image-full.sig = hash(file1.sig + file2.sig + file3.sig...)).
Need to check the existence of the file and the signature verification
passed.
Also, added unit test case for the mergeFiles method.
Tested:
Enable `WANT_SIGNATURE_FULL_VERIFY` and ran the following command:
curl -k -H "X-Auth-Token: $token" -H "Content-Type: application/octet-stream"
-X POST -T obmc-phosphor-image-fp5280g2.static.mtd.tar
https://${bmc}/redfish/v1/UpdateService
{
"@odata.id": "/redfish/v1/TaskService/Tasks/1",
"@odata.type": "#Task.v1_4_3.Task",
"Id": "1",
"TaskState": "Running",
"TaskStatus": "OK"
}
And Log output:
`Successfully completed Signature vaildation.`
Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: I0e658b9dd90ea405a9c8292f29183ab516a0fa31
diff --git a/image_verify.hpp b/image_verify.hpp
index 02e1093..a995e5a 100644
--- a/image_verify.hpp
+++ b/image_verify.hpp
@@ -199,6 +199,13 @@
*/
CustomMap mapFile(const fs::path& path, size_t size);
+ /**
+ * @brief Verify the full file signature using public key and hash function
+ *
+ * @return true if signature verification was successful, false if not
+ */
+ bool verifyFullImage();
+
/** @brief Directory where software images are placed*/
fs::path imageDirPath;