- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
"Intel SGX SDK for Windows v2.5.101.3.exe": Tuesday, November 12, 2019 1:13:24 AM
"Intel SGX PSW for Windows v2.5.101.3.exe": Tuesday, November 12, 2019 1:13:08 AM
"Intel SGX DCAP for Windows v1.3.101.3.exe": Tuesday, November 12, 2019 1:12:52 AM
All of these files were signed with the timestamps above. The EV code signing certificate used to sign them expired on Saturday, October 26, 2019 5:59:59 PM.
Could Intel please perhaps update the code signing certificate, and re-sign them (or re-build them) with the updated certificate? I don't know how Windows does its Authenticode process (if it checks the binary's signature before or after it checks the validity of the timestamp versus the certificate chain or the validity of the certificate chain in the first place), so I can't particularly trust the binaries I just downloaded.
Thanks for your time!
-Kyle H
- Tags:
- General Support
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot for point out the expired cert issue. We will fix it in next release(2.6), it will be available in this month.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks a lot for point out the expired cert issue. We will fix it in next release(2.6), it will be available in this month.
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page