Microsoft Technology Licensing, LLC

James Gordon Cantwell

Sean Conway Draine

Gregory Darrell Fee

John Joseph Rivard

Izydor Gryko

Stephanie Sweeny Saad

David Kehl Templin

Michael Eng

Svetlozar Emilov Keremidarski

Systems and methods for using private keys in software development that minimizes the risks of the private key being lost or stolen. A strong name consists of the assembly's identity, e.g., its simple text name, version number, and culture information (if provided), plus a public key and a digital signature. It is generated from an assembly file using the corresponding private key. The private/public key pair is persisting in a password-encrypted file using a standard encryption format that can be made available to everyone. The first time any subsystem of the development environment requires use of the private key contained in an encrypted file format, the developer is prompted to provide the password to decrypt the key. The user supplies the password and the public/private key is imported into a non-exportable key container in the local cryptographic store.

Persisting private/public key pairs in password-encrypted files for transportation to local cryptographic store

A system and method that allows developers to debug a component while it is restricted by any arbitrary set of specific permissions, or restricted by an existing permission set associated with a security 'zone.' A security sandbox is mimicked within the development environment so that developers can study how applications perform inside the sandbox. Developers are able create any sandbox and debug inside it, where violating any bound of the artificial sandbox will throw a security exception and drop the user out on the exact line of code which generated the error, as well as provide helpful information about how to correct the error.

Debugging applications under different permissions

Growing community of inventors

Sammamish, WA, United States of America

James Gordon Cantwell