May, 2007

  • .NET Security Blog

    Silverlight Security II: What Makes a Method Critical

    Yesterday we talked about the CoreCLR security model , and how it is built upon the transparency model introduced in the v2.0 .NET Framework. The quick summary was that all Silverlight application code is transparent, and transparent code may only call...
  • .NET Security Blog

    The Silverlight Security Model

    You may have heard a thing or two last week about a little project we like to call Silverlight , including a small version of the CLR that will run in the browser on both Windows and the Mac. (If you haven't grabbed the Silverlight v1.1 alpha bits yet...
  • .NET Security Blog

    Silverlight Security Cheat Sheet

    Over the last week we took a look at the new Silverlight security model. When you're writing a Silverlight application though, there's a lot of information there that you may not want to wade through to get yourself unblocked. Here's a quick cheat sheet...
  • .NET Security Blog

    Bypassing the Authenticode Signature Check on Startup

    A while back I wrote about the performance penalty of loading an assembly with an Authenticode signature . The CLR will attempt to verify the signature at load time to generate Publisher evidence for the assembly. However, by default most applications...
  • .NET Security Blog

    Silverlight Security III: Inheritance

    Over the last few days we've looked at the basics of the CoreCLR security model in Silverlight , and how to tell which platform APIs are available for applications to call . Let's wrap up this mini-series on CoreCLR security by looking at how the CoreCLR...
Page 1 of 1 (5 items)