That's not a way "around" the security model any more than booting to a DOS disk and running a program is, or installed a device driver.
Sorry to be so blunt, but anyone that downloads an unknown .exe to his/her hard drive and runs it, is a fool. In my more cynical moments, I've occasionally thought it would be extremely useful if there were a rogue .exe/virus that actually did reformat hard drives. It would force evolution of computer users, or at least Darwinian survival policies. <g> -- Brent Rector, .NET Wise Owl Demeanor for .NET - an obfuscation utility http://www.wiseowl.com/Products/Products.aspx -----Original Message----- From: franklin gray [mailto:[EMAIL PROTECTED]] Sent: Friday, May 31, 2002 8:49 AM To: [EMAIL PROTECTED] Subject: Re: [DOTNET] Strongly named assemblies require Full Trust ??? Oh yeah :-) The funny thing is...there is a way around all this stuff. Create an Exe and download it to the machine, then run it. Have that Exe call a Web Service that returns a byte array(s) which is my dll(s) and exe. Then save the array(s) as a file(s) on the harddrive, then kick of the new exe. This will by-pass all that security stuff. So, in a way, the security patch doesn't work....just makes it harder for us to do what we want and puts the pressure on the user to know what he is doing when he runs an Exe that he downloaded. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
