Welcome back to Advance Export Development, and in this section, we're going to go for the bad character
analysis of the section I already eliminated zero eight.
But just to demonstrate now, the point I'm trying to make in this section is that there is a lot of
bad characters in this application due to the Unicode encoding.
However, a viable alternative to using standard SQL code is to encode your code using any range from
zero to nine and capital A to Capital Z that will be Hex 41 and capital A in Hex five A four Capital
Z.
When we use our Alpha to encoder, it will all be based along interweaved numbers, as you can see right
here.
So we're going to just take out a few bad characters first to demonstrate the limited character said
that we are dealing with when it comes to Unicode exploits.
So let's go back and restart immunity.
So control of two to restart go.
Yes, OK.
Pressplay.
We refer to Lord Steele's.
Contrary to act, I jumped to an expression, go to our pop pop return instruction.
Yes.
And we're going to try to eliminate one bad character.
Top 40, remember, were taking over S.H., so passionate ception.
Then increment.
And go all the way down to pushbacks then, right, click on the register, address the following dump,
and we got remember, this is all Unicode and coded, so now it's appended with no bytes.
So zero one zero two zero three if you go all the way down to.
Zero, eh?
That is our first bad character, so we can take a note of that.
But just to let you know, we're not going to be using standard show code, we're going to code it using
uppercase letters and numbers.