holly-hacker / Confuser.Protections.HoLLy

Extra protection modules for ConfuserEx
GNU General Public License v3.0
66 stars 21 forks source link

Please leave it compatible with ConfuserEx #8

Closed MrakDev closed 6 years ago

MrakDev commented 6 years ago

I'm having trouble injecting your protections into Confuser. I wonder if it's possible, you do something compatible, or help me. Thank you

holly-hacker commented 6 years ago

If you can tell me the actual problem, sure.

MrakDev commented 6 years ago

The source code not is compatible, ex: you use public override string Name => "Memory Protection analysis"; === NO COMPATIBLE

corret: public override string Name = "Memory Protection analysis";

several others too. if at all I can not compile their protections together with the KI ConfuserEx

holly-hacker commented 6 years ago

You should update your Visual Studio to 2017, these are C# 7 features.

For more information on expression bodies, see here: https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/statements-expressions-operators/expression-bodied-members

MrakDev commented 6 years ago

Serius I love you m8 thank you. I'll test and tell you the results.

MrakDev commented 6 years ago

Okay, now c# is talking "is inaccessible due to its protection level" image

holly-hacker commented 6 years ago

That is strange, because I set an assembly attribute to show the internals of the Runtime assembly to the main assembly. Make sure that this line is present in your copy of the source.

Proof that it does work for me: pic

You can always download the latest source from AppVeyor, and decompile it with dnSpy if you need to edit something.

MrakDev commented 6 years ago

i already hnow, i change type of ObfuscatedValue image For image now gave to compile, but when I go to obfs the .exe gives an error.

MrakDev commented 6 years ago

I do not really know what to do, I've tried everything, use the appVeyor dll to compile the dll and use it in confuser, try to get the src of the dll in dnspy, solve the problems by VS :(

holly-hacker commented 6 years ago

ObfuscatedValue is meant to be internal, making it public is just a workaround but if it works for you I guess that's fine.

So what exactly is the issue now? Not being able to run a module protected with this? Keep in mind that this is still a work-in-progress, and please be specific with what the issue is.

MrakDev commented 6 years ago

Could you compile the entire project? in appVeyor?, type with all confuser config https://github.com/yck1509/ConfuserEx

MrakDev commented 6 years ago

the only thing I need is memory protection :/

holly-hacker commented 6 years ago

If all you need is memory protection, annotate a property with the following attribute:

[Obfuscation(Exclude = false, Feature = "memory protection")]

Note that this only works on primitive types such as int (and family), float + double, string and enum.

MrakDev commented 6 years ago

I did not understand (sorry for being annoying)

holly-hacker commented 6 years ago

Before protection, it will look like this:

    private static int _normal = 100;

    [Obfuscation(Exclude = false, Feature = "memory protection")]
    private static int _special = 100;

And after protection, it will look like this:

    private static int _normal = 100;

    private static \u206E\u200E\u200E(...)\u206A\u202E<int> _special = 100;
MrakDev commented 6 years ago

Do you have any social networks? ex skype you know I need something to protect the string inside the memory. to prevent from memory editor like cheat engine

holly-hacker commented 6 years ago

I just explained it to you. If it still isn't clear, perhaps you should use more mature software than this, which may have more clear (or any) documentation.