   C# security thought
  Given:1) .Net code that is strongly signed is extremely difficult to maliciously modify.2) The .Net runtime knows the security zone (local, intranet and Internet) that managed code is operating in and resticts the codes access priviledges accordingly. Would it be a far strech for MS to one day decide that unmanaged executables are a high security risk? Possible requiring administrative privildeges to install and/or alter.  
  I''ll bet that if you run a un-managed application on Longhorn, it''ll give you a warning message before running (''This application is unsafe''), which doesn''t sound too professional. Just a thought ;  I''m pretty sure that is what I read as well.  Longhorn will have a security level setting much like Internet Explorer.  The default will be set to very secure so that a message pops up when you run unmanaged code.  You can turn the level down, but of course you have to know to do that. ;  I think it''s pretty early to speculate on what Longhorn will be doing in the final release.   I like pie. ;quote:Original post by eagleone  The .Net runtime knows the security zone (local, intranet and Internet) that managed code is operating in and resticts the codes access priviledges accordingly.Considering what a great job Microsoft has done with this concept in Internet Explorer, that should work out just fine. Restricting applications to managed code is probably what Microsoft have in mind for the not-too-distant future (not necessarily Longhorn). Maybe they think it''ll allow them to better enforce licensing for their products. Or perhaps they really are stupid enough to think that it would have any security benefits for end users. ;quote:Original post by eagleone  Would it be a far strech for MS to one day decide that unmanaged executables are a high security risk? Possible requiring administrative privildeges to install and/or alter.    news flash: unmanaged executables are a high security risk