Microsoft Technology Licensing, LLC

Jeremy Scott Barton

Morgan Asher Brown

Sam Franklin Williams, Iii

Michael Vandekerkhof

Gabriel Alexandru Ghiondea

Levi P Broderick

Barry Dorrans

Levi Broderick

Techniques are described herein that are capable of providing security for code between a code generator and a compiler. The code generator generates source code. The code generator generates a first checksum of a file that includes the source code. The code generator provides the first checksum to the compiler via a secure channel. The compiler generates a second checksum of the file that includes the source code. The compiler determines whether to compile the source code based at least in part on whether the first checksum and the second checksum are the same. The first checksum and the second checksum being the same indicates that the source code is to be compiled. The first checksum and the second checksum being different indicates that the source code is not to be compiled.

Security of code between code generator and compiler

The authenticity of a compressed archive is verified without decompressing the files and/or directories contained therein and without impeding existing archive reader tools and utilities. A container is produced that includes a signature component and a compressed archive component. The signature component contains a digital signature of the compressed archive and the compressed archive component contains the compressed archive. The signature component and the compressed archive component are constructed as independent components so that existing software tools that operate on a compressed archive can still function in their normal course of operation.

Cryptographic verification of a compressed archive

A determination is made as to whether a user has been logged off from the web-based application accessed through a web browser on a computer. If it is determined that the user has been logged off from the web-based application, then a new user interface is provided through the web browser. The new user interface may enable the user to enter user credentials. The user credentials are received through the new user interface. A request to validate the user based on the user credentials is transmitted. Upon transmitting the request to validate the user, an instruction to remove the new user interface is received when the user is validated. Upon receiving the instruction, a display of the web-based application is transformed by removing the new user interface.

Asynchronous identity establishment through a web-based application

Growing community of inventors

Seattle, WA, United States of America

Jeremy Scott Barton