Crash after obfuscation : Security Rules Violated.

.NET obfuscator and automated error reporting

Crash after obfuscation : Security Rules Violated.

Postby UsherNet » Thu Sep 29, 2011 2:00 am

I experience an issue after running SA6, the exe works before the obfuscation. Anyone any ideas?

Inheritance security rules violated while overriding member: 'SmartAssembly.SmartExceptionsCore.SmartStackFrame.GetObjectData(System.Runtime.Serialization.SerializationInfo, System.Runtime.Serialization.StreamingContext)'. Security accessibility of the overriding method must match the security accessibility of the method being overriden.


Posts: 4
Joined: Thu Mar 31, 2011 6:16 am

Postby Brian Donahue » Thu Sep 29, 2011 4:51 pm

Hi Paul,

I can't be 100% sure, but it sounds again like that problem you have when you used .NET 2 code access policy and tried to run it in .NET 4. There probably needs to be a SecurityTransparent attribute removed from some method. Have you got a stack trace leading up to this error?
Brian Donahue
Posts: 6590
Joined: Mon Aug 23, 2004 9:48 am

Postby nkilian » Tue Nov 08, 2011 12:15 pm

I am experiencing this same problem after upgrading an application to .NET 4.0. It runs fine before obfuscation, but in the obfuscated executable a TypeLoaderException is thrown with a SecurityException as the inner.

Decoded stack trace is:

at SmartAssembly.SmartExceptionsCore.StackFrameHelper.CreateExceptionN(Exception , Object[] )
at SmartAssembly.SmartExceptionsCore.StackFrameHelper.CreateException4(Exception , Object , Object , Object , Object )
at SmartAssembly.StringsEncoding.Strings..cctor()

Occurs with or without string encoding enabled.

Fake Edit:

Adding the following attribute to the Assembly resolved the issue:
<Assembly: System.Security.SecurityRules(System.Security.SecurityRuleSet.Level1)>
Posts: 11
Joined: Thu Dec 10, 2009 10:43 am
Location: South Africa

Return to SmartAssembly 6

Who is online

Users browsing this forum: No registered users and 0 guests