.NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

.NET Framework 3.5 SP1 Allows managed code to be launched from network

DotNetKicks.com — Thu, 14 Aug 2008 02:15:36 GMT

You've been kicked (a good thing) - Trackback from DotNetKicks.com

re: .NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

MichaelGG — Thu, 14 Aug 2008 09:15:24 GMT

I agree with the rationale - as long as people can go running unmanaged code willy nilly.

But that makes me wonder: What's different in the security analysis in 2008 than it was in 2001 or so (why wasn't it like this since 1.0/1.1/2.0...)?

.NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

Brad Abrams — Thu, 14 Aug 2008 09:18:28 GMT

This has got to be one of the most consistently asked for "features" of .NET from the start!    

Link Listing - August 13, 2008

Christopher Steen — Thu, 14 Aug 2008 09:53:32 GMT

Link Listing - August 13, 2008

Christopher Steen — Thu, 14 Aug 2008 09:53:56 GMT

WPF dabbling around the new WPF datagrid (part 1) [Via: jaimer ] Code Camps Southwest Florida Code...

My .NET Application Runs

Infosys | Microsoft — Thu, 14 Aug 2008 11:14:47 GMT

.NET applications now run off network path

[.NET FX SP1] Eseguire codice unmanaged da uno share di rete

Corrado's BLogs — Thu, 14 Aug 2008 12:49:28 GMT

[.NET FX SP1] Eseguire codice unmanaged da uno share di rete

Visual Studio 2008 Service Pack

Khurram Aziz — Thu, 14 Aug 2008 13:54:07 GMT

Soma announced the availability of Visual Studio 2008 Service Pack 1 and .NET 3.5 Service Pack 1 . Installation

Visual Studio 2008 SP1 and .NET Framework 3.5 SP1 enhancements

STEFANO DEMILIANI — Thu, 14 Aug 2008 15:54:54 GMT

Visual Studio 2008 SP1 and .NET Framework 3.5 SP1 enhancements

Executables .NET depuis un partage réseau : le SP1 de .NET 3.5 apporte bien la solution annoncée

CoqBlog — Thu, 14 Aug 2008 16:37:07 GMT

Ca se confirme, c'est dans le SP1 de .NET 3.5 qui a été publié cette semaine : si lancées directement

.NET Framework 3.5 SP1 consente l'esecuzione di codice unmanaged da una share di rete

DevAdmin Blog — Thu, 14 Aug 2008 17:01:29 GMT

.NET Framework 3.5 SP1 consente l'esecuzione di codice unmanaged da una share di rete

re: .NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

darrenkopp — Thu, 14 Aug 2008 18:03:39 GMT

can i give you a hug? i'm so happy right now i just don't know what to do.

re: .NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

vancem — Thu, 14 Aug 2008 20:05:44 GMT

To answer the question: what is differnet now than when we shipped that promped the change?

The simple answer is that we made a mistake. In 2001 we believed we are the avant-guard in making things 'secure by default' and thus biased our decisions believing that we would eventually 'plug' the hole of unmanaged code running from a network share. We also did not appreciate the pain this decision would cause.

However over time, we realized that we were naive. The cost/benefit of changing the behavior of unmanaged code is simply too high. Moreover it also become clear that for security to work, it must be simple, which means treating cases uniformly. Thus if you want to disallow launching exes off the network you should not have one way of doing it for managed code, and a completely different way for unmanage code.

In fact there IS a way of locking down exe launch uniformly (see Security Policies above), so really it became abundantly clear that really the 'right' approach is to treat security wholisitically (not just the managed case) and make managed code and unmanaged code as simmilar as possible (after all from an end user's perspective, who cares if code is managed or not?)

So to sum up, we made a mistake (frankly we make lots of them), and sadly it is VERY difficult to fix mistakes when you have millions of users to break, and even more so when security is involved. Thankfully, in this case we were able to convince ourselves that we could fix this one after the fact.

Vance (.NET Runtime Architect)

re: .NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

JWilcox — Fri, 15 Aug 2008 09:03:57 GMT

Awesome!!! Thanks a TON for pushing for this Vance, I can't wait to start using it!

re: .NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

robbie@thepawnshopper.com — Fri, 15 Aug 2008 15:29:13 GMT

Thank you. This makes things much easier.

Launch .NET apps from network share

Marius Gheorghe — Thu, 21 Aug 2008 11:49:15 GMT

Launch .NET apps from network share

.NET Framework 3.5 SP1 Changes

Nuno Filipe Godinho — Thu, 28 Aug 2008 02:38:56 GMT

   With the release of the new Service Pack 1 for the .NET Framework 3.5 several changes were

.NET Framework 3.5 SP1 Changes

Nuno Filipe Godinho — Thu, 28 Aug 2008 02:39:15 GMT

   With the release of the new Service Pack 1 for the .NET Framework 3.5 several changes were

.NET Framework 3.5 SP1允许从网络共享中调用托管代码了！

Joycode@Ab110.com — Sun, 07 Sep 2008 18:38:26 GMT

【原文地址】 .NET Framework 3.5 SP1 Allows managed code to be launched from a network share! 【原文发表日期】 13 August

re: .NET Framework 3.5 SP1 Allows managed code to be launched from a network share!

Subli — Mon, 16 Feb 2009 09:21:13 GMT

This change WAS acceptable if you kept the default behaviour intact and simply added the evidence of MyComputer to the network launched application by setting a registry key something like "ExpandMyComputerZone" to 1.

How come can't you imagine changing default behaviour of run-time causes huge problems? It looks like all of sudden you began following any demand of republican and didn't give an inch to GOP, though Redmond has been for republican, as long as I know.

I sincerely want a word from you,

Thanks,