[x86] (6) Secure WMI based on SSL Handshaking Between Application and Embedded Controller

Easy and simple topic just explains all. If one would like to make sure certain WMI (usually OEM customized ones, related to EC maybe and 95% of them are trouble makers of system performance!) to be secured without being used by other applications, the following method is considerable.

The idea is simple, application must handshake with EC through SSL to prove it's identity to gain permission to use certain WMI, otherwise the EC will block the request or even shut the system down shown as below.

Great! I believe you got the idea, if you're not, you may do a little study of SSL as well since it's open standard drafted by legendary Netscape. Following is the detailed flow of handshaking, note that only after the handshaking is done, the security of transmission between application and EC is ensured. The blue square "AES Secured" indicates it.

Once the handshake is done, other flow is just determined by OEM/ EC policy which is pretty trivial, crazy PM and annoying supervisors just love it.

Here's detailed flow how the secure transmission between application and EC, they're extremely trivial if you do take a look on SSL standard...not for lazy bones!

This method is not perfect but simply convincing since it's built on the giant's shoulder...

Any questions, suggestions or comments, please let me know, thanks a lot!