|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Running .NET exe from a network shareHello all,
We have an application here which we are migrating from WIN32/C++ to .NET This tool can be used by our client and launch from a network share : The user install it on one server and any workstation can run the tool by \\SERVER\Tools\Tools.exe When dealing with .NET, it seems there is some security which forbid by default to run a .NET exe from a network share. What is the solution and which action must be done on workstation by our client to be able to run this .NET exe from the server share ? Best regards, Frédéric Hi,
what you encountered is a Code Security issue and you have to deal with the Runtime Configuration of your System and Code. It is called "Code Access Security". Read this for more Information: [.NET Framework Developer's Guide Code Access Security] http://msdn.microsoft.com/en-us/library/930b76w0.aspx [.NET Framework Security Chapter 8 - Code Access Security in Practice] http://msdn.microsoft.com/en-us/library/aa302424.aspx [Understanding .NET Code Access Security] http://www.codeproject.com/KB/security/UB_CAS_NET.aspx [Code Access Security (CAS) and Design Patterns] http://www.codeproject.com/KB/architecture/CASDesignPatterns.aspx [Code Access Security] http://en.wikipedia.org/wiki/Code_Access_Security [Configuring .NET Code Access Security] http://www.15seconds.com/Issue/040121.htm Good Luck! regards Kerem -- Show quoteHide quote-- ----------------------- Beste Grüsse / Best regards / Votre bien devoue Kerem Gümrükcü Latest Project: http://www.pro-it-education.de/software/deviceremover Latest Open-Source Projects: http://entwicklung.junetz.de ----------------------- "This reply is provided as is, without warranty express or implied." "Frederic Forjan" <frederic.forjan@newsgroup.nospam> schrieb im Newsbeitrag news:#cInXGX9JHA.2120@TK2MSFTNGP02.phx.gbl... > Hello all, > > We have an application here which we are migrating from WIN32/C++ to .NET > This tool can be used by our client and launch from a network share : > The user install it on one server and any workstation can run the tool by > \\SERVER\Tools\Tools.exe > > When dealing with .NET, it seems there is some security which forbid by > default to run a .NET exe from a network share. > What is the solution and which action must be done on workstation by our > client to be able to run this .NET exe from the server share ? > > Best regards, > Frédéric Thanks for all these links, very very interesting :-)
My conclusion, is that an action MUST be done on any computer wanted to access and run this executable from the network share. (There is different way to achieve this action, manually or automatically depending on our solution...) Thanks again, Frédéric Kerem Gümrükcü a écrit : Show quoteHide quote > Hi, > > what you encountered is a Code Security > issue and you have to deal with the Runtime > Configuration of your System and Code. It is > called "Code Access Security". Read this for > more Information: > > > [.NET Framework Developer's Guide > Code Access Security] > http://msdn.microsoft.com/en-us/library/930b76w0.aspx > > [.NET Framework Security > Chapter 8 - Code Access Security in Practice] > http://msdn.microsoft.com/en-us/library/aa302424.aspx > > [Understanding .NET Code Access Security] > http://www.codeproject.com/KB/security/UB_CAS_NET.aspx > > [Code Access Security (CAS) and Design Patterns] > http://www.codeproject.com/KB/architecture/CASDesignPatterns.aspx > > [Code Access Security] > http://en.wikipedia.org/wiki/Code_Access_Security > > [Configuring .NET Code Access Security] > http://www.15seconds.com/Issue/040121.htm > > Good Luck! > > > regards > > Kerem > Hi,
this behavior has been changed with .NET 2.0 SP2. Once installed, you can launch programs from a network share like you can from a local harddrive. Kind regards, Henning Krause Show quoteHide quote "Frederic Forjan" <frederic.forjan@newsgroup.nospam> wrote in message news:OZurOcj9JHA.3244@TK2MSFTNGP03.phx.gbl... > Thanks for all these links, very very interesting :-) > > My conclusion, is that an action MUST be done on any computer wanted to > access and run this executable from the network share. > (There is different way to achieve this action, manually or automatically > depending on our solution...) > > Thanks again, > Frédéric > > Kerem Gümrükcü a écrit : >> Hi, >> >> what you encountered is a Code Security >> issue and you have to deal with the Runtime >> Configuration of your System and Code. It is >> called "Code Access Security". Read this for >> more Information: >> >> >> [.NET Framework Developer's Guide >> Code Access Security] >> http://msdn.microsoft.com/en-us/library/930b76w0.aspx >> >> [.NET Framework Security >> Chapter 8 - Code Access Security in Practice] >> http://msdn.microsoft.com/en-us/library/aa302424.aspx >> >> [Understanding .NET Code Access Security] >> http://www.codeproject.com/KB/security/UB_CAS_NET.aspx >> >> [Code Access Security (CAS) and Design Patterns] >> http://www.codeproject.com/KB/architecture/CASDesignPatterns.aspx >> >> [Code Access Security] >> http://en.wikipedia.org/wiki/Code_Access_Security >> >> [Configuring .NET Code Access Security] >> http://www.15seconds.com/Issue/040121.htm >> >> Good Luck! >> >> >> regards >> >> Kerem >>
XmlDSig trouble
ComputeSignature: The Keyset is not defined .NET Security Failed to access IIS metabase Empty Event Logs from Windows 2003 Server,Win32_NTLogEvent,WMI SslStream and AES 128 cipher Form authentication MD5CryptoServiceProvider tied to machine? Firewall Error Messgae RE: .NET CLR Error 800700002 |
|||||||||||||||||||||||