![]() ![]() You’re right that comment is even offtopic enought so I better stop here. Like scan da code for all occurence of 31 C0 and 33 C0 and the modify it like this It’s just da style what matters.Īh and there I even got some other idea – you may use this kind of simularities for stegographie(=To scramble hidden messages into data\Watermarking). Well of course the result of both is the same. ![]() the ‘reversed’ compiler standard (xor second, first op). So on the one hand we’ve 33 C0, which is the standard (xor first, second op ) nearly each compiler uses.Īnd on the other hand there is 31 C0. Nice that Intel even thought of us reverse engineers when creating the x86 operation set. Just because I curious I had a look at the patch patch.Īnd thought though 31 c0 ugh what’s this? Isn’t that supposed to be 33 c0? So I triedģ1 C0 => XOR EAX, EAX and then just for checkingģ3 C0 => XOR EAX, EAX funny thing man what’s thisģ3 C1 => XOR EAX, EAX Haharr! ….so Mr.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |