[GH-ISSUE #619] Methods renaming #374

New issue

Closed

opened 2026-02-27 15:50:05 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 15:50:05 +03:00

Owner

Originally created by @Powershell-coder on GitHub (Sep 13, 2017).
Original GitHub issue: https://github.com/quasar/Quasar/issues/619

Hi
I want to extend renamer.cs and rename all methods.
But may be there is some methods which renamed, client may crash or doesnt work correctly
Which methods MUST not be renamed ?

Originally created by @Powershell-coder on GitHub (Sep 13, 2017). Original GitHub issue: https://github.com/quasar/Quasar/issues/619 Hi I want to extend renamer.cs and rename all methods. But may be there is some methods which renamed, client may crash or doesnt work correctly Which methods MUST not be renamed ?

kerem

2026-02-27 15:50:05 +03:00

closed this issue
added the
question
label

kerem commented

2026-02-27 15:50:06 +03:00

Author

Owner

@life-coder commented on GitHub (Sep 15, 2017):

You can rename every method. Just be sure to rename all the references too

@life-coder commented on GitHub (Sep 15, 2017): You can rename every method. Just be sure to rename all the references too

kerem commented

2026-02-27 15:50:06 +03:00

Author

Owner

@yankejustin commented on GitHub (Sep 15, 2017):

It doesn't matter if you change the method names. You would only experience issues if you began to restructure the code (changing the namespace of certain classes mainly).

You can see the namespaces that dislike being renamed here.

@yankejustin commented on GitHub (Sep 15, 2017): It doesn't matter if you change the method names. You would only experience issues if you began to restructure the code (changing the namespace of certain classes mainly). You can see the namespaces that dislike being renamed [here](https://github.com/quasar/QuasarRAT/blob/64cb0e5f837954be59b484b42744661805b0a837/Server/Core/Build/Renamer.cs#L59-#L61).

kerem commented

2026-02-27 15:50:06 +03:00

Author

Owner

@Powershell-coder commented on GitHub (Sep 17, 2017):

Yes
But i want to obfuscate the code with some obfuscators like .Net Reactor.

Its is needed NOT ot obfuscate some parts of code because if obfuscate all Client doesnt work.

            if (typeDef.Namespace.Contains("NetSerializer") 
                || typeDef.Namespace.Contains("Registry") || typeDef.HasInterfaces)
                return;

Based on this only NetSerializer and Registry and typeDef.HasInterfaces can not be obfuscated.

Is it true ?

And what about Build option in Server. Does renaming has side effect on it and Must rename somthing in server ?

@Powershell-coder commented on GitHub (Sep 17, 2017): Yes But i want to obfuscate the code with some obfuscators like .Net Reactor. Its is needed NOT ot obfuscate some parts of code because if obfuscate all Client doesnt work. ``` if (typeDef.Namespace.Contains("NetSerializer") || typeDef.Namespace.Contains("Registry") || typeDef.HasInterfaces) return; ``` Based on this only NetSerializer and Registry and typeDef.HasInterfaces can not be obfuscated. Is it true ? And what about Build option in Server. Does renaming has side effect on it and Must rename somthing in server ?

kerem commented

2026-02-27 15:50:06 +03:00

Author

Owner

@MaxXor commented on GitHub (Oct 9, 2017):

@EhsanArio Yes, classes from NetSerializer & Registry namespace and classes with interfaces can not be renamed. It does have no negative side effects.

@MaxXor commented on GitHub (Oct 9, 2017): @EhsanArio Yes, classes from NetSerializer & Registry namespace and classes with interfaces can not be renamed. It does have no negative side effects.