50 likes | 163 Views
This resource delves into the essentials of code authentication, focusing on Microsoft Authenticode. It explains how code is signed using a hash encrypted with a private key from a Certifying Authority, creating a signature block embedded in executable files. It covers the process of code verification when downloaded, including how browsers or client-side applications use tools like WinVerifyTrust to extract and verify signatures against the signed digest. Additionally, it outlines application areas such as .exe, .dll, and .cab files, while highlighting advancements in certification hierarchies and revocation lists.
E N D
COEN 351 E-Commerce Security Code Authentication
Code Authentication • Microsoft Authenticode • Code signed in the usual manner. • Hash of code, encrypted with private key obtained from a Certifying Authority. • Combine hash with certificate in a signature block. • Embed result into the file format of the executable.
Code Authentication • When code is downloaded • Browser / client side application extracts the signature block. • E.g. using WinVerifyTrust on a Windows system. • Uses public key of CA to verify / extract certificate. • Rehashes code and compares with signed digest.
Code Authentication • Authenticode applies to • .cab files • .cat files • .ctl files • .dll files • .exe files • .ocx files
Code Authentication • Later versions • add support for certification hierarchies. • add support for Certificate Trust Lists (CTL) and Certificate Revocation Lists (CRL). • SetReg • Sets registry key values that control the behavior of authenticode.