June, 2006

  • .NET Security Blog

    Reducing Startup Time Due To Strong Name Verification

    • 6 Comments
    Occasionally we run into a scenario where someone asks about shipping a strong name skip verification entry for their assembly with their product. Generally, their reasoning is that the performance hit of strong name verification is too great for their...
  • .NET Security Blog

    Special Permissions in the SSCLI

    • 2 Comments
    Before digging into a pretty clever optimization that the SSCLI makes for certain special permission demands, I want to point out that everything I’m about to cover is an implementation detail. Although this optimization does occur today, we can and will...
  • .NET Security Blog

    Browsing the SSCLI in Visual Studio

    • 9 Comments
    I've attached a simple Visual Studio 2005 project that I use for browsing the SSCLI v2 source tree . (Once you've downloaded it, rename the file to remove the .txt extension). The project is good for browsing, however it will not build or debug the SSCLI...
  • .NET Security Blog

    APTCA and SQL Server 2005

    • 1 Comments
    Last year, I explored the ins and outs of the AllowPartiallyTrustedCallersAttribute . Today, the SQL-CLR blog takes a look at how APTCA affects assemblies hosted in SQL Server 2005 databases -- recommended reading for those dealing with strong names and...
  • .NET Security Blog

    CLR Inside Out: Using Strong Name Signatures

    • 2 Comments
    Mike Downen , our CLR security PM, wrote the CLR Inside Out column this month in MSDN Magazine on strong name signatures. He covers what strong name signatures are, what they're good for, what they're not good for, delay signing, and test signing. I just...
  • .NET Security Blog

    Avoiding Deny and Permit Only: Take 2

    • 2 Comments
    Last week when I dug into the details of the special permission optimization , we saw in the code that before the CLR can use this optimized form of a demand, it needs to check to ensure there are no Deny or PermitOnly modifiers on the call stack. I noted...
Page 1 of 1 (6 items)