{qP} Posted December 18, 2016 Share Posted December 18, 2016 Difficulty : 3? You decide. I'm interested in your opinion of the difficulty level!Language : .NETPlatform : Microsoft WindowsOS Version : Microsoft Windows XP and AbovePacker / Protector : Intellilock Description : Figure out the correct string for the textbox. If correct, you will be prompted with a "Success!" messagebox. Screenshot : 12182016CrackMe.zip Link to comment Share on other sites More sharing options...
crystalboy Posted December 19, 2016 Share Posted December 19, 2016 (edited) Level in my opinion is 1. Here my solution. Spoiler Correct serial is: DP4YGP74THX052O How to solve: - Break on MessageBox.Show method on System.Windows.Forms.MessageBox then trace until we find the method responsible to perform the check The comparision between inserted serial and the correct serial is made through CompareString: Then have the right serial to solve the challenge: Edited December 19, 2016 by crystalboy 3 Link to comment Share on other sites More sharing options...
{qP} Posted December 19, 2016 Author Share Posted December 19, 2016 (edited) 3 hours ago, crystalboy said: Level in my opinion is 1. Here my solution. Hide contents Correct serial is: DP4YGP74THX052O How to solve: - Break on MessageBox.Show method on System.Windows.Forms.MessageBox then trace until we find the method responsible to perform the check The comparision between inserted serial and the correct serial is made through CompareString: Then have the right serial to solve the challenge: Awesome, thank you for your freedback! Yeah the main reason I did this was to see if someone could see the raw string. I used something that 'scrambles' the string I used (DP4YGP74THX052O) in the source. So if someone uses a reflector they would see the wrong string. But, I guess it actually doesn't work which is fine I was just seeing how that plus obfuscation would work out together. I can show you what I mean about the 'scrambles' part when I get home. I'll still use the scramble method because I use some external .ini files for my programs, and if I scramble the text in the .ini files my program 'deceypts' it and can still reads what my settings are. Also if a user opens the .ini it's just random looking strings too. So it's okay I guess. Edited December 19, 2016 by {qP} Forgot something. Link to comment Share on other sites More sharing options...
mrexodia Posted December 20, 2016 Share Posted December 20, 2016 Most obfuscators are useless against debuggers if you are trying to hide values, just makes it a little more annoying... 1 Link to comment Share on other sites More sharing options...
man of the war Posted February 19, 2017 Share Posted February 19, 2017 Easy Link to comment Share on other sites More sharing options...
+noble Posted February 25, 2017 Share Posted February 25, 2017 Solved by hooking microsoft.visualbasic.compilerservices.operators.comparestring and forcing it to return 0 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now