CLR 4 Security on Channel 9

A while back I did an interview with Charles Torre  about the changes to security in CLR v4, and he posted it to the Channel 9 videos site yesterday. I start out talking about the security policy changes I’ve been covering here over the last week, and then transition into an overview of some of…

1

Visual Studio 10 Security Tab Changes

Kris Makey, who works on the Visual Studio team, has written up a good blog post about the changes you’ll see on the security tab in Visual Studio 10 when it comes to editing permission sets.  He covers what the changes are, and some of the reasons why we worked with the Visual Studio team…

1

Coding with Security Policy in .NET 4.0 – Implicit uses of CAS policy

Last week we looked at sandboxing and the v4 CLR – with the key change being that the CLR now defers exclusively to the host application when setting up sandboxed domains by moving away from the old CAS policy model, and moving instead to simple sandboxed AppDomains. This leads to an interesting situation when your…

4

Sandboxing in .NET 4.0

Yesterday I talked about the changes in security policy for managed applications, namely that managed applications will run with full trust – the same as native applications – when you execute them directly. That change doesn’t mean that managed code can no longer be sandboxed however – far from it.  Hosts such as ASP.NET and…

7

Security Policy in the v4 CLR

One of the first changes that you might see to security in the v4 CLR is that we’ve overhauled the security policy system.  In previous releases of the .NET Framework, CAS policy applied to all assemblies loaded into an application (except for in simple sandbox domains). That lead to a lot of interesting problems.  For…

13

.NET 4.0 Security

The first beta of the v4.0 .NET Framework is now available, and with it comes a lot of changes to the CLR’s security system.  We’ve updated both the policy and enforcement portions of the runtime in a lot of ways that I’m pretty excited to finally see available.  Since there are a lot of security…

11