mirror of
https://github.com/quasar/Quasar.git
synced 2026-04-25 23:35:58 +03:00
[GH-ISSUE #426] Obfuscation prevents RegistryEditor from working properly #217
Labels
No labels
bug
bug
cant-reproduce
discussion
duplicate
easy
enhancement
help wanted
improvement
invalid
need more info
pull-request
question
wont-add
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Quasar#217
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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.
@LjungErik commented on GitHub (Mar 14, 2016):
Yes, the
Renameris the root cause of the problem. To confirm this I added a check to prevent theRenamerfrom obfuscation the Registry namespace which seems to have solved the problem.@DragonzMaster commented on GitHub (Mar 14, 2016):
you can see #369 , I don't know if it will help you or no.
@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.