[GH-ISSUE #426] Obfuscation prevents RegistryEditor from working properly #217

Closed
opened 2026-02-27 15:49:23 +03:00 by kerem · 4 comments
Owner

Originally created by @LjungErik on GitHub (Mar 14, 2016).
Original GitHub issue: https://github.com/quasar/Quasar/issues/426

After some research on issue: #425, I have found that the crashes most certainly are caused by the obfuscation that is performed during the build process of the client.

The client-side serializer will in this case generate a representation of the registry that cannot be deserialized on the server, and through this causes a exception to be thrown that disconnects the client.

Originally created by @LjungErik on GitHub (Mar 14, 2016). Original GitHub issue: https://github.com/quasar/Quasar/issues/426 After some research on issue: #425, I have found that the crashes most certainly are caused by the obfuscation that is performed during the build process of the client. The client-side serializer will in this case generate a representation of the registry that cannot be deserialized on the server, and through this causes a exception to be thrown that disconnects the client.
kerem 2026-02-27 15:49:23 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@DragonzMaster commented on GitHub (Mar 14, 2016):

Did you mean the renamer ??
It is not the first time that renamer cause problems in release config.
I remember that the keylogger face such problem and it was solved by excluding (something like that) some of keylogger namespaces so we can try the same with registry editor namespaces but first we have to know which one cause this problem.

<!-- gh-comment-id:196251391 --> @DragonzMaster commented on GitHub (Mar 14, 2016): Did you mean the renamer ?? It is not the first time that renamer cause problems in release config. I remember that the keylogger face such problem and it was solved by excluding (something like that) some of keylogger namespaces so we can try the same with registry editor namespaces but first we have to know which one cause this problem.
Author
Owner

@LjungErik commented on GitHub (Mar 14, 2016):

Yes, the Renamer is the root cause of the problem. To confirm this I added a check to prevent the Renamer from obfuscation the Registry namespace which seems to have solved the problem.

<!-- gh-comment-id:196257393 --> @LjungErik commented on GitHub (Mar 14, 2016): Yes, the `Renamer` is the root cause of the problem. To confirm this I added a check to prevent the `Renamer` from obfuscation the Registry namespace which seems to have solved the problem.
Author
Owner

@DragonzMaster commented on GitHub (Mar 14, 2016):

you can see #369 , I don't know if it will help you or no.

<!-- gh-comment-id:196262588 --> @DragonzMaster commented on GitHub (Mar 14, 2016): you can see #369 , I don't know if it will help you or no.
Author
Owner

@LjungErik commented on GitHub (Mar 14, 2016):

Thanks, @DragonzMaster this is how i solved the problem. I'll try and get everything pushed to my fork later today and hopefully make a pull request tomorrow.

<!-- gh-comment-id:196331295 --> @LjungErik commented on GitHub (Mar 14, 2016): Thanks, @DragonzMaster this is how i solved the problem. I'll try and get everything pushed to my fork later today and hopefully make a pull request tomorrow.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Quasar#217
No description provided.