Methods for firmware signature
A method for installing embedded firmware is provided. The method includes generating one or more firmware file instances and generating one or more digital certificate instances that are separate instances from the firmware file instances. The method includes associating the one or more digital certificate instances with the one or more firmware file instances to facilitate updating signature-unaware modules with signature-aware firmware or to facilitate updating signature-aware modules with signature-unaware firmware.
1. A method, comprising:
receiving, by a first device, signature unaware firmware code;
installing, by the first device via boot code, the signature unaware firmware code on the first device, wherein the boot code is configured for installation of a signature aware firmware code and the signature unaware firmware code to the first device, wherein the installing the signature unaware firmware code further comprises verifying, via at least one feedback mechanism, that the signature unaware firmware code is received from a second device associated with a user that has physical access to the first device.
2. The method of claim 1 , wherein the installing the signature unaware firmware code further comprises verifying that the signature unaware firmware code is received from a proxy module located remotely from the first device, where the proxy module has verified the signature unaware firmware code.
3. The method of claim 1 , wherein the installing the signature unaware firmware code further comprises receiving from a proxy module that intercepted a request to install the signature unaware firmware code on the first device, a signed certificate comprising a signature generated by the proxy module.
4. The method of claim 3 , wherein the installing the signature unaware firmware code further comprises:
determining whether the certificate is valid by verifying that the signature of the signed certificate is valid;
in response to the certificate being valid, loading the signature unaware firmware code on the first device; and
in response to the certificate being invalid, preventing installation of the signature unaware firmware code on the first device.
5. The method of claim 4 , wherein the determining whether the certificate is valid further comprises verifying that the signature unaware firmware code is valid for the certificate.
6. A non-transitory computer-readable medium having instructions stored thereon that, in response to execution, cause a first device to perform operations comprising:
receiving signature unaware firmware code;
installing, via boot code, the signature unaware firmware code on the first device, wherein the boot code is configure for installation of a signature aware firmware code and the signature unaware firmware code to the first device, wherein the installing the signature unaware firmware code further comprises verifying, via at least one feedback mechanism, that the signature unaware firmware code is received from a second device associated with a user that has physical access to the first device.
7. The non-transitory computer-readable medium of claim 6 , wherein the installing the signature unaware firmware code further comprises verifying, via the boot code, that the signature unaware firmware code is received from a proxy module located remotely from the first device, where the proxy module has verified the signature unaware firmware code.
8. The non-transitory computer-readable medium of claim 6 , wherein the installing the signature unaware firmware code further comprises receiving from a proxy module that intercepted a request to install the signature unaware firmware code on the first device, a signed certificate comprising a signature generated by the proxy module.
9. The non-transitory computer-readable medium of claim 8 , wherein the installing the signature unaware firmware code further comprises:
determining whether the certificate is valid by verifying that the signature of the signed certificate is valid;
in response to the certificate being valid, loading the signature unaware firmware code on the first device; and
in response to the certificate being invalid, preventing installation of the signature unaware firmware code on the first device.
10. The non-transitory computer-readable medium of claim 9 , wherein the determining whether the certificate is valid further comprises verifying that the signature unaware firmware code is valid for the certificate.
11. A system, comprising:
a first device configured to receive signature unaware firmware code;
a boot code installed on the first device configured to install the signature unaware firmware code on the first device, wherein the boot code is configured for installation of a signature aware firmware code and the signature unaware firmware code on the first device, wherein the boot code, prior to installing the signature unaware firmware code, verifies, via at least one feedback mechanism, that the signature unaware firmware code is received from a second device associated with a user that has physical access to the first device.
12. The system of claim 11 , wherein the boot code, prior to installing the signature unaware firmware code, verifies that the signature unaware firmware code is received from a proxy module located remotely from the first device, where the proxy module has verified the signature unaware firmware code.
13. The system of claim 11 , wherein the boot code, prior to installing the signature unaware firmware code, receives from a proxy module that intercepted a request to install the signature unaware firmware code on the first device, a signed certificate comprising a signature generated by the proxy module.
14. The system of claim 13 , wherein the boot code, prior to installing the signature unaware firmware code:
determines whether the certificate is valid by verifying that the signature of the signed certificate is valid;
in response to the certificate being valid, loads the signature unaware firmware code on the first device; and
in response to the certificate being invalid, prevents installation of the signature unaware firmware code on the first device.