x84 | python telnet/ssh server | Command Line Interface 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:

When you enter the input with escape characters, you are actually providing the characters '\', 'x', '8', '6' etc. as separate ASCII-encoded bytes. If the characters had corresponded to some correct UTF-8 encoding, you could probably enter it at least by copying and pasting, if not through typing on your keyboard. But exploits rarely correspond to valid encodings, so an alternate is to use another program to supply the specific sequence of bytes through the input stream of your vulnerable binary.

You can use a python one-liner to supply your input containing escape characters:

Replace double backslashes with a single backslash and use decode('utf-8')

If your project depends on build environment, we suggest that you use self-hosted agents, which give you more control to install dependent software needed for your builds and deployments. If the project is running correctly locally, you should get the same result using self-hosted agents which will build on your local machine.

In addition, if you prefer to use Microsoft-hosted agents, please make sure that it is the same build environment as your local machine. You can see the installed software for each hosted agent by choosing the Included Software link in the table.

BTW, you could set pipeline variable system.debug to true, and then queue a new build to get debug logs, so you can review it to get detailed build information. See: Troubleshoot pipeline runs for details.

Try open(filename, encoding="utf-8").

This will give you Unicode strings that are already decoded.

Re: the code to use to generate the contents of the file:

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 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:

I guess that when you say "I want to convert umlauts into hex codes", you mean that you want a C string representation of the string, where some characters are encodes as escape sequences.

Let's do that and treat the following characters:

• basic escape sequences: The special characters like tab (\t) are encoded as backslash plus one letter.
• hex escape characters: All other characters not in the valid ASCII range from 32 to 127 are encoded as a sequence like \xc0.

These escapes make the string longer, so you cannot encode the string in place. Create another string that can hold at least four times the original string length plus one for the null terminator.

Now iterate over the original string and convert as you go: