So, simply put, Intel changed the digital signature for the driver to SHA-256 from HAXM 7.2. According to this article, Windows 7 actually requires a patch to enable SHA-256 support, whereas Windows 8 and later supports it by default. However, apparently the new driver signature is not recognized by some Windows systems. So we did that, and tested the new driver against our own Windows 7/8/8.1 systems without noticing any issue. ![]() However, we were advised that SHA-1 algorithm is now considered insecure, and that we should replace it with SHA-256 (a variant of SHA-2). Previously (for HAXM 7.1.0 and earlier), we used a SHA-1 certificate for these Windows versions. ![]() ![]() Here is the relevant comment from the forumįor the HAXM 7.2.0 release, we changed the certificate that we use to sign the Windows 7/8/8.1 driver (IntelHaxm.sys). The problem is actually indirectly related to a missing security update for Windows 7 64 bit.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |