xff | A Golang Middleware to handle X-Forwarded-For Header | Runtime Evironment library

You can't use serialPuts to send the null terminator. As with all similar functions, it will stop when the null terminator is encountered in the string. In this case I think your best option is to add a function that uses the ordinary write function that is used internally by WiringPi's own functions.

You could make a wrapper function to make it look similar to the other calls:

the values following to the ff, fe, 00 etc do not make sense to me when talking about characters.

That's because you don't know how UTF-16 works.

The 16 in UTF-16 refers to how many bits characters use, i.e. each character will use 2 bytes.

When you have two bytes A and B, you can physically place them as AB (that's called "little-endian") or BA (that's "big endian"). That's called byte order, and it's important to know for successful conversion of bytes back to characters ("decoding") later.

For this, the byte string starts with a byte-order mark ("BOM"). \xff\xfe is the BOM for the "little endian" type.

Characters like G do not need the full 16 bit, so the second byte stays empty (\x00) and G becomes \x47\x00. Python displays characters for all bytes that are less than 127, so this gets displayed as G\x00, but it's the same thing.

Little-endian encoding:

You need to call eval on it and then write it to a file

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:

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

This is the address of the memoryview object in memory not the string object itself (assuming CPython implementation). In order to see the string bytes you need id(s) or id(memv.obj):

decompressed = zlib.decompress(message, -zlib.MAX_WBITS).decode('UTF-8')

Bouncy Castle doesn't have a native CBOR decoding.

If you give it a public key point it will try and parse a X9.62 formatted point, which starts with a byte valued 02 or 03 for a compressed point and 04 for an uncompressed point. Compression in this case means that the Y-coordinate is calculated from the X-coordinate according to an EC-specific algorithm.

If you want to create a point to decompress giving the current point you will first have to parse the point using a CBOR library. Then you'd have to stick the X-coordinate and Y-coordinate together and put 04 in front of it, which would give you:

From the look of the header (b'\xff\xd8), those seem to be standard jpeg images as raw data.

You can show them by using loadFromData(), Qt is smart enough to recognize the file format from its contents, as long as the data is not corrupted.
Note that that function returns a bool stating if loading was successful or not, so you first need to create the instance, and then call the function.