> Curious.... say that each method checked a class-wide global > variable to see if it could run. Now, this global variable > would be set to true, if the user had successfully > authenticated himself. > > Even with ILDasm, there wouldn't be anyway to change the > value of the variable at all, as long as the assembly was > signed with a strong name key, correct? Would this provide > enough protection? I'm sure the other ways mentioned are > better, but I'm just curious if this would work, or is it > still "hackable" by changing the MSIL?
mscorlib is strongly named, yet you can "hack" it without resorting to MSIL; reflection is an amazing tool. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
