You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
It looks like in one of the newer Eazfuscator versions (I can't specify a exact version number, sorry!), the assembly resolver component has had a change made to it which resulted in this tool breaking.
Hello,
It looks like in one of the newer Eazfuscator versions (I can't specify a exact version number, sorry!), the assembly resolver component has had a change made to it which resulted in this tool breaking.
The breaking change:
https://github.com/HoLLy-HaCKeR/EazFixer/blob/a99eca4c84cc022d8afd6c5eb152fd3b09c65462/EazFixer/Processors/AssemblyResolver.cs#L136
In the newer versions
i
is initialized to1
instead of0
in the loop. This causes aIndexOutOfRangeException
to occur later in the process as the tool tries to read out of the bounds of thesplit
array.Picture of change:
![image](https://user-images.githubusercontent.com/37494960/146998558-f97f15ea-bc1d-43f6-a7c5-c6bcf72647ab.png)
Non-breaking change:
![image](https://user-images.githubusercontent.com/37494960/146998789-3fccaeff-647d-4e9f-93f5-f8b191232e87.png)
Eazfuscator seems to have added a new
f
flag. Luckily it doesn't affect this tool at all.Sample which can be used to reproduce this issue:
Sample-all.zip
The text was updated successfully, but these errors were encountered: