Microsoft Technology Licensing, LLC

Arun Moorthy

Raja Krishnaswamy

Christopher Wellington Brumme

Jonathan C Hawkins

Charles W Kaufman

Shawn Farkas

Michael D Downen

Reid Borsuk

Mueez Siddiqui

Andrew Dai

The present invention extends to methods, systems, and computer program products for updating signature algorithms used for signing an assembly with a strong name without changing the identity of the assembly. The present invention enables an assembly that has already been given an identity (via strong name signing with an identity public/private key pair) to be resigned with a different public/private key pair without changing the original identity that was based on the identity public/private key pair. This is accomplished by including a counter signature within the assembly that links the original identity of the assembly to the new signature key pair.

Updating signature algorithms for strong name binding

Performing security sensitive operations with an application security model. Security agnostic code is executed. The security agnostic code is identified as not having authorization to perform a security sensitive operation. Executing the security agnostic code includes calling code identified as security safe critical code. In response to the security agnostic code calling the security safe critical code, the security safe critical code is executed. The security safe critical code includes functionality for performing validity checks. Executing the security safe critical code includes performing an validity check for the security agnostic code. When the security agnostic code passes the validity check, code identified as security critical code is called. In response to the security safe critical code calling the security critical code, the security critical code is executed. The security critical code is authorized to perform the security sensitive operation.

Application security model

Described herein is an implementation for exposing an 'execution context' to a logical execution flow of procedures as it executes. An 'execution context' is a set of data and/or sub-procedures that might be useful at some point during a logical execution flow (to manage and control the execution flow and provide additional services to the execution flow) of computer-executable instructions though the often complex, intertwined, and interconnected conglomeration of procedures of software product(s).

Execution context infrastructure

Growing community of inventors

Newcastle, WA, United States of America

Arun Moorthy