xed | x86 encoder decoder | Messaging library

I replicated this error with the continuumio/miniconda2:4.5.11 Docker image:

I don't know where you see the value 0x119, but BYTE bootstrap[12] is a BYTE array.

So assigning bootstrap[i++] = sizeof(bootstrap) + shellcodeALength - i - 4; will store the lowest byte of the expression in bootstrap[i++] and ignore the rest, hence can never go above 255.

You probably want something like this instead:

To display the user friendly names you have given instead of the values.

RIP is the 64-bit program counter on x86-64. The disassembler is using RIP to keep track of the address of each instruction.

exampleRip is the start address for exampleCode, to be shown as the address of each instruction.

Normally you'd use a single 64-bit integer variable for that, but JavaScript numbers are IEEE double floating point so they round large numbers to a multiple of some power of 2, i.e. round away the low bits of big numbers, making it unusable for kernel addresses (in the high half of the canonical address range). (awk also uses double, and https://unix.stackexchange.com/questions/649013/why-does-awk-print-0xffffffffbb6002e0-as-ffffffffbb600000-using-printf on unix.SE is an example of the effect, with FP explanation.)

That's the point of this comment:

// You have to enable the bigint feature to get i64/u64 APIs, not all browsers support BigInt

They're explaining that they're not using the BigInt feature, so instead they use two variables (exampleRipHi and exampleRipLo) to implement one 64-bit variable.

You can use the escape function like this to print the string to the console or insert it into the HTML.

When you use single quote for a string each character is as it is and php doesn't interpret it, so $str2 can't convert to another encoding.

Also Query strings assumes as single quote strings so $str3 is like $str2.

And the solution is stripcslashes. it actually converts a single quote string to double quote string.

and you can fix it in this way:

Getting the same hash requires when writing and reading a video file requires careful attention.

Before comparing the hash, try to look at the video first.

Executing your code gave me the following output (first frame of video_2):

When the input (first frame of video) is:

I suggest the following modifications:

• Use AVI container (instead of MKV) for storing test_2 video in raw video format.
  AVI video container is originally designed for storing raw video.
  There could be a way for storing raw, or lossless RGB video in MKV container, but I am not aware of such option.
• Set the input pixel format of test_2 video.
  Add an argument: pixel_format='rgb24'.
  Note: I modified it to pixel_format='bgr24', because AVI supports bgr24 and not rgb24.
• Select video a lossless codec for test_2 video.
  You may select vcodec='rawvideo' (rawvideo codec is supported by AVI but not supported by MKV).

Note:
For getting equal hash, you need to look for lossless video codec that supports rgb24 (or bgr24) pixel format.
Most of the lossless codecs, converts the pixel format from RGB to YUV.
The RGB to YUV conversion has rounding errors that prevents equal hash.
(I suppose there are ways to get around it, but it's a bit complicated).

Here is your complete code with few modifications:

The initial bytes PK\x03\x04 suggest that it's PK Zip format. Try unzipping it first, either with unzip x or with Python builtin zipfile module.

The problem is that when you convert numpy bytes to str it adds up the escape characters (i.e., \) to every \, which results in \\ instead of \ (e.g., \x00 turns into \\x00 etc.). This messes up the decoding of the string back to the numpy bytes object. In addition, the str() function adds the b\ and the ' to the string, which are then being also encoded as bytes.

The fix is to get rid of all the added characters, (i.e., the extra \ and of the first two b' and the last '). The b' and the last ' characters are easily removed by the [2:-1] indexing operation. Then the 'ISO-8859-1' will remove all the redundant \s and will bring it to the original form (i.e., the form of the vector_bytes)

Here is the solution: